[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 this with different versions of CMake source code - also on Windows host using Cygwin, but an update to the latest source to git/master resolved it on Windows+cygwin side. Anyways with travis-ci on macosx it's still not working. You can check out the whole log file here: https://s3.amazonaws.com/archive.travis-ci.org/jobs/22760491/log.txt Any pointers? Best Regards, Andrew Csizmadia -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
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 check out the whole log file here: https://s3.amazonaws.com/archive.travis-ci.org/jobs/22760491/log.txt The first error I see in that log comes before the above error: CMake Error at Utilities/cmlibarchive/CMakeLists.txt:15 (FILE): file STRINGS file /Users/travis/build/vpmedia/crossbridge/build/mac/cmake/Utilities/cmlibarchive/build/version cannot be read. That file is supposed to be part of the source tree. Is it there? -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
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 compiler, eng/mx libraries, matlab program
- proper version testing
- making use of FindPackageHandleStandardArgs for the version + components +
variables
Thanks. I'll take another look through the module when I get a chance.
You should be able to make further progress with the comments below.
I avoided using the new syntax of cmake 3.x because I am still using 2.8.12
and I also would like ppl to get this new package and run it on older
versions.
If it is going to be added upstream it needs to have the appropriate
documentation syntax. You can still use comment blocks starting in
'#' on every line as most modules currently do and it will work with
2.8.12.
The current solution I am seeing now is to do a test on a cmake
script that does the job of launching the command and flushing
the log file onto the console.
Many of our tests use cmake -P to run a cmake script that performs
the test inside. You can use -Dvar=${val} before the -P option to
pass options to the script, such as $TARGET_FILE_DIR:my_mex_target.
- Is it ok if we create log files of leave them onto the disk?
Yes, but they should be inside the CMake build tree so there are
no side effects left when the tree is removed.
two modes for querying the registry: x86 and x64 modes.
This is not very clear to me what I should do on that:
The find_library command expands registry values with the view
that matches the target architecture. The find_program command
looks at the matching architecture first and then the other one:
http://cmake.org/gitweb?p=cmake.git;a=blob;f=Source/cmFindCommon.cxx;hb=v3.0.0-rc3#l347
This is how most of the modules deal with the difference. I'm
not familiar enough with matlab to say what should be done here.
Thanks,
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
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 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 check out the whole log file here: https://s3.amazonaws.com/archive.travis-ci.org/jobs/22760491/log.txt The first error I see in that log comes before the above error: CMake Error at Utilities/cmlibarchive/CMakeLists.txt:15 (FILE): file STRINGS file /Users/travis/build/vpmedia/crossbridge/build/mac/cmake/Utilities/cmlibarchive/build/version cannot be read. That file is supposed to be part of the source tree. Is it there? -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[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 [1] is: CMake Internal Error (please report a bug): Missing cmGeneratorTarget instance! CMake Error at /srv/jenkins/install/linux/x86_64/g++/latest- qt4/kde/kdelibs/inst/share/apps/cmake/modules/KDE4Macros.cmake:1010 (add_executable): Error evaluating generator expression: $TARGET_OBJECTS:kdevclangcodecompletion Objects of target kdevclangcodecompletion referenced but no such target exists. Call Stack (most recent call first): /srv/jenkins/install/linux/x86_64/g++/latest- qt4/kde/kdelibs/inst/share/apps/cmake/modules/KDE4Macros.cmake:862 (kde4_add_executable) tests/CMakeLists.txt:24 (kde4_add_unit_test) The relevant code is here: [2] I see that there was some discussion wrt this on the cmake ML, [3], but actually I lack the CMake foo in order to understand this discussion's implications. At any rate, I don't think the above behavior is intended, is it? Greets [1] http://build.kde.org/view/kdevelop/job/kdev-clang_master/5/console [2] http://quickgit.kde.org/?p=kdev-clang.gita=treehb=22e0c136a252813ff0732eba25bda79d89173682 [3] http://public.kitware.com/pipermail/cmake-developers/2014-February/009838.html -- Kevin Funk -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
