Thanks Petr.
I wonder what the point of get_property(foo VARIABLE PROPERTY bar) is if it
is equivalent to set(foo ${bar}). It just seems like the weirdest feature
to add.
On Thu, Apr 17, 2014 at 2:10 AM, Petr Kmoch wrote:
> Hi James.
>
> Quoting the docs at http://www.cmake.org/cmake/help/v2.
For the case when libplplot (the principal library of the PLplot
project) is linked to Qt4, libplplot can be exported and other
projects can import and link to libplplot and its Qt4 dependency
without issues regardless of whether libplplot is built shared or
static. However, there are linking err
I'm not sure if this is a bug, but in my top level CMakeLists.txt file I
try to do something like this:
cmake_minimum_required ( VERSION 2.8.11 FATAL_ERROR )
include ( checkOutOfSource.cmake )
include ( configureBuilds.cmake )
include ( configurePlatform.cmake )
enable_language ( C )
enable_langua
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
Thanks for your answers!
Le 17/04/2014 14:38, Jakub Zakrzewski a écrit :
Visual Studio doesn't work like a good gcc?
Good joke. ;)
The only thing I prefer in VS is his debugger...
Is there some option to export automatically some methods without using
__declspec(dllexport)?
No. There are
>> Visual Studio doesn't work like a good gcc?
Good joke. ;)
>> 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 muc
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 4/17/14, Aggelos Kolaitis wrote:
> Short: Is linking to Mac OS X frameworks with Xcode generator totally
> broken, or am I just doing something wrong?
>
> Long: I use CMake as the build system for my project[1], and I use
> this [2] module to find SDL2 in the user's system. find_library() opts
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
Hi James.
Quoting the docs at http://www.cmake.org/cmake/help/v2.8.12/cmake.html:
"""
get_property(
wrote:
> I see that I can get the value of a variable from a directory using:
>
> get_directory_property(sub1_val1 DIRECTORY sub1 DEFINITION val1)
>
> Can I do the same thing with
Short: Is linking to Mac OS X frameworks with Xcode generator totally
broken, or am I just doing something wrong?
Long: I use CMake as the build system for my project[1], and I use
this [2] module to find SDL2 in the user's system. find_library() opts
for the SDL2.framework on Mac OS X, which is l
13 matches
Mail list logo
