Re: [CMake] Weird binary directory problem

2009-06-03 Thread Tyler Roscoe
Please don't top-post. > 2009/6/3 Tyler Roscoe : > > Sounds like you must have overriden the default destination directory. > > Did you set EXECUTABLE_OUTPUT_PATH (or the related target property)? On Wed, Jun 03, 2009 at 08:59:11PM +0200, Steven Van Ingelgem wrote: > Yes, but only for the base-pr

Re: [CMake] Weird binary directory problem

2009-06-03 Thread Steven Van Ingelgem
Yes, but only for the base-project, not for the project where I did an "add_subdirectory" for... 2009/6/3 Tyler Roscoe : > On Wed, Jun 03, 2009 at 01:09:09PM +0200, Steven Van Ingelgem wrote: >> When I "make" it, it says: >> Linking C executable ../../bin/file >> >> But the current binary director

Re: [CMake] Weird binary directory problem

2009-06-03 Thread Tyler Roscoe
On Wed, Jun 03, 2009 at 01:09:09PM +0200, Steven Van Ingelgem wrote: > When I "make" it, it says: > Linking C executable ../../bin/file > > But the current binary directory is "build/externals/file", why does > it build in "../../bin"?? > > How can I know in what directory the executable is being

[CMake] Weird binary directory problem

2009-06-03 Thread Steven Van Ingelgem
Hi, I have the following setup: CMakeLists.txt [have project()] externals\CMakeLists.txt [add_subdirectory(file)] externals\file\CMakeLists.txt [have project()] The problem I am facing is because in the last txt-file I have: add_executable(file ) when I ask to show the directories, what I get