Re: [CMake] FindBoost not finding MinGW libraries

15 ноя 2016 г. 7:40 PM пользователь "Robert Ramey" написал: > > On 11/14/16 5:36 AM, David Demelier wrote: > I spent some time getting CMake to work with with boost libraries. > > My conclusions is that FindBoost can be relied upon only for header only libraries. To used build

Re: [CMake] Compiling CMake without libuv?

You can ask CMake to use its own copy of libuv by specifying CMAKE_USE_SYSTEM_LIBRARY_LIBUV to false. If building even the CMake version of libuv is not possible you can just disable building server mode by setting CMake_ENABLE_SERVER_MODE On Tue, Nov 15, 2016 at 5:59 PM, Christoph Grüninger

[Cmake-commits] CMake branch, master, updated. v3.7.0-538-gaf46484

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

[CMake] Compiling CMake without libuv?

Dear CMake folks, I am trying to package CMake for openSuse. I was a bit surprised that the new dependency libuv was nowhere mentioned. Can it be disabled by a configure switch for older systems? Currently it errors out when libuv is not found. It should be only necessary for cmake-server, right?

[Cmake-commits] CMake branch, next, updated. v3.7.0-1205-g76e1fe8

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1203-g977d4b3

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

Re: [CMake] FindBoost not finding MinGW libraries

On 11/14/16 5:36 AM, David Demelier wrote: I spent some time getting CMake to work with with boost libraries. My conclusions is that FindBoost can be relied upon only for header only libraries. To used build libraries, you'll have to explicitly set the specific library variable to the path

[Cmake-commits] CMake branch, next, updated. v3.7.0-1201-g027c414

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1198-ge909a7d

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1196-ge5f9144

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1194-gee3724f

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1165-g7f07081

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

Re: [CMake] CMake 3.7: Test #379: RunCMake.CPack_RPM fails

2016-11-15 15:16 GMT+01:00 Christoph Grüninger : > Hi Domen, > thanks for your answer. > > > > CMake 3.7 compiles so far, but test #379 (RunCMake.CPack_RPM) fails, > see > > > the error below from OBS. I had a brief look at our patches and I am > apt > > > to think they are

Re: [CMake] Force MSVC runtime for debug builds

Issue created: https://gitlab.kitware.com/cmake/cmake/issues/16430 On Tue, Nov 15, 2016 at 3:47 AM, Mueller-Roemer, Johannes Sebastian < johannes.sebastian.mueller-roe...@igd.fraunhofer.de> wrote: > I agree that CMake should not be defining _DEBUG explicitly, as it is used > by Microsoft’s

[Cmake-commits] CMake branch, next, updated. v3.7.0-1186-gcdf609a

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1162-g33eadfa

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1160-gbded335

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1156-gcbeb298

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

[Cmake-commits] CMake branch, release, updated. v3.7.0-6-gafb4a22

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1158-ge10b5d7

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-537-g4790842

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1151-g904ac9e

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-533-gb6f1b17

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-516-gdadccc7

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-512-g06ee14f

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-520-g2b7cc76

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-518-g06209c4

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-514-gfcfddc6

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

Re: [CMake] CMake 3.7: Test #379: RunCMake.CPack_RPM fails

Hi Domen, thanks for your answer. > > CMake 3.7 compiles so far, but test #379 (RunCMake.CPack_RPM) fails, see > > the error below from OBS. I had a brief look at our patches and I am apt > > to think they are unrelated. > > Can someone have a look and give some hint? > > > I'll test it today

[Cmake-commits] CMake branch, next, updated. v3.7.0-1143-g496e09e

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

Re: [cmake-developers] CMAKE 3.7 (for Android target) error: crtbegin_dynamic.o:crtbrand.c:function _start: error: undefined reference to 'main’

Hi Thank you for the quick response. >> What generator are you now using? Right! I forgot to mention this. I am using the "NMake Makefiles JOM" >> We don't have first-class support for those steps outside of Nsight Tegra. >> They need to be done with add_custom_target/add_custom_command. This

Re: [cmake-developers] CMAKE 3.7 (for Android target) error: crtbegin_dynamic.o:crtbrand.c:function _start: error: undefined reference to 'main’

On 11/14/2016 04:38 PM, Roberto Regalino wrote: > still target Android but not using VisualStudio What generator are you now using? > So far, I managed to create a new toolchain file containing the following: > > set(CMAKE_ANDROID_API 21) > set(CMAKE_ANDROID_SKIP_ANT_STEP 0) >

Re: [CMake] Are the current scoping rules for functions intended and documented?

Hi Brad, thank you very much for the clarification and the background information! I definitely have to scrutinize our CMake code to make sure that no additional problems are lurking in our build system. For now, I am going to file a feature request to keep track of the idea of properly scoping

Re: [CMake] FindBoost not finding MinGW libraries

2016-11-15 12:26 GMT+03:00 David Demelier : > 2016-11-14 16:00 GMT+01:00 Sergei Nikulov : >> Add option -DBoost_ADDITIONAL_VERSIONS="1.62.00;1.62" to command line >> or >> Update you findboost.cmake module from CMake repository. > > I've tried

Re: [CMake] FindBoost not finding MinGW libraries

2016-11-14 16:00 GMT+01:00 Sergei Nikulov : > Add option -DBoost_ADDITIONAL_VERSIONS="1.62.00;1.62" to command line > or > Update you findboost.cmake module from CMake repository. I've tried the additional the variable with no luck. I've also updated CMake to 3.7 with no

Re: [CMake] Force MSVC runtime for debug builds

I agree that CMake should not be defining _DEBUG explicitly, as it is used by Microsoft’s headers to match the chosen runtime. Maybe this warrants a bug report on gitlab. From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Kim Kryger Sent: Monday, November 14, 2016 22:05 To: Stephan Menzel