Re: [CMake] [binary dir] breaks INSTALL(...) if added to ADD_SUBDIRECTORY(...)

It works! I will avoid using the [binary dir] option from now.Thanks for the reference to "CMake_Useful_Variables". I did search the wiki, but using an underscore in the search string doesn't work.Cheers, Peter.On 10/21/06, Filipe Sousa <[EMAIL PROTECTED]> wrote: Filipe Sousa wrote:> Peter Visser w

Re: [CMake] 64bit format

Original-Nachricht Datum: Fri, 20 Oct 2006 18:05:09 +0200 Von: frederic heem <[EMAIL PROTECTED]> An: cmake Betreff: [CMake] 64bit format > Hi, > While trying to convert ethereal build system from autotool to cmake, I > came > across a problem which may be already solved. > The

Re: [CMake] [binary dir] breaks INSTALL(...) if added to ADD_SUBDIRECTORY(...)

Filipe Sousa wrote: > Peter Visser wrote: >> Thanks for the advice, but I cannot find these directives in the >> documentation (http://www.cmake.org/HTML/Documentation.html). >> Perhaps I'm looking in the wrong place, where do I need to look for the >> documentation? http://www.cmake.org/Wiki/CMak

Re: [CMake] [binary dir] breaks INSTALL(...) if added to ADD_SUBDIRECTORY(...)

Peter Visser wrote: > Thanks for the advice, but I cannot find these directives in the > documentation (http://www.cmake.org/HTML/Documentation.html). > Perhaps I'm looking in the wrong place, where do I need to look for the > documentation? You're right, this is not documented. But you can use it

Re: [CMake] [binary dir] breaks INSTALL(...) if added to ADD_SUBDIRECTORY(...)

Thanks for the advice, but I cannot find these directives in the documentation (http://www.cmake.org/HTML/Documentation.html).Perhaps I'm looking in the wrong place, where do I need to look for the documentation? Thanks again, Peter.On 10/21/06, Filipe Sousa <[EMAIL PROTECTED]> wrote: Peter Visser

Re: [CMake] [binary dir] breaks INSTALL(...) if added to ADD_SUBDIRECTORY(...)

The default build directory works fine, however I would like to group some components:ADD_SUBDIRECTORY (Example1 foo)ADD_SUBDIRECTORY (Example2 foo)ADD_SUBDIRECTORY (Example3 bar)ADD_SUBDIRECTORY (Example4 bar) In my case I can omit the foo and bar since I don't have conflicting names in the execut

Re: [CMake] [binary dir] breaks INSTALL(...) if added to ADD_SUBDIRECTORY(...)

Peter Visser wrote: > Hello, > > The following example works fine: > > > In the top CMakeLists.txt > ADD_SUBDIRECTORY (Example1) > ADD_SUBDIRECTORY (Example2) > > In the subdirectories Example1/Example2 > INSTALL(TARGETS Example1/Example2 > RUNTIME DESTINATION bin >

Re: [CMake] TRY_COMPILE and CMAKE_C_FLAGS

Gregor Jasny wrote: > Hi, > > I want to test if the current GNU compiler accept the -fopenmp flag. INCLUDE(CheckCCompilerFlag) CHECK_C_COMPILER_FLAG(-fopenmp HAVE_OPENMP) -- Filipe Sousa signature.asc Description: OpenPGP digital signature ___ CMake

Re: [CMake] [binary dir] breaks INSTALL(...) if added to ADD_SUBDIRECTORY(...)

On 2006-10-21 12:39+0200 Peter Visser wrote: Hello, The following example works fine: In the top CMakeLists.txt ADD_SUBDIRECTORY (Example1) ADD_SUBDIRECTORY (Example2) In the subdirectories Example1/Example2 INSTALL(TARGETS Example1/Example2 RUNTIME DESTINATION bin LI

[CMake] [binary dir] breaks INSTALL(...) if added to ADD_SUBDIRECTORY(...)

Hello,The following example works fine:In the top CMakeLists.txt ADD_SUBDIRECTORY (Example1) ADD_SUBDIRECTORY (Example2) In the subdirectories Example1/Example2INSTALL(TARGETS Example1/Example2     RUNTIME DESTINATION bin     LIBRARY DESTINATION lib     ARCHIVE DESTINA

[CMake] TRY_COMPILE and CMAKE_C_FLAGS

Hi, I want to test if the current GNU compiler accept the -fopenmp flag. In my cmake module I have the following test: TRY_COMPILE( OPENMP_COMPILED ${CMAKE_BINARY_DIR} ${CMAKE_SOURCE_DIR}/cmake/Modules/CheckForOpenMP.c CMAKE_FLAGS -DCMAKE_C_FLAGS:STRING="-fopenmp" OUT