[CMake] ExternalProject and another CMake based project.

Hello all, I would like to use the ExternalProject_Add command in one CMake project to include another CMake based project. Basically this works great, the project is downloaded, configured, build, tested and installed. (Great command, the ExternalProject!) The libraries of the included proj

Re: [CMake] CMake 2.8.5 problem with include directories with response files

On 8/12/2011 3:17 PM, David Cole wrote: Sounds like you're using "MSYS Makefiles" but then running make from a non-MSYS shell. I have tried the following msys shells. sh.exe rxvt.exe mintty.exe For all these shells the include directories with response files do not work. If I paste the conten

[CMake] CMake 2.8.5 problem with include directories with response files

Hello, I experience a problem with "include directories with response files" when upgrading from CMake 2.8.4 to CMake 2.8.5. The problem is probably that gcc does not handle the response files correctly. Is it possible to disable the response files with an option in CMake ? I have a small "H

Re: [CMake] custom target (kernel modules)

Hi, could you post the working example? I'm doing something similar but I'm doing it wrong, the add_custom_command is always being build in my case. Thanks in advance, Peter. On 6/28/07, Alexandru Ciobanu <[EMAIL PROTECTED]> wrote: Thanks Alan, it works. =) Alan W. Irwin wrote: > On 2007-06

Re: [CMake] CPack and 7-Zip?

Please update from cvs. It seems stripping static libs is a bad idea (since it removes their symbol table) and stripping import libs doesn't make sense (since they don't have debug information), so both are now excluded from stripping. Please correct me if I'm wrong. Let me know if stripping t

Re: [CMake] CPack and 7-Zip?

> INSTALL(TARGETS helloworld > RUNTIME DESTINATION bin STRIP_ALWAYS > LIBRARY DESTINATION lib STRIP_NEVER > ARCHIVE DESTINATION lib STRIP_NEVER >) > > In my case that would work very well. I guess you would do it this way for

Re: [CMake] CPack and 7-Zip?

We'll do something about it. How about adding options to the install() command like STRIP_ALWAYS and STRIP_NEVER ? Do you mean something like this: INSTALL(TARGETS helloworld RUNTIME DESTINATION bin STRIP_ALWAYS LIBRARY DESTINATION lib STRIP_NEVER

Re: [CMake] CPack and 7-Zip?

te: On Thursday 14 June 2007 16:36, Peter Visser wrote: > I rather like the current (2.4.6) fine grained approach. In the past I > experienced problems (run-time crashes) when stripping dll's, hence not > stripping them better suits my specific case. > > Furtermore, the cvs

Re: [CMake] CPack and 7-Zip?

n the package target): ...strip.ex 'dll.a' : No such file Regards, Peter. On 6/14/07, Alexander Neundorf <[EMAIL PROTECTED]> wrote: On Thursday 14 June 2007 16:11, Peter Visser wrote: > I just tried the current cvs HEAD, 7zip now works fine in my case. > Thanks for t

Re: [CMake] CPack and 7-Zip?

e, or perhaps the command has changed ? Cheers, Peter. On 6/14/07, Alexander Neundorf <[EMAIL PROTECTED]> wrote: On Tuesday 15 May 2007 04:50, Peter Visser wrote: > Thanks for the suggestion but still no 'sutable' ZIP program found. > > I have associated 7-Zip with .z

Re: [CMake] CPack and 7-Zip?

Thanks for the suggestion but still no 'sutable' ZIP program found. I have associated 7-Zip with .zip files (and all other possible extensions .tar .gz .rar and so on.) and added 7-Zip to the system path. But unfortunately CPack was not able to use 7-Zip yet. I used my *old* system again and no

[CMake] CPack and 7-Zip?

fPackers.cmake, but could not find a solution for this. Regards, Peter Visser. ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Cmake Editor for Eclipse

Hi, I'm using the plugin without problems under windows XP with Eclipse 3.3M7 / CDT4.0RC0. Great work! Peter. On 5/12/07, Maik Beckmann <[EMAIL PROTECTED]> wrote: Am Samstag, 12. Mai 2007 13:00:43 schrieb Trevor Kellaway: > Good news, but alas it doesn't seem to work for me (using Eclipse >

Re: [CMake] MSYS paths (in build output)

As a temporary solution I will 'regexp' the paths in the build output. Thanks for your response, Peter. On 5/9/07, Brandon Van Every <[EMAIL PROTECTED]> wrote: On 5/8/07, Peter Visser <[EMAIL PROTECTED]> wrote: > > Hello, > > I'm using eclipse with min

[CMake] MSYS paths (in build output)

Hello, I'm using eclipse with mingw/msys. Eclipse scans the build output for auto discovery of include paths and defines, which is very useful for auto completion. I upgraded from CMake 2.4.3 to CMake 2.4.6 and this breaks the auto discovery from eclipse. The reason for this is that CMake 2.4.3

Re: [CMake] LINK_LIBRARIES() does not respect SUFFIX/PREFIX

Great! A while ago I tried to cross-compile code for win32 with mingw from linux and ran into the same problem with the library PREFIX and SUFFIX. Setting the PREFIX and SUFFIX globally works great, cross-compiling now works good for my project (and much faster than the native compile with mingw

Re: Re[2]: [CMake] CMake and Eclipse

Hi, What I found useful when using eclipse is adding 'VERBOSE=1' to make. Eclipse scans the output of the build process (enabled by default -> 'discovery options' -> 'enable build output scanner info discovery') on INCLUDE/LIBRARY directories and uses this for the code completion functionality.

Re: [CMake] MSYS + MINGW + wx-config.sh

Hi, Instead of trying to call wx-config directly, you can (should) use "FIND_PACKAGE(wxWidgets)", this will call the wx-config shell script and set the necessary/required variables. for example the wx_minimal sample: ### PROJECT(wx_minimal) FIND_PACKAGE(wxWidgets) IF(wxWidgets_FOUND) IN

[CMake] ADD_CUSTOM_TARGET [ANY] ?

Hi, I would like to execute a command exactly one time during each build for any, some or all targets, it this possible in an easy way? I fiddled with the ADD_CUSTOM_TARGET and ADD_CUSTOM_COMMAND commands but was unable to do so. For instance when I used ADD_CUSTOM_TARGET(dummy ALL echo FOO), th

[CMake] FindwxWidgets.cmake, suggestion add option to pass to wx-config

Hi, I'm using FindwxWidgets, currently it seems that it is not possible to specify options like version, debug static and so on. At least not for non-WIN32 (The documentation describes to specify arguments to nmake at build time.). Perhaps it is an idea to pass options to wx-config. This could

Re: [CMake] Problem with library prefix/suffix when cross compiling.

Hi, I now have a working example to cross compile the CMake example ( http://www.cmake.org/HTML/Examples.html) with MINGW under linux for windows. Unfortunately it requires a "small" replace in a build.make file, I wasn't able to figure it out completely in CMake. To get the example working I ch

Re: [CMake] Problem with library prefix/suffix when cross compiling.

le Win32 using mingw32" OFF) was set ON for mingw32 cross compiling and OFF for Linux "native" compiling. Then use your MY_TARGETLIB_xxx in all other places: SET_TARGET_PROPERTIES(ex1 PROPERTIES PREFIX $(MY_TARGETLIB_PREFIX) SUFFIX $(MY_TARGETLIB_SUFFIX)

[CMake] Problem with library prefix/suffix when cross compiling.

Hi, I have a working build under win32 with MSYS/MINGW, now I would like to cross-compile code for win32 with mingw from linux with by using the same CMakelists.txt files. It almost works, the problem is that the shared libraries are not named "myex.dll" but "libmyex.so". By using the following c

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

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: P

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

n 10/21/06, Alan W. Irwin <[EMAIL PROTECTED]> wrote: 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 Exampl

[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

Re: [CMake] CPack (NSIS) error - hello example

emptyinstall tree prior to running "make package" successfully.HTH,DavidOn 10/20/06, Peter Visser < [EMAIL PROTECTED]> wrote:> Hello,>> I would like to use CPack to make an install package with NSIS for win32.>> I downloaded the hello example > (http://www.cmak

[CMake] CPack (NSIS) error - hello example

Hello,I would like to use CPack to make an install package with NSIS for win32.I downloaded the hello example (http://www.cmake.org/HTML/Examples.html) added "INCLUDE(CPack)" to the CMakeLists.txt (http://www.cmake.org/Wiki/CMake:Packaging_With_CPack) and tried to run "make package"However an error

[CMake] MSYS EXEC_PROGRAM() or EXECUTE_PROCESS() fails

I just "discovered" cmake, I find cmake easy to setup and it works fantastic. However, a small problem occurs. I'm using: cmake 2.4-patch3 under MSYS-1.0.10.  The problem occurs when using EXEC_PROGRAM() or EXECUTE_PROCESS(). Instead of "sh.exe" from MSYS being used to execute the program "cmd.exe