The library itself depends on other ones I generated, but it isn't a
dependency itself.
I did some more research and setting EXCLUDE_FROM_DEFAULT_BUILD
worked... I find it strange that there are 2 properties that
essentially should do the same thing, but cause different behavior
depending on the s
Does another library that you add later depend on that one? Or an executable?
If so, then the library will be added because it's required by dependencies,
despite your request to exclude it from all.
-Original Message-
From: Robert Dailey
To: CMake
Sent: Fri, Feb 8, 2013 4:59
Sean:
On Feb 8, 2013, at 11:00 AM, Sean McBride wrote:
> On Fri, 8 Feb 2013 10:53:16 -0800, Ed said:
>
>>> I've never heard of "CMAKE_OSX_64" and google has only 7 results…
>>
>> "CMAKE_OSX_64" is just a variable in the cmakelists.txt file which is
>> converted to ARCH=X86_64.
>> Does this vari
On Fri, 8 Feb 2013 10:53:16 -0800, Ed said:
>> I've never heard of "CMAKE_OSX_64" and google has only 7 results…
>
>"CMAKE_OSX_64" is just a variable in the cmakelists.txt file which is
>converted to ARCH=X86_64.
>Does this variable need to be set to CMAKE_OSX_ARCHITECTURES=X86_64
>instead of ARCH
Sean:
Thanks for the suggestions.
On Feb 8, 2013, at 9:39 AM, Sean McBride wrote:
> On Fri, 8 Feb 2013 09:22:12 -0800, Ed said:
>
>> Here is what I tried:
>> cmake -DCMAKE_OSX_64=ON -DCMAKE_OSX_DEPLOYMENT_TARGET=10.6 -
>> DCMAKE_C_COMPILER=/usr/bin/gcc -DCMAKE_CXX_COMPILER=/usr/bin/g++ ..
>
> I
I'm probably missing something, but why
> add_dependencies(parent child)
? That doesn't make sense. Parent is not using anything from child. You can
just leave that line away and everything will be fine right?
On 2013-08-02, at 16:24:21 , Andreas Haferburg wrote:
> Yes, that's pretty much the
On Fri, 8 Feb 2013 09:22:12 -0800, Ed said:
>Here is what I tried:
>cmake -DCMAKE_OSX_64=ON -DCMAKE_OSX_DEPLOYMENT_TARGET=10.6 -
>DCMAKE_C_COMPILER=/usr/bin/gcc -DCMAKE_CXX_COMPILER=/usr/bin/g++ ..
I've never heard of "CMAKE_OSX_64" and google has only 7 results...
>It built fine and runs on 10.
Sean:
Sorry for the misdirection, Mail has some Idiosyncrasies I haven't quite
figured out yet.
Here is what I tried:
cmake -DCMAKE_OSX_64=ON -DCMAKE_OSX_DEPLOYMENT_TARGET=10.6
-DCMAKE_C_COMPILER=/usr/bin/gcc -DCMAKE_CXX_COMPILER=/usr/bin/g++ ..
It built fine and runs on 10.7.5 but does not run
Yes, that's pretty much the setup we have: The common (static) library contains almost all obj's,
and the two exe projects only have a small main.obj and link against the library. I'd like to
eliminate the build(=link) time of child.exe by having the linker link both exes at the same time.
Rega
Yay, that is almost what I want. Except that I'd like the launch target to behave exactly like the
parent target: When I select the project in Visual Studio, I'd like to press F7 to build it and F5
to run it (with the debugger attached). When using add_custom_target(), the exe is started at build
On Fri, Feb 8, 2013 at 8:16 AM, Andreas Haferburg wrote:
> What happens is that common is built, then child, then parent, then parent
> is executed.
> What I'd like to happen is that common is built, then child+parent are
> being built concurrently, and as soon as both are done, parent is executed
Sure. Example:
add_library(common MyFancyString.cpp)
add_executable(parent parent_main.cpp)
target_link_libraries(parent common.lib)
add_executable(child child_main.cpp)
target_link_libraries(child common.lib)
add_dependencies(parent child)
Now I make a change to MyFancyString.cpp, select the
Well cmake will take care of that if you target_link_library(common), right?
On 2013-08-02, at 12:50:13 , Andreas Haferburg wrote:
> Right, sorry. I should have mentioned that they both depend on some library
> common.lib. When that library has to be rebuilt, both exes need to be
> rebuilt, too
Right, sorry. I should have mentioned that they both depend on some library common.lib. When that
library has to be rebuilt, both exes need to be rebuilt, too.
Andreas
On 08.02.2013 12:21, Nick Overdijk wrote:
Can't you only launch parent.exe in VS and remove the dependency?
On 2013-08-02, a
Can't you only launch parent.exe in VS and remove the dependency?
On 2013-08-02, at 12:19:56 , Andreas Haferburg wrote:
> In our build, we have two executables, parent.exe launches child.exe as a
> child process. ATM the build is set up with add_dependencies(parent child).
> So when using F5 in
In our build, we have two executables, parent.exe launches child.exe as a child process. ATM the
build is set up with add_dependencies(parent child). So when using F5 in Visual Studio, child.exe is
built first, then parent.exe, then parent.exe is launched. Is it possible to set this up such that
On 7/2/13 7:54 PM, Patrick Johnmeyer wrote:
On Thu, Feb 7, 2013 at 12:41 PM, Yngve Inntjore Levinsen
mailto:yngve.levin...@gmail.com>> wrote:
I think you are fighting the tool in any case, because you are
asking to build multiple configurations in one build folder (?).
Normally you
17 matches
Mail list logo
