Re: [CMake] CMake and user friendliness
Please install cmake bash_completion and then it will be easy as typing: cmake -D --Adam -- 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/mailman/listinfo/cmake
[CMake] VxWorks and CMake
Has anyone used CMake for VxWorks environments? As far as I can see, there is no VxWorks support yet in the cmake distribution. The cleanest way seems to create a VxWorks.cmake in the Modules/Platform directory that specifies the OS specifics. Also a create a file VxWorks-toolchain.cmake that specifies the details of the compiler (gnu) and other tools. A copy of a working platform file and toolchain file would be great, but any useful hint is appreciated. Kind regards, Alexis Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. -- 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/mailman/listinfo/cmake
Re: [CMake] CMake and user friendliness (Drew DeVault)
Well, it depends on who you are expecting the "user" to be and what their background is. I always configure new cmake buiulds with cmake-gui or ccmake, which I find to be much easier than auto tools, because the documentation and ability to set options is in the same place--one stop shopping. No need to read about a number of options, then try to remember which ones to set, and to what. Just read the doc string of each option one at a time and then change its value from the default if desired. my $0.02 -Zaak Izaak Beekman === (301)244-9367 Princeton University Doctoral Candidate Mechanical and Aerospace Engineering ibeek...@princeton.edu UMD-CP Visiting Graduate Student Aerospace Engineering ibeek...@umiacs.umd.edu ibeek...@umd.edu -- 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/mailman/listinfo/cmake
[CMake] CMake course in Carrboro, NC October 20, 2014.
Kitware is hosting a CMake training course, titled “Project Lifecycle Management with the CMake Family of Tools,” in Carrboro, NC. The course will be held on October 20, 2014. Through the course, you will learn how to create a build system for your C/C++/Fortran project using CMake, CPack, CTest, and CDash. This course covers in-depth how CMake works and how you can efficiently write CMake scripts for small to large projects. The course also covers unit testing with CTest, packaging with CPack and continuous integration with CDash. Additional details and registration information are available on the Kitware website. The price of the course via early registration is $650. Early registration is available through October 8, 2014. The price of the course via regular registration is $815. In addition, Kitware will be hosting a “Scalable Visualization using VTK, ParaView, & Python” training course on October 21, 2014. This course will also be hosted on Carrboro. For more information, please visit http://www.kitware.com/products/protraining.php. -Bill -- 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/mailman/listinfo/cmake
[CMake] ExternalProject_Add dependency graph (dot/graphviz?) ?
Hi, CMake has graphviz output capability for dependency within a project. Is there a way to graph dependency at the ExternalProject_Add() level ? Cheers -- Nicholas Yue Graphics - RenderMan, Visualization, OpenGL, HDF5 Custom Dev - C++ porting, OSX, Linux, Windows http://au.linkedin.com/in/nicholasyue https://vimeo.com/channels/naiadtools -- 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/mailman/listinfo/cmake
Re: [CMake] Ninja generator fail for QNX on Windows
On 9/22/2014 1:45 AM, Cristian Adam wrote: On QNX side, thins are not as good. First, in order to compile the project I had to apply this patch [1], provided by Stephen Kelly. And now the "fail" part for QNX, the second subsequent build doesn't say "ninja: no work to do" instead it starts compiling, taking as much as 70% of the original clean build time :( Now I don't know who to blame cmake or ninja? There is no way to really tell what is going on from what you have posted. What about the third time you run ninja does it have nothing todo? You can run: ninja -d explain to see why ninja wants to run things. Sounds like some input files are getting changed during your build for QNX for some reason. -Bill -- 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/mailman/listinfo/cmake
Re: [CMake] Ninja generator fail for QNX on Windows
On Mon, Sep 22, 2014 at 5:40 PM, Bill Hoffman wrote: > On 9/22/2014 1:45 AM, Cristian Adam wrote: > >> >> On QNX side, thins are not as good. First, in order to compile >> the project I had to apply this patch [1], provided by Stephen Kelly. >> >> And now the "fail" part for QNX, the second subsequent build >> doesn't say "ninja: no work to do" instead it starts compiling, >> taking as much as 70% of the original clean build time :( >> >> Now I don't know who to blame cmake or ninja? >> > There is no way to really tell what is going on from what you have > posted. What about the third time you run ninja does it have nothing todo? > For the 3rd time, 4th time etc. same thing happens. > > You can run: > ninja -d explain > to see why ninja wants to run things. Sounds like some input files are > getting changed during your build for QNX for some reason. > > -Bill > > "-d explain" parameter gives for lots of files (probably all) in the project (headers, source files, object files, static libraries, executables) "is dirty" This means that ninja's method of detecting if a file has been changed doesn't quite work for QNX. Or is this being set by cmake? Some compiler flag which needs a -Wc, or -Wp prefix? Cheers, Cristian. -- 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/mailman/listinfo/cmake
[CMake] How to make the construction and reuse of CMake lists safer?
Hello, The build tool "CMake" supports also the data processing for lists to some degree. http://www.cmake.org/cmake/help/v3.0/manual/cmake-language.7.html#lists I notice that CMake scripts are also provided by some software libraries so that corresponding settings can be automatically determined by the command "find_package". http://www.cmake.org/cmake/help/v3.0/command/find_package.html I have also noticed that a lot of libraries provide only a single file for source file inclusion and linking. It seems that appropriate quoting of variables is often forgotten for this use case, isn't it? How many library build scripts construct variables with suffixes like "_INCLUDE_DIRS" and "_LIBRARIES" which contain two list elements at least? Can any special build function help to make the required data processing safer here? How can it be achieved that contents are properly escaped? Regards, Markus -- 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/mailman/listinfo/cmake
[CMake] Problems resolving PTHREAD_* symbols.
We have some semaphore code that has conditional compilation based on
#defines in config.h. We're having problems with resolving the various
PTHREAD_* symbols to get the correct values in config.h. Our first attempt
at this (done on Linux) used
check_symbol_exists(PTHREAD_MUTEX_RECURSIVE "pthread.h"
HAVE_PTHREAD_MUTEX_RECURSIVE)
This did not pick the symbol up correctly. Eventually, we got things
to work by using
check_c_source_compiles("#include
int main(int arg, char **argv) {
int tryme;
tryme = PTHREAD_MUTEX_RECURSIVE;
return 0;}"
HAVE_PTHREAD_MUTEX_RECURSIVE)
and got everything to build cleanly. Over the weekend, we tried
building on OSX for the first time, and once again, we were not
resolving that these symbols existed. What are we missing here? Is
there some technique we should be using that will work across the
various platforms?
Rick
--
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/mailman/listinfo/cmake
[CMake] Building CTestDashboardTargets Experimental, etc From Xcode Fails
Hello! I am trying to build my Dashboard targets from inside Xcode, and it keeps failing! Here is the build log... echo "" /usr/local/Cellar/cmake/3.0.2/bin/ctest -C Debug -D Experimental Site: macpat Build name: Darwin-clang++ Create new tag: 20140922-1554 - Experimental Configure project Each . represents 1024 bytes of output Size of output: 3K Build project Each symbol represents 1024 bytes of output. '!' represents an error and '*' a warning. .make: *** [/Volumes/Users/patrick/Projects/skeleton/xcode_build/CMakeFiles/Experimental] Interrupt: 2 Building these targets with Unix Makefiles works just fine. Running "/usr/local/Cellar/cmake/3.0.2/bin/ctest -C Debug -D Experimental” manually in the Xcode build directory works just fine. Any ideas?! Thanks, Patrick -- 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/mailman/listinfo/cmake
Re: [CMake] Ninja generator fail for QNX on Windows
On 9/22/2014 11:53 AM, Cristian Adam wrote: "-d explain" parameter gives for lots of files (probably all) in the project (headers, source files, object files, static libraries, executables) "is dirty" This means that ninja's method of detecting if a file has been changed doesn't quite work for QNX. Or is this being set by cmake? Some compiler flag which needs a -Wc, or -Wp prefix? I would look close at the output of explain: For example, in building cmake: If I start with an up to date build, and do this: touch ../cmake/Source/cmake.cxx ninja -d explain I get something like this: Creating library bin\ctest.lib and object bin\ctest.exp ninja explain: output Source\CMakeFiles\CMakeLib.dir\cmake.cxx.obj older than most recent input C:\Users\hoffman\Work\My Builds\cmake\Source\cmake.cxx (433106324 vs 433106443) ninja explain: Source\CMakeFiles\CMakeLib.dir\cmake.cxx.obj is dirty ninja explain: Source\CMakeLib.lib is dirty ninja explain: Source\CMakeLib.lib is dirty ninja explain: bin\cmake.exe is dirty ninja explain: Source\CMakeLib.lib is dirty ninja explain: bin\cmcldeps.exe is dirty ninja explain: Source\CMakeLib.lib is dirty ninja explain: bin\cpack.exe is dirty ninja explain: Source\CMakeLib.lib is dirty ninja explain: bin\ctest.exe is dirty ninja explain: Source\CMakeLib.lib is dirty ninja explain: Tests\CMakeLib\CMakeLibTests.exe is dirty ninja explain: Source\CMakeLib.lib is dirty ninja explain: Tests\CTestTestMemcheck\memcheck_fail.exe is dirty ninja explain: Source\CMakeLib.lib is dirty ninja explain: Tests\CTestTestMemcheck\BC.exe is dirty ninja explain: Source\CMakeLib.lib is dirty ninja explain: Tests\CTestTestMemcheck\purify.exe is dirty ninja explain: Source\CMakeLib.lib is dirty ninja explain: Tests\CTestTestMemcheck\valgrind.exe is dirty Maybe if you looked at the very first older than in your output instead of the dirty ones it might tell you what ninja thinks is out of date. Could be some sort of path issue that has something to do with the way the paths are constructed. Again, without seeing the details I can only guess. Do makefiles work for you? What if you try the "Unix Makefiles" generator on the same machine does it have the same problem? -Bill -- 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/mailman/listinfo/cmake
