[cmake-developers] cmake building from source with travis-ci (osx host)

Hi, I would like to build CMake from source for a customized toolchain using Travis-CI, but I can't solve the following issue (or related to that): CMake Error at Utilities/cmlibarchive/CMakeLists.txt:316 (CHECK_HEADER_DIRENT): Unknown CMake command CHECK_HEADER_DIRENT. I've experienced

Re: [cmake-developers] cmake building from source with travis-ci (osx host)

On 04/11/2014 08:59 AM, Andras Csizmadia wrote: I would like to build CMake from source for a customized toolchain using Travis-CI, but I can't solve the following issue (or related to that): CMake Error at Utilities/cmlibarchive/CMakeLists.txt:316 (CHECK_HEADER_DIRENT): [snip] You can

Re: [cmake-developers] Introduction and volunteering for the Matlab package

On 04/09/2014 05:09 PM, Raffi Enficiaud wrote: After Brad’s feedbacks, I did the following: - fix + clean the documentation - remove any unwanted message, added a variable in order to print diagnostic - cleaned variable/function names - changed macros to function - added components: mex

Re: [cmake-developers] cmake building from source with travis-ci (osx host)

Hi! Thanks, I feel a bit stupid didn't noticing this : ) - the build folder were under .gitignore for sure, so now testing the fixed version. Thank you for the response! Best, Andrew On 2014.04.11. 15:23, Brad King wrote: On 04/11/2014 08:59 AM, Andras Csizmadia wrote: I would like to

[cmake-developers] Problems with CMake-master and OBJECT libraries

Hey guys, Recently I've started porting internal KDevelop libraries to OBJECT libraries. The CMake code I've written seems to work fine with v2.8.12.2 (what I have on my system, locally) but apparently fails with recent CMake-master (which is installed on the KDE CI). The error I get on the CI

[CMake] Custom Commands and Environmnt Settings for PATH and LD_LIBRARY_PATH

Hi! Had an issue with cmake custom commands - was able to solve it after serveral hours. But i think this is realy an issue for an improvement I. What i wanted to do: I wanted to add a simple custom command add_custom_command( OUTPUT out COMMAND mycommand ... ) mycommand

Re: [CMake] Custom Commands and Environmnt Settings for PATH and LD_LIBRARY_PATH

On 04/11/2014 11:32 AM, Jörg Kreuzberger wrote: After reading serveral threads i ended in this solution - create a batch/shell script for the command i want to start. This ensures path modifications are local. Creation is done via a configure_file step I would run a cmake script with

Re: [CMake] Custom Commands and Environmnt Settings for PATH and LD_LIBRARY_PATH

ok, biggest hint here was the tip for $TARGET_FILE:... This was new to me (am new to cmake at all). Thanks. My major problem is still passing the additonal PATH elements to the cmake script, cause they will always expanded in an space seperated list. So if i add

Re: [CMake] Custom Commands and Environmnt Settings for PATH and LD_LIBRARY_PATH

On 04/11/2014 12:56 PM, Jörg Kreuzberger wrote: ok, biggest hint here was the tip for $TARGET_FILE:... This was new to me (am new to cmake at all). Thanks. My major problem is still passing the additonal PATH elements to the cmake script, cause they will always expanded in an space seperated

[CMake] CMake Configure error: Width with l64 failed with result: 1

Hi. I'm new with CMake trying to generate the ITK libs. I've downloaded CMake version 2.8.12 and ITK 4.5.1, both, for Windows. I've let only ITK_BUILD_DEFAULT_MODULES in CMake. I press Configure and I get the following: Enabled ITKZLIB, requested by ITK_BUILD_DEFAULT_MODULES. Checking for

[CMake] Explanation....

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have run on behaviour of cmake that I really do not understand (even if I have clues)... This is probably stupid, but I'm puzzled... The attached CMakeLists.txt gives the following output: ::-B-:: - This shows that B is indeed parsed as OPTIONAL

[CMake] Custom-target is in Visual Studio not added to default build in case custom-target is not part of sub-directory tree of project (solution)

Hi, Summary: What is the reason that custom-targets that are needed by a project and its dependencies are not added to the default-build in Visual Studio in case that target is defined out-side the sub-directory tree of this project? I have the following directory-structure: root/A - in this

