Re: [CMake] Linker error when building 3.8.0-rc4 on Linux

Can confirm that this happens with the latest source from Github as well. -- 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

[CMake] Linker error when building 3.8.0-rc4 on Linux

Trying to build CMake 3.8.0-rc4 from source on Ubuntu 16.10 gives the following output: $ make [ 2%] Built target cmsys [ 3%] Built target cmsysTestDynload [ 4%] Built target cmsys_c [ 4%] Built target cmsysTestProcess [ 4%] Built target cmsysTestSharedForward [ 5%] Built target cmsysTestsC

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc4-617-g60dde28

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 60dde287e71efbad71b107902991098a6c77556d (commit) from

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-631-geddbd87

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 discards baa8c9c3568c808b6217c6548a1d927cf85475ab (commit) discards

[CMake] How to exclude some files from building?

There are some files I do not want to build if the specified condition was ture. For example, for testing, I want build a new file witch include a main entry just for testing; if not, a new file would be compile for normal task. I do not want to write two main entries in the same file just using

Re: [CMake] Building third party libraries along with normal targets

Miller, Thank you for your input; I'm hoping we can use it to improve our description of Spack at http://spack.io . I'm cross-posting to the Spack list, maybe someone there can add to this. https://github.com/LLNL/spack/issues/2115 There has been talk of a comparison; but I'm not familiar

