Re: [CMake] Disabling INSTALL target for subdirectory

Hi Florent, thank you so much. EXCLUDE_FROM_ALL does indeed have the effect of ignoring any install() invocations from within the subdirectory. I remember stumbling across this option, but from the docs I didn't get the impression that this would affect the installation as well. Maybe the

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-128-gb6c9a85

_VERSION_MINOR 8) -set(CMake_VERSION_PATCH 20170216) +set(CMake_VERSION_PATCH 20170217) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-127-gc508fd8

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

[Cmake-commits] CMake branch, release, updated. v3.8.0-rc1-25-g2c354f4

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-218-g638f376

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-211-g0823533

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-209-ged67fe7

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-204-g5dc1ca6

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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-121-gbb4730d

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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-110-gaa18d5b

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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-106-gd1530cc

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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-112-g60b5616

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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-114-gfb3fd78

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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-117-g160083b

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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-108-g5d5be3b

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

Re: [CMake] Default CMAKE_C_FLAGS value by OS

On 02/16/2017 08:07 AM, Chuck Atkins wrote: > That being said, I do think we should revisit the use of O3 by default > given the safety issues surounding it. The following is just my opinion: In my experience if O3 fails it is a bug in the compiler, which should be fixed and somebody has to find

Re: [CMake] Default CMAKE_C_FLAGS value by OS

On 2017-02-16 10:07-0500 Chuck Atkins wrote: Hi YC, cmake version on fedora 25: 3.6.2 Fedora is specifically patching CMake in the RPM spec file to reduce the gcc flag from O3 to O2 so it's the distributuion's packaging making that change, not CMake itself. If you download and build the

Re: [CMake] [cmake-developers] how to use cmake3.7 for building fast code infedora 24

Hi Soumaia, Please keep conversations on the mailing list so others can benefit from it as well. Also, I've moved this over to the CMake Users list at cmake@cmake.org as it's a more appropriate place for this than that developers list. can you help me please how can i do this setup ? > All you

Re: [CMake] Default CMAKE_C_FLAGS value by OS

Thanks a lot for all these informations. I wrote a macro to be sure to replace all the -O3 flags ... # replace_ccxx_flag: replace compilation flags from the compiler command line # flag_orig: the flag to be replace # flag_dest: the new flag value macro(replace_ccxx_flag flag_orig flag_dest)

Re: [cmake-developers] how to use cmake3.7 for building fast code in fedora 24

Hi Soumaia, The compilers are not yet in your search path so CMake can't find them. You need to setup the intel compiler's environment first with: source /opt/intel/bin/compilervars.sh intel64 , then CMake should be able to find your compiler. -- Chuck Atkins Staff R Engineer,

Re: [CMake] Default CMAKE_C_FLAGS value by OS

Hi YC, > cmake version on fedora 25: 3.6.2 > Fedora is specifically patching CMake in the RPM spec file to reduce the gcc flag from O3 to O2 so it's the distributuion's packaging making that change, not CMake itself. If you download and build the source from cmake.org then you'll get O3 as

Re: [CMake] cmake 3.7.2 centos 7 :: kwsys.testSystemTools (Failed)

Hi Adrian, I'd suggest taking the issue up with the package maintainer. The upstream source for CMake 3.7.2 configures, builds, and passes all tests on EL7 so the problem seems to lie in how the RPM SPEC file is driving the build. -- Chuck Atkins Staff R Engineer, Scientific Computing

Re: [CMake] Disabling INSTALL target for subdirectory

Use add_subdirectory(... EXCLUDE_FROM_ALL) to prevent anything in there to be installed by default. I had the issue in one project and it did fix it for us. Also, 3rdparty libraries should be tagged like that anyway to be built only when they are used by the main targets. /Florent On Feb 16,

[CMake] cpack logging question

Hi, I am using the cpack variable CPACK_INSTALL_COMMANDS to run an extra command. (First time I do this) I have noticed that whenever the script command fails I get a log with the output in (InstallOtput.log) However when it runs correctly I have no log at all. I have tried to redirect the

[cmake-developers] how to use cmake3.7 for building fast code in fedora 24

I want to install FAST (Fast Absorption Simulation by TDDFT) code but I faced some problems. I use for this  Cmake 3.7 and siesta-4.0, and the Intel 17.X compilers, my system is linux fedora 24. FAST code is freely available at https://gforge.inria.fr/frs/?group_id=1179This is the

Re: [CMake] Default CMAKE_C_FLAGS value by OS

cmake version on fedora 25: 3.6.2 And the corresponding lines in GNU.cmake (there are some differences): # Initial configuration flags. set(CMAKE_${lang}_FLAGS_INIT "") set(CMAKE_${lang}_FLAGS_DEBUG_INIT "-g") set(CMAKE_${lang}_FLAGS_MINSIZEREL_INIT "-Os -DNDEBUG")

Re: [CMake] Default CMAKE_C_FLAGS value by OS

Hi, On 16 February 2017 at 09:06, wrote: > Hello, > > My question is related to CMAKE_*_FLAGS. > I've got a project under linux fedora 24 and, in release mode, this project > compiles with the -O2 flag. > But when I switched to other platform (ubuntu, fedora 16 - I

[CMake] Default CMAKE_C_FLAGS value by OS

Hello, My question is related to CMAKE_*_FLAGS. I've got a project under linux fedora 24 and, in release mode, this project compiles with the -O2 flag. But when I switched to other platform (ubuntu, fedora 16 - I now this one is quite old but I need to compile on this platform), this default

Re: [CMake] cmake 3.7.2 centos 7 :: kwsys.testSystemTools (Failed)

On 02/15/2017 09:04 PM, Chuck Atkins wrote: Hi Adrian, Hi! and thank you for looking into this problem! So, would this imply that cmake is not supported on EL7 because gcc does not support cxx11 ? That's not really what's happening. CMake is testing the C compiler to determine

Re: [CMake] Disabling INSTALL target for subdirectory

2017-02-16 7:59 GMT+01:00 Milan Ziegler : > Hi, > > we are using the CMake install mechanism "install(...)" to copy all > relevant files and target binaries of the product into the CMake install > prefix folder, for further packaging. So far so good. > > We are also using