[CMake] How to assign specific c, c++, fortran compiler and does CMake support Intel C/C++/Fortran Compiler?

2016-06-30 Thread Chaos Zhang
Hi, all, First, thanks for review my email. There are two questions i faced now: 1. I faced problem to assign specific compiler in CMake, and i searched for a while then i found [ CC="Foo\gcc.exe" CXX="Foo\g++.exe" cmake . ] seem work. Now i use CMake in QtCreator, is there other way i can assign

Re: [CMake] CMAKE_C_COMPILE_OBJECT vs

2016-06-30 Thread Sam Cristall
Hi Robert, Yes, we are adding the Keil C8051 compiler, which is very old and uses a very unique command line syntax compared to the others supported by CMake. Also, it's Windows only but Wine works -- so we optionally add Wine on non-Windows platforms. An example would be: wine C51.exe INCDI

Re: [CMake] CMAKE_C_COMPILE_OBJECT vs

2016-06-30 Thread Robert Maynard
Hi, Can you explain what the goal of your compilation wrappers are? Are you trying to add a new compiler? On Wed, Jun 29, 2016 at 1:41 PM, Sam Cristall wrote: > Looks like this was just a change in CMake 3.4. Updated to latest, and > everything is working. >> On Jun 28, 2016, at 5:19 PM, Sam

Re: [CMake] How do you handle recursive dependencies in CMake

2016-06-30 Thread Alan W. Irwin
On 2016-06-30 10:59+0200 Sven Baars wrote: 2) ExternalProject which will grab a repository and build it. This will not work. One of the projects I use is Trilinos, which has build of around 1GB. I don't want to pull and build that for every project I have. Also the build flags that are used so

[CMake] CPack source package install location

2016-06-30 Thread cen
Hi I have a very standard CPack configuration for deb package. I have two questions: 1. I generate the deb with: cpack --config CPackConfig.cmake -G "DEB" This is supposedly a binary package but when I install it on the machine I see header files being installed in /usr/include. Is this no

Re: [CMake] How do you handle recursive dependencies in CMake

2016-06-30 Thread Sven Baars
Hey again Marcel, Your reply got me thinking. I just checked again, and found that I just have to set the LIBRARY_PATH correctly as well. After that everything seems to work. Apparently this was not done in the right way. Since I have to use PATH anyway to find the FoobarConfig.cmake files, it is

Re: [CMake] CMake 3.6.0-rc4 now ready for testing!

2016-06-30 Thread Brad King
On 06/29/2016 05:05 PM, Hendrik Sattler wrote: >> * The "InstallRequiredSystemLibraries" module learned a new >> "CMAKE_INSTALL_UCRT_LIBRARIES" option to enable app-local deployment >> of the Windows Universal CRT libraries with Visual Studio 2015. > > Maybe the help should note that this is on

Re: [CMake] How do you handle recursive dependencies in CMake

2016-06-30 Thread Sven Baars
Hey Marcel, They are indeed always set correctly, and for this reason, find_package is also always able to find these packages, which is great, and this is why I love using CMake, but then it still happens that when you don't explicitly use find_package, so in this case I don't use find_package(A)

Re: [CMake] How do you handle recursive dependencies in CMake

2016-06-30 Thread Marcel Loose
Hi Sven, Sorry to chime in so late. I was wondering, since you're mentioning large computer clusters, don't you use the "module" system to select which versions of which packages you want to use? If so, then (I assume) your PATH and LD_LIBRARY_PATH environment variables will have been set such tha

Re: [CMake] How do you handle recursive dependencies in CMake

2016-06-30 Thread Sven Baars
I don't think this is a solution to the problem, since then it seems like the build will still fail for all our users unless they also build all their packages from inside hunter. If I wanted it to work just for myself I could just use hardcoded paths. The problem is that I want a portable way such

Re: [CMake] How do you handle recursive dependencies in CMake

2016-06-30 Thread Nicholas Braden
If find_project is not enough, and ExternalProject's only problem is build duplication, then I think it makes sense to consider a CMake-based dependency manager such as hunter: https://github.com/ruslo/hunter On Thu, Jun 30, 2016 at 3:59 AM, Sven Baars wrote: > This is a reply to the options tha

[CMake] ctest: how to include pre- and post- processing commands

2016-06-30 Thread TS
Hi, Apologize if I sent this twice. Is it possible to have a ctest which involves preprocessing as well as postprocessing. The code to test is myCode.exe, which writes an output file. PASS or FAIL is the result of comparison of output against reference data. Currently I use two add_tests:

Re: [CMake] How do you handle recursive dependencies in CMake

2016-06-30 Thread Sven Baars
Hey Ray, For myself it is not a big problem either, but I don't want to tell users of my libraries that they have to look up how the administrators at their supercomputing facility compiled 20 other libraries so they can set their environment variables in the right way, while at the same time mak

Re: [CMake] How do you handle recursive dependencies in CMake

2016-06-30 Thread Raymond Wan
Hi Sven, On Thu, Jun 30, 2016 at 6:40 PM, Sven Baars wrote: > So let's take Trilinos as an example, which is quite a big library, > which depends on a lot of libraries as well. In every project that > builds upon it (but does not even use functionality of any libraries), > we would have to set:

Re: [CMake] How do you handle recursive dependencies in CMake

2016-06-30 Thread Sven Baars
Hi Ray, This still has the same problem. If I use FindBoost in project B, I can use BOOST_ROOT to be able to find it. This works fine. Now, if I try to compile project C, I can set B_ROOT for FindB, but then Boost will not be found, because it is not in B_ROOT, so project C will not compile. That

Re: [CMake] How do you handle recursive dependencies in CMake

2016-06-30 Thread Raymond Wan
Hi Sven, On Thu, Jun 30, 2016 at 4:59 PM, Sven Baars wrote: > This is a reply to the options that Ray gave. Here I will use the > package dependencies C -> B -> A{1,2}: Well, I presented some options to you. Perhaps there are others, but if none of them are right for you then there's nothing

Re: [CMake] How do you handle recursive dependencies in CMake

2016-06-30 Thread Sven Baars
This is a reply to the options that Ray gave. Here I will use the package dependencies C -> B -> A{1,2}: 1) The "ad-hoc" method I first mentioned by setting CMAKE_LIBRARY_OUTPUT_DIRECTORY. As far as I understand, this would mean that every user of all of the different projects would have to be f