Re: [CMake] Newbie questions: verbosity and compiler invocation

2010-09-10 Thread Alexander Neundorf
On Thursday 09 September 2010, David Aldrich wrote: Hi Michael With CMake you can use absolute and relative paths, no problem. If you use absolute paths, please use one of the pre-defined variables, such as ${CMAKE_SOURCE_DIR}, ${CMAKE_BINARY_DIR}, ${CMAKE_CURRENT_SOURCE_DIR}

Re: [CMake] Newbie questions: verbosity and compiler invocation

2010-09-09 Thread David Aldrich
Hi Michael The makefile I am replacing uses VPATH to specify a source file that must be compiled for the target. That source file is in a different directory to the one containing CMakeLists.txt. How can I achieve this with CMake please? Best regards David

Re: [CMake] Newbie questions: verbosity and compiler invocation

2010-09-09 Thread David Aldrich
Hi Michael With CMake you can use absolute and relative paths, no problem. If you use absolute paths, please use one of the pre-defined variables, such as ${CMAKE_SOURCE_DIR}, ${CMAKE_BINARY_DIR}, ${CMAKE_CURRENT_SOURCE_DIR} ${CMAKE_CURRENT_BINARY_DIR} ${PROJECT_SOURCE_DIR},

Re: [CMake] Newbie questions: verbosity and compiler invocation

2010-09-09 Thread David Aldrich
Hi Michael Are they _always_ next to each other and is FolderB always called by that name? Yes If so, just do ${CMAKE_PROJECT_DIR}/../FolderB. Thanks that worked fine. I wasn't aware of that syntax possibility. David ___ Powered by

Re: [CMake] Newbie questions: verbosity and compiler invocation

2010-09-09 Thread Michael Wild
On 9. Sep, 2010, at 15:37 , David Aldrich wrote: Hi Michael Are they _always_ next to each other and is FolderB always called by that name? Yes If so, just do ${CMAKE_PROJECT_DIR}/../FolderB. Thanks that worked fine. I wasn't aware of that syntax possibility. David There's

[CMake] Newbie questions: verbosity and compiler invocation

2010-09-08 Thread David Aldrich
Hi I am experimenting with using CMake to replace our manually written gnu makefiles on Linux. I have a couple of questions: 1) VERBOSITY I would like to see the compiler command on the console when running make. I know that one can run: make VERBOSE=1 but that displays a lot of detail, for

Re: [CMake] Newbie questions: verbosity and compiler invocation

2010-09-08 Thread Michael Wild
On 8. Sep, 2010, at 16:33 , David Aldrich wrote: Hi I am experimenting with using CMake to replace our manually written gnu makefiles on Linux. I have a couple of questions: 1) VERBOSITY I would like to see the compiler command on the console when running make. I know that one can

Re: [CMake] Newbie questions: verbosity and compiler invocation

2010-09-08 Thread David Aldrich
Wild [mailto:them...@gmail.com] Sent: 08 September 2010 15:56 To: David Aldrich Cc: CMake@cmake.org Subject: Re: [CMake] Newbie questions: verbosity and compiler invocation On 8. Sep, 2010, at 16:33 , David Aldrich wrote: Hi I am experimenting with using CMake to replace our

Re: [CMake] Newbie questions: verbosity and compiler invocation

2010-09-08 Thread Michael Wild
...@gmail.com] Sent: 08 September 2010 15:56 To: David Aldrich Cc: CMake@cmake.org Subject: Re: [CMake] Newbie questions: verbosity and compiler invocation On 8. Sep, 2010, at 16:33 , David Aldrich wrote: Hi I am experimenting with using CMake to replace our manually written gnu makefiles

Re: [CMake] Newbie questions: verbosity and compiler invocation

2010-09-08 Thread David Aldrich
Hi Michael Yes, this is correct. Thanks. And before you even get the idea: Never add the CMake-generated files (Makefile, CMakeCache.txt, etc.) to your version control system. They are not relocatable. Ah yes. You told me that before ;-) I will take your advice! David