[CMake] WINDOWS_EXPORT_ALL_SYMBOLS invalid .def file

2017-06-13 Thread Balázs Oroszi
Hi, I'm porting a rather large project/library from Linux to Windows and was looking for an automatic symbol export solution, and found the WINDOWS_EXPORT_ALL_SYMBOLS to be excellent. It works almost nicely, however there is a problem with the .def file it creates. Upon linking I get errors like t

Re: [CMake] WINDOWS_EXPORT_ALL_SYMBOLS

2016-01-27 Thread Micha Renner
Am Mittwoch, den 27.01.2016, 10:27 -0500 schrieb Bill Hoffman: > On 1/26/2016 12:51 PM, Bill Hoffman wrote: > > > > I am running the community edition... Maybe there is some > > difference > > with express? > One other question, did you build 64 or 32 bit? 64-bit. Michael -- Powered by www.k

Re: [CMake] WINDOWS_EXPORT_ALL_SYMBOLS

2016-01-27 Thread Bill Hoffman
On 1/26/2016 12:51 PM, Bill Hoffman wrote: I am running the community edition... Maybe there is some difference with express? One other question, did you build 64 or 32 bit? -Bill -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/

Re: [CMake] WINDOWS_EXPORT_ALL_SYMBOLS

2016-01-26 Thread Bill Hoffman
On 1/26/2016 5:12 AM, Micha Renner wrote: It prevents that I can link the library to a program since there is no __local_stdio_printf_options etc. May be there exists an explanation. Greetings Michael cmake 3.4.2 Windows 10 VS Express 15 So, I am able to get this to work with Visual Studio