Is there some option to export automatically some methods without using
__declspec(dllexport)?
>>
>> No. There are workarounds like in
>> http://stackoverflow.com/questions/225432/export-all-symbols-when-creating-a-dll
>> but it's too much work.
>> Basically you want to define a macro tha
2014 14:27
To: Nils Gladitz; cmake@cmake.org
Subject: Re: [CMake] Linking Error with Visual Studio 2013 x64
Visual Studio doesn't work like a good gcc? Because, I try this code with mingw
(32 and 64) and it's working perfectly.
Is there some option to export automatically some met
Leguay
Sent: Donnerstag, 17. April 2014 14:27
To: Nils Gladitz; cmake@cmake.org
Subject: Re: [CMake] Linking Error with Visual Studio 2013 x64
Visual Studio doesn't work like a good gcc? Because, I try this code with mingw
(32 and 64) and it's working perfectly.
Is there some optio
On 17.04.2014 14:26, Romain Leguay wrote:
Visual Studio doesn't work like a good gcc? Because, I try this code
with mingw (32 and 64) and it's working perfectly.
Is there some option to export automatically some methods without
using __declspec(dllexport)?
Per default on windows the binutils
Visual Studio doesn't work like a good gcc? Because, I try this code
with mingw (32 and 64) and it's working perfectly.
Is there some option to export automatically some methods without using
__declspec(dllexport)?
Romain
Le 17/04/2014 12:03, Nils Gladitz a écrit :
On 17.04.2014 11:46, Romain
On 17.04.2014 11:46, Romain Leguay wrote:
I think I found a bug with CMake 2.8.12.2: I have on project with two
sub-folders: a SHARED library and an executable that use the library.
When I generate the Visual Studio solution, my application want to
link with a static version of my library.
I
Hello everyone,
I think I found a bug with CMake 2.8.12.2: I have on project with two
sub-folders: a SHARED library and an executable that use the library.
When I generate the Visual Studio solution, my application want to link
with a static version of my library.
I join you a very small proj
