[CMake] emitting CMakeLists.txt for TRY_COMPILE considered harmful

Summary: emitting a CMakeLists.txt is never parallel with standard coding practices in the toplevel CMakeLists.txt. At a minimum, this causes programmers to do everything 2 different ways. In the likely case, the emission fails because it is fragile as quotes are consumed. These kinds of

Re: [CMake] Makefile modification

Repost: Hi, Bill! I'm try to use CMake with Code Warrior for Nitendo DS. It seems that CW uses standard make-files. But in project makefile must be included two files There are: include$(NITROSDK_ROOT)/build/buildtools/commondefs include

[CMake] Retrieve all directories?

Hello, is it in any way possible to retrieve the list of directories within a given directory and store it into a variable? I'm looking for something like FILE(GLOB ... ) or FILE(GLOB_RECURSE...) that collects directory names instead of files. Thanks in advance Timo

Re: [CMake] Makefile modification

Ilya Shvetsov wrote: Repost: Hi, Bill! I'm try to use CMake with Code Warrior for Nitendo DS. It seems that CW uses standard make-files. But in project makefile must be included two files There are: include$(NITROSDK_ROOT)/build/buildtools/commondefs include

RE: [CMake] Simple file copy

Thanks a lot! But the name CONFIGURE_FILE suggest it happens before the build. Is that so? I need to copy lib files after build! -Regards Martin L Martin L, Software Engineer / Architect (see also www.doxys.org) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On

Re: RE: [CMake] Simple file copy

Original-Nachricht Datum: Wed, 22 Nov 2006 15:22:53 +0100 Von: Martin Lütken [EMAIL PROTECTED] An: Eric Noulard [EMAIL PROTECTED], CMake ML cmake@cmake.org Betreff: RE: [CMake] Simple file copy Thanks a lot! But the name CONFIGURE_FILE suggest it happens before the build. Is

[CMake] Finding out the Endianness of a system at CMake config time

I have recently joined a project where I am to do some coding. The code base is cross platform HPC type code and the original coders have defined their own little/big endian #defines (L_ENDIAN B_ENDIAN). They pass this into the compiler via -DL_ENDIAN during compiles. Is there a way to

Re: [CMake] Suggestion for CMake platform/compiler detection

Brandon J. Van Every wrote: If you macrotize all the CMake code out of existence, then people have to dig through your code and documentation to understand what's going on. If people need help with what's going on, they have to ask you, because nobody else in the CMake community knows what's

[CMake] Re: CMake 2.4.4 available for download

Hello all, I guess there has been a change in the interpretation of optimized and debug libraries used in the TARGET_LINK_LIBRARIES command. In 2.4.3 the following line successfully produced a link to the Qt libraries: TARGET_LINK_LIBRARIES(JCore optimized ${QT_QT_LIBRARY} debug

Re: [CMake] Finding out the Endianness of a system at CMake config time

May be you could use TRY_RUN to detect endianity with something like: TRY_RUN( ENDIANESS_RESULT ENDIANESS_COMPILE /tmp/ ${CMAKE_CURRENT_SOURCE_DIR}/make/endianess.c OUTPUT_VARIABLE ENDIANESS_OUT ) MESSAGE(STATUS ENDIANITY is :${ENDIANESS_OUT}) endianess.c is attached. The trouble I

Re: [CMake] Simple file copy

Martin Lütken wrote: Thanks a lot! But the name CONFIGURE_FILE suggest it happens before the build. Is that so? I need to copy lib files after build! I didn't really understand the rest of the post; perhaps some context got snipped. Going by the subject line, I think what you want is an

Re: [CMake] Finding out the Endianness of a system at CMake config time

Eric Noulard wrote: May be you could use TRY_RUN to detect endianity with something like: TRY_RUN( ENDIANESS_RESULT ENDIANESS_COMPILE /tmp/ ${CMAKE_CURRENT_SOURCE_DIR}/make/endianess.c OUTPUT_VARIABLE ENDIANESS_OUT ) MESSAGE(STATUS ENDIANITY is :${ENDIANESS_OUT}) endianess.c is

Re: [CMake] Re: CMake 2.4.4 available for download

wedekind wrote: Hello all, I guess there has been a change in the interpretation of optimized and debug libraries used in the TARGET_LINK_LIBRARIES command. In 2.4.3 the following line successfully produced a link to the Qt libraries: TARGET_LINK_LIBRARIES(JCore optimized ${QT_QT_LIBRARY}

Re: [CMake] Finding out the Endianness of a system at CMake config time

On 2006-11-22 19:00, Eric Noulard said: Sorry for my dummy answer: 1) There is a TestBigEndian.cmake already shipped with CMake (as of 2.4.3) 2) I should have checked ENDIANESS_RESULT and not ENDIANESS_OUT At the risk of repeating myself... :) Remember that using TRY_COMPILE/TRY_RUN or any

Re: [CMake] Finding out the Endianness of a system at CMake config time

Sean McBride wrote: On 2006-11-22 19:00, Eric Noulard said: Sorry for my dummy answer: 1) There is a TestBigEndian.cmake already shipped with CMake (as of 2.4.3) 2) I should have checked ENDIANESS_RESULT and not ENDIANESS_OUT At the risk of repeating myself... :) Remember that

[CMake] first argument to qt_wrap_cpp() and qt_wrap_ui() unused ?

Hi, it seems to me the first argument to both qt_wrap_cpp() and qt_wrap_ui(), i.e. the project argument, is unused. I don't see any effect if I change it to something arbitrary, and from looking at the sources it also not used at all. Am I right with this ? If so, can you please mention this

[CMake] Re: emitting CMakeLists.txt for TRY_COMPILE considered harmful

Maybe the following is a better explanation of the pitfalls of emitting a CMakeLists.txt. This is taken from the current Chicken CMake build. # CHANGELOG #