On Sat, 2 Nov 2013 15:09:25 +0100
Petr Kmoch wrote:
> Hi Ivan.
> The correct use of OBJECT libraries is not to link against them, but
> to list them as sources (using a special syntax), like this:
> add_executable(project main.c $)
> (Assuming 'serial' is the name of the object library). This
Wow, this thread has gone wild...
To clarify my case:
The prototype of each functions I want to export is prefixed by a
MYPROJECT_EXTERNAL preprocessor constant. With Visual Studio, this constant
is, by default, set to __declspec(dllimport). This way, I can link against
the shared version of this
Hi Ivan.
The correct use of OBJECT libraries is not to link against them, but to
list them as sources (using a special syntax), like this:
add_executable(project main.c $)
(Assuming 'serial' is the name of the object library). This is outlined in
the documentation for OBJECT libraries.
Petr
O
So the bugfix would be to use the -D parameters, given to cmake-gui, when
configuring a completely new project (=> cache is empty/non existing)? That
would make sense to me and shouldn't be hard to implement.
On Sat, Nov 2, 2013 at 1:00 PM, David Cole wrote:
> -Original Message-
>> From
-Original Message-
From: J Decker
To: physhh .
Cc: cmake
Sent: Fri, Nov 1, 2013 9:51 pm
Subject: Re: [CMake] Forwarding parameters to cmake through cmake-gui
sorry and I should ask; after reading a bit more context;
why are you using cmake-gui if you have -D's to pass already?
It
-Original Message-
From: physhh .
To: Matthew Woehlke
Cc: CMake ML
Sent: Fri, Nov 1, 2013 8:19 pm
Subject: Re: [CMake] Forwarding parameters to cmake through cmake-gui
The question is: What is the expected behavior?
Execute it per configure but don't overwrite variables? What if one