Re: [CMake] Custom Commands and Environmnt Settings for PATH and LD_LIBRARY_PATH

ok, finaly got it working. Thanks for your great support. -Ursprüngliche Nachricht- Von:Nils Gladitz nilsglad...@gmail.com Gesendet: Fr 11.04.2014 13:12 Betreff:Re: AW: [CMake] Custom Commands and Environmnt Settings for PATH and LD_LIBRARY_PATH An: Jörg Kreuzberger

[CMake] Resource filters in generated eclipse projects

Hello! Has anyone figured out a good way to preserve resource filters across a cmake-rerun when using an eclipse generated project? The eclipse re-indexing time on one of my projects has gotten a bit out of hand. By setting resource filters to have eclipse ignore the [Targets] and [Subprojects]

[CMake] Why does build_command() return a command that ignores errors?

build_command( BUILD_COMMAND CONFIGURATION ${CMAKE_BUILD_TYPE} PROJECT_NAME something TARGET install ) results in 'make -i install' so if there are errors in compiling, it installs anyway, obliterating the errors. So Why is there an ignore error flag on BULD_COMMAND? -- Powered by

Re: [CMake] Why does build_command() return a command that ignores errors?

Here's a guess: For dashboard submissions, some prefer to see *as many errors as possible* at once in one go, so as to have the least turnaround time in fixing errors on a remote system without having direct access to that system. To accommodate such a preference, the default flags have

Re: [CMake] Support for building of OCaml software?

How do you think about to extend configuration checks for OCaml compiler variants? What do you mean by OCaml compiler variants ? - bytecode - Will any implementation for native code generation apply also aggressive software optimisations? - interfaces - librarian (linker?) Would you also

[CMake] CMake and Xcode and Intel Fortran...

Using Xcode 5.1.1, CMake 2.8.12 and Intel Fortran 15 beta, trying to use Xcode for development instead of Windows and having no luck. What, if any, is the relationship between CMakeLists.txt and the order of compilation under XCode? I don't see that the Xcode generator does any dependency

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc3-2219-g35435b7

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 35435b77a28c83fd7fde8fdbebf7f96279e7d7ee (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.0-rc3-550-g7ae1399

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, master has been updated via 7ae13b83ffd54c3ab1a1b7c44b95f67c5785 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.0-rc3-543-g0c08da9

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, master has been updated via 0c08da9912ab8211339098ba87047a3d0d507cda (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.0-rc3-546-g76425a6

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, master has been updated via 76425a62192ddad23c84e3022b400dc3c5be0ace (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.0-rc3-556-ga6fee73

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, master has been updated via a6fee73dacdb8bd6e09e238a81b62ba303e1 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.0-rc3-552-g893843c

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, master has been updated via 893843ce21451d7cb8f1aaf3ae14477bfc351fa8 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.0-rc3-548-g61ac6d6

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, master has been updated via 61ac6d640134b4b0131af5147ca90b1f4dd37650 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc3-2230-g621235a

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 621235ab70fb796ff0bbe675ef09b742ea7dcc34 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc3-2232-g67eb10b

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 67eb10b2c75a477565e91964e0a1573e71d61999 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc3-2237-g7d55b4a

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 7d55b4a5ed19c61c7ef1a8cb3fa47dca7f574013 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.0-rc3-560-g3927747

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, master has been updated via 3927747547a5ddc9495cc4796876e207f2cae811 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.0.0-rc3-20-g1c58719

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, release has been updated via 1c5871984a33922e3ec229ba28bacf0848e9b003 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc3-2240-g20944b4

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 20944b4c8b072b8c5430f70a52dd1b20fe5dd4ff (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc3-2242-g6834f7b

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 6834f7bf399ce3b569c03ae6c7f0018bce0866ba (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc3-2244-g348e648

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 348e64856fe77044d810da955c3267e99f475246 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc3-2250-g38f8b0a

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 38f8b0a9484a39d9acbce3f9efb5729c12566ea4 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.0-rc3-561-g973b3e7

20140411) +set(CMake_VERSION_PATCH 20140412) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake