Re: [cmake-developers] CPack API redesign

2010-08-12 Thread Eric Noulard
2010/8/12 Brad King brad.k...@kitware.com: Hi Eric, On 08/11/2010 05:47 PM, David Cole wrote: The warnings Brad fixed showed up on the Continuous dashboard for CMake here: http://www.cdash.org/CDash/index.php?project=CMakedate=2010-08-11#Continuous

Re: [cmake-developers] CPack API redesign

2010-08-12 Thread Brad King
On 08/12/2010 08:20 AM, Eric Noulard wrote: May be adding some extra warning flags wouldn't hurt? It can make user-performed builds from release tarballs look less clean if there is a warning their compiler adds with -Wall that we do not see. It may be worthwhile though to reduce dashboard

Re: [cmake-developers] CPack API redesign

2010-08-12 Thread Brad King
On 08/12/2010 02:51 PM, Eric Noulard wrote: Sorry I did this too fast, I did merge to next and pushed as usual. It does succeed without trouble, what would have been the advantage of using stage to merge to next ? It makes it easier for us to track the heads of topics that need to be merged to

[cmake-developers] Adding ZIP and LZMA compression support to libarchive-wrapper

2010-08-12 Thread Eric Noulard
Brad, I began working on backporting my previous cmCPackArchiveGenerator component support to redesigned CPackAPI **and** the use of libarchive-wrapper (step3). The current libarchive-wrapper is missing: - support for ZIP archive which is needed - support for LZMA compression which not

Re: [CMake] OS X architecture changes interfere with CheckTypeSize()?

2010-08-12 Thread Chris Wolf
On 8/11/10 4:29 PM, Michael Wild wrote: On 11. Aug, 2010, at 22:16 , Michael Jackson wrote: On Aug 11, 2010, at 3:52 PM, Michael Wild wrote: On 11. Aug, 2010, at 21:44 , Erik Lindahl wrote: Hi, Sound technical answers from both David Clinton - I see the limitations, and why we

Re: [CMake] Obtaining info about the compiler command arguments

2010-08-12 Thread Óscar Fuentes
Óscar Fuentes o...@wanadoo.es writes: How to know the compiler arguments set by include_directories, add_definitions, etc? CMAKE_LANG_FLAGS (with and whitout the uppercase build_type suffix) doesn't contain anything that was set by the cmake commands mentioned above. I guess that the lack

[CMake] Framework + Unix tools help

2010-08-12 Thread Carlos Gonçalves
Hi, I have already looked everywhere possible (so to speak) on how to create a Framework + Unix tools as described in [1] but found no examples. So far I was able to create a Framework only [2]. I'm trying to add Mac OS X support to GeneratorRunner[3] and my current CMakeLists.txt can be

Re: [CMake] Obtaining info about the compiler command arguments

2010-08-12 Thread Michael Wild
On 12. Aug, 2010, at 15:59 , Óscar Fuentes wrote: Óscar Fuentes o...@wanadoo.es writes: How to know the compiler arguments set by include_directories, add_definitions, etc? CMAKE_LANG_FLAGS (with and whitout the uppercase build_type suffix) doesn't contain anything that was set by the

Re: [CMake] Obtaining info about the compiler command arguments

2010-08-12 Thread Óscar Fuentes
Michael Wild them...@gmail.com writes: How to know the compiler arguments set by include_directories, add_definitions, etc? CMAKE_LANG_FLAGS (with and whitout the uppercase build_type suffix) doesn't contain anything that was set by the cmake commands mentioned above. I guess that the

Re: [CMake] Obtaining info about the compiler command arguments

2010-08-12 Thread Chris Wolf
On 8/12/10 1:30 PM, Óscar Fuentes wrote: Michael Wild them...@gmail.com writes: How to know the compiler arguments set by include_directories, add_definitions, etc? CMAKE_LANG_FLAGS (with and whitout the uppercase build_type suffix) doesn't contain anything that was set by the cmake

Re: [CMake] Framework + Unix tools help

2010-08-12 Thread Chris Wolf
On 8/12/10 10:20 AM, Carlos Gonçalves wrote: Hi, I have already looked everywhere possible (so to speak) on how to create a Framework + Unix tools as described in [1] but found no examples. So far I was able to create a Framework only [2]. I'm trying to add Mac OS X support to

[CMake] Weirdness with shared library, RPATH policy on MacOS

2010-08-12 Thread Chris Wolf
I have a project which creates a shared library and a utility which uses this shared library. I would like to be able to run the utility within the build tree and also from the final install directory. I can do this, it works, but the path hard-coded path in the executable is always the build

Re: [CMake] Framework + Unix tools help

2010-08-12 Thread Carlos Gonçalves
Hi, On 2010/08/12, at 20:15, Chris Wolf wrote: On 8/12/10 10:20 AM, Carlos Gonçalves wrote: Hi, I have already looked everywhere possible (so to speak) on how to create a Framework + Unix tools as described in [1] but found no examples. So far I was able to create a Framework only

[CMake] Cmake 2.8.2 Bug under windows

2010-08-12 Thread J Decker
2.8.1 also does this I thought it was because i didn't specify the drive, because I'm pretty sure I did this a lot when first developing cmakelists for my projects... but I don't know maybe 2.8.0 did it differently and I don't have that anymore... maybe I had the cmake-gui up and kept hitting

Re: [CMake] Obtaining info about the compiler command arguments

2010-08-12 Thread Ryan Pavlik
On 8/12/10 1:51 PM, Chris Wolf wrote: On 8/12/10 1:30 PM, Óscar Fuentes wrote: Michael Wildthem...@gmail.com writes: How to know the compiler arguments set by include_directories, add_definitions, etc? CMAKE_LANG_FLAGS (with and whitout the uppercase build_type suffix) doesn't contain

Re: [CMake] Cmake 2.8.2 Bug under windows

2010-08-12 Thread Alan W. Irwin
On 2010-08-12 17:36-0700 J Decker wrote: To Reiterate steps -- mkdir /test touch /test/CMakeLists.txt mkdir /build cd /build [cmake-gui /test] or [cmake -G MinGW Makefiles /test] touch /test/CMakeLists.txt make (fails) In the past I found a subdirectory of the source tree named

[Cmake-commits] CMake branch, next, updated. v2.8.2-416-g7c87bfe

2010-08-12 Thread Eric Noulard
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via 7c87bfedca075e7be87ff7c737102088b99969ec (commit) via