Google Code Exporter
Google Code Exporter
``` What do you think? Can this be included in the source? ``` Original comment by `[email protected]` on 21 Nov 2012 at 10:05
``` I fixed the typo you mentioned above. ``` Original comment by `[email protected]` on 21 Nov 2012 at 10:10 Attachments: - [FindCtemplate.cmake](https://storage.googleapis.com/google-code-attachments/ctemplate/issue-91/comment-6/FindCtemplate.cmake)
``` Yes, I think this can be included in the next release. ``` Original comment by `olafvdspek` on 22 Nov 2012 at 5:50
``` "__declspec(dllexport)" was added to avoid a warning when using the DLL, so you can't just remove it. ``` Original comment by `olafvdspek` on 1 Feb 2012 at 9:16
``` But it is posssible to use *.def export function name? Or add an other define MACRO? Such as "CTEMPLATE_STATIC". ``` Original comment by `[email protected]` on 1 Feb 2012 at...
``` Another macro might be ok if necessary. ``` Original comment by `olafvdspek` on 1 Feb 2012 at 12:24
``` Ugh, sorry for that problem. Olaf is right that I added these to silence a warning, probably based on advice in the MSDN. This dllimport/export stuff is all a...
``` Just realized I've hit this issue too, didn't know it was due to ctemplate. ``` Original comment by `olafvdspek` on 1 Feb 2012 at 6:49
``` I know two way to generate dll *.lib (c dll not c++ dll). 1th: Using lib.exe with *.def file to create *.lib. 2nd: Using __declspec(dllexport) auto create *.lib. And...
``` Just wondering, who is actually using the DLL? Until Windows gets package management, I prefer static linking. ``` Original comment by `olafvdspek` on 2 Feb 2012 at 3:10