Re: [CMake] How to exclude some files from building?

Oh, I got it. I think the first method was so cool. Thank you very much. At 2017-03-31 14:10:12, "Domen Vrankar" wrote: 2017-03-31 4:41 GMT+02:00 kipade : There are some files I do not want to build if the specified condition was ture. For example,

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

Also, I have try with a sample, just a main and a lib. But it seems that the lib CMakeLists.txt file is not called ! The project is created, but it does not point to the source code by example and the "message" are not displayed in the console too ! The download link :

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

On 2017-03-31 09:12+0200 Nils Gladitz wrote: On 03/31/2017 09:04 AM, ウルヰ wrote: To disable OpenSSL e.g. "cmake ... -DCMAKE_USE_OPENSSL=false" or "bootstrap ... -- -DCMAKE_USE_OPENSSL=false". What would be the ramifications of building CMake without OpenSSL? As far as I am aware it would

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

On 03/31/2017 07:46 AM, ウルヰ wrote: ../Utilities/cmlibarchive/libarchive/libcmlibarchive.a(archive_hmac.c.o): In function `__hmac_sha1_init': archive_hmac.c:(.text+0x25): undefined reference to `HMAC_CTX_new' ../Utilities/cmlibarchive/libarchive/libcmlibarchive.a(archive_hmac.c.o): In function

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

On 03/31/2017 11:54 AM, Alan W. Irwin wrote: Hi Nils: And use of ExternalProject_Add, etc. In other words, this is a pretty crippling restriction for users with Linux distributions (such as the quite recent Ubuntu 2016.10 of the original poster) that do not yet give access to libssl version

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

[about shell script portability] We do use shell-scripts on Windows since git-bash comes with git for free. Our workflow is centered around the command-line (git-bash for Windows) and you can run shell scripts in git-bash, that's why compatibility is not a problem. All our scripts and workflows

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

On 2017-03-31 14:00+0200 Nils Gladitz wrote: On 03/31/2017 11:54 AM, Alan W. Irwin wrote: Hi Nils: And use of ExternalProject_Add, etc. In other words, this is a pretty crippling restriction for users with Linux distributions (such as the quite recent Ubuntu 2016.10 of the original poster)

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

On 31.03.2017 22:44, Alan W. Irwin wrote: Therefore, from the sidelines I am encouraging you guys to be extraordinarily careful about this particular issue; e.g., by attempting to to confirm this CMake-3.8.0-rc4 issue independently for Ubuntu 16.10. FWIW I tried reproducing it from within an

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

> I suggest you try the experiment of using the system version of > libcurl instead (which also supplies SSL capability). For example, my > Linux distribution is Debian Stable which only installs libssl 1.0.1. > And for that case when I tried the bootstrap method with the > --system-curl option

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

> To disable OpenSSL e.g. "cmake ... -DCMAKE_USE_OPENSSL=false" or "bootstrap > ... -- -DCMAKE_USE_OPENSSL=false". What would be the ramifications of building CMake without OpenSSL? -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

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

On 03/31/2017 09:04 AM, ウルヰ wrote: To disable OpenSSL e.g. "cmake ... -DCMAKE_USE_OPENSSL=false" or "bootstrap ... -- -DCMAKE_USE_OPENSSL=false". What would be the ramifications of building CMake without OpenSSL? As far as I am aware it would mean no "https://; support in curl which would

Re: [CMake] How to exclude some files from building?

2017-03-31 4:41 GMT+02:00 kipade : > 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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-635-gcb99a24

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-633-g20e7a6d

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

Re: [cmake-developers] Problems with CTestTestParallel

On 03/10/2017 10:32 AM, Brad King wrote: > On 03/10/2017 06:34 AM, Rolf Eike Beer wrote: >> I've attached the complete build dir of that test, maybe anyone >> has a clue what is going on there > > The `Testing/Temporary/LastSubmit_20170310-1035.log` shows errors > submitting to CDash. However,

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-637-g38bbe41

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-641-g5aa11aa

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-639-g9ec9018

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-643-ged76ca4

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

[Cmake-commits] CMake branch, nightly-master, updated. v3.8.0-rc4-631-gc791fb1

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

[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc4-643-ged76ca4

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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc4-632-g20326cf

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 20326cff8f8a7e469c481767074e343006d7d901 (commit) from

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-644-g37df168

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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc4-631-gc791fb1

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

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

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