[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc4-630-gbaa8c9c

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, nightly has been updated discards fcb2d3e17b5cfc3c0a98dad59a56e0022ba92541 (commit) discards

[Cmake-commits] CMake branch, nightly-master, updated. v3.8.0-rc4-616-g3e2f6bd

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-630-gbaa8c9c

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

[CMake] Creating List file outputs from each source file

Hi, I hope this is a simple question and I'm just missing something fundamental. I'm trying to emulate a binary build manager for an embedded Cortex-M0 target using a CMake project. I'm having some trouble figuring out how to generate list files for each dependency of my executable target. The

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-625-g83fb339

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 discards 31343f9a91b19a4015b4decd56b757cb2109718a (commit) discards

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-625-g31343f9

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 discards b68e609a9c620ecfd64b51e4d86aa70ec641aa70 (commit) discards

[CMake] FindThreads and toolchains

I am using CMake 3.7.2 and playing around with the FindThread finder. The following simple CMakeLists.txt works fine on various compilers: GCC, clang, MSVC (tried 2013 and 2015). CMAKE_MINIMUM_REQUIRED( VERSION 3.1 ) ADD_EXECUTABLE( mythread main.cpp ) SET( THREADS_PREFER_PTHREAD_FLAG TRUE )

[cmake-developers] [ANNOUNCE] CMake 3.8.0-rc4 now ready for testing!

I am proud to announce the fourth CMake 3.8 release candidate. https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.8 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.8/release/3.8.html Some of the more significant

[CMake] [ANNOUNCE] CMake 3.8.0-rc4 now ready for testing!

I am proud to announce the fourth CMake 3.8 release candidate. https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.8 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.8/release/3.8.html Some of the more significant

Re: [CMake] Building third party libraries along with normal targets

30.03.2017, 18:15, "Miller Henry" : > I have found the following projects which all seem to do some variation of a > meta build so that you can build multiple projects that depend on each other > and manage dependencies. (there are a couple others that seem to not be

Re: [CMake] Building third party libraries along with normal targets

I have found the following projects which all seem to do some variation of a meta build so that you can build multiple projects that depend on each other and manage dependencies. (there are a couple others that seem to not be maintained as well) https://gradle.org/ https://bazel.build/

Re: [CMake] ExternalProject_Add ... output directy (sln file directory)

BTW, I notice this too, if I use the following command line with an empty cmakelists.txt file : cmake -G "Visual Studio 15 2017 Win64" And it also generate the .sln (and other files) in the same folder, but I don't request to build such a solution ! right ? In reality, I only need a

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-621-gb68e609

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

Re: [CMake] ExternalProject_Add and include_external_msproject dynamic duo... but what if their powers combined?

Apologies for not responding sooner... this fell off my radar and I found it in my email. On Thu, Jan 12, 2017 at 6:29 AM, David Cole wrote: > Why not just use a BUILD_COMMAND which builds the VS project using the > msbuild command line directly? Do you have an example of this? Even if this

Re: [CMake] Building third party libraries along with normal targets

I do this using the spack autobuilder. Only problem is it doesn't run on windows. Maybe Conda? On Mar 30, 2017 9:45 AM, "Robert Dailey" wrote: > On Thu, Mar 30, 2017 at 3:42 AM, Tamás Kenéz > wrote: > > An alternative to the CMake superbuild:

[Cmake-commits] CMake annotated tag, v3.8.0-rc4, created. v3.8.0-rc4

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 annotated tag, v3.8.0-rc4 has been created at 52edf05b496638c949c9daec3aef51da33793ca5 (tag) tagging

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-642-g3e2f6bd

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 discards bcaac6a864e64fe3b6900051cc6b0fbf241fb6fb (commit) discards

[Cmake-commits] CMake branch, release, updated. v3.8.0-rc3-26-g9e32b88

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 9e32b88784e5e0f14258597fde162fcaf6290fea (commit) from

Re: [CMake] ExternalProject_Add ... output directy (sln file directory)

Do give it a BINARY_DIR, but do NOT give it a BUILD_COMMAND. Giving it an empty BUILD_COMMAND means "do nothing" for the build step and using "cmake --build ./LibraryBuild" does not work unless cmake is in your PATH, and with a Visual Studio solution, you also need to specify "--config Release" or

[CMake] ExternalProject_Add ... output directy (sln file directory)

Hi, I'm currently using one CMakeLists.txt file that will execute an external CMakeLists.txt (and dependency). For this I use the ExternalProject_Add command, but I can't find a way to specify where the ".sln" file will be generated. I have also created StackOverflow question here with

Re: [CMake] Building third party libraries along with normal targets

On Thu, Mar 30, 2017 at 3:42 AM, Tamás Kenéz wrote: > An alternative to the CMake superbuild: leave your actual project intact. > Simply create a separate shell script which builds all the dependencies (by > running cmake commands). Or, if you do like the ExternalProject

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-643-gbcaac6a

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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc3-640-gc268850

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

[Cmake-commits] CMake branch, release, updated. v3.8.0-rc3-25-g18eeed4

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-640-gc268850

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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc3-634-g1cc918a

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-636-gce9c4b4

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 discards bd55c2b5e748d753817f0079994fe38f2d1a6366 (commit) discards

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc3-617-g7bb8b38

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-634-gbd55c2b

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 discards 9da9936ec88418db8ff9e3c24dd9cef555bf4e1b (commit) discards

Re: [cmake-developers] Targets with same name in different projects

On 03/30/2017 07:13 AM, Tobias Hunger wrote: > So I was wondering: Is this even allowed? The CMake manual says target > names must be unique within a project. It shouldn't be allowed. See CMP0002 [1]. -Brad [1] https://cmake.org/cmake/help/v3.8/policy/CMP0002.html -- Powered by

[cmake-developers] Targets with same name in different projects

Hello, I found a project recently which looks odd in the Qt Creator project tree. Looking into it I found that this project has several projects defined and two of those define the same target (same SOURCE file, same name, etc.). It seems like both projects somehow include the same CMakeLists.txt

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-634-g9da9936

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 discards 8484d6edc18a7f269be41f2f7adca80f2a0c369e (commit) discards

Re: [CMake] Building third party libraries along with normal targets

An alternative to the CMake superbuild: leave your actual project intact. Simply create a separate shell script which builds all the dependencies (by running cmake commands). Or, if you do like the ExternalProject stuff, create a superbuild which builds only the dependencies. Tamas On Thu, Mar