[CMake] Who want find_package(ImGui)?
Hello dear CMake users!Anybody use Dear ImGui project?Please help to review PR for add CMake support:https://github.com/ocornut/imgui/pull/1713Have a nice day! -- 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 offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[Cmake-commits] CMake branch, master, updated. v3.12.0-rc2-114-gb49b406
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 b49b4066c01fce2d1e4f766581016b036e3e06a4 (commit) from 8ad33961582bd0a70bf8226558c28fb3829b99a7 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b49b4066c01fce2d1e4f766581016b036e3e06a4 commit b49b4066c01fce2d1e4f766581016b036e3e06a4 Author: Kitware Robot AuthorDate: Tue Jul 3 00:01:06 2018 -0400 Commit: Kitware Robot CommitDate: Tue Jul 3 00:01:06 2018 -0400 CMake Nightly Date Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 3734784..c8cecc0 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,5 +1,5 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 12) -set(CMake_VERSION_PATCH 20180702) +set(CMake_VERSION_PATCH 20180703) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org https://cmake.org/mailman/listinfo/cmake-commits
[CMake] CMake, Visual Studio, do not generate absolute paths
So, it seems it is not possible to have CMake NOT to use absolute paths Quote “CMake does always use absolute paths. It's part of the concept.” https://stackoverflow.com/questions/45856955/how-to-tell-cmake-to-use-relative-paths One use case: 1) I have a Cmake script and I generate a Visual Studio project on machine 1 2) I have another high security computer, machine 2, where I don’t have administrator privileges To install software and CMake is on the list of “not approved” software. 3) I can copy the generated Visual Studio project from machine 1 to machine 2… But …alas, all miserably fails to compile because the paths are all wrong One solution I have used in the past for small projects, like 1 project file, was to manually edit the .vcxproj Visual Studio file For example replace this F:\wt.leaflet\wt-4.0.1\src\3rdparty\gason\src; With a relative path ..\..\..\3rdparty\gason\src; Which works perfectly (also remove all the CMake generated things, it’s really not needed after the project is made), but for projects where the number of generated projects Is more than 40, this is not a good way to spend our time Of course , doing a dedicated program that does this replacement for us Would be ideal So, question, does anyone know of the existence of this program? Also, this post circa 2008 says there was a “CMAKE_USE_RELATIVE_PATHS” That seems to have been deprecated “If you set CMAKE_SUPPRESS_REGENERATION to true, and CMAKE_USE_RELATIVE_PATHS to true, you might get things to work for a small project. “ would this work? Of course I would have to travel back in time to 2008, but that’s another problem https://cmake.org/pipermail/cmake/2008-March/020629.html I quote here the original post on this thread, “I cant help but comment that this is unnecessarily complicated when all that is desired is simply compiling without the Cmake dependency. Conceptually it should not be this hard. “ Yes, it should not be this hard for Cmake to have an *OPTION* to use relative paths, maybe ? http://pedro-vicente.net/ -- 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 offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[cmake-developers] Building cmake QtDialog: Can't find QT 5.11.1
I have QT 5.11.1 installed, I used the open source installer. It did install msvc2015 32-bit libs but not 2017. Google search shows that 2015 is ABI compatible so CMake should use that. When I generate the CMake project, it says it can't find QT version 4.x. How do I build CMake with the GUI application using the version of QT I have installed? QT installed at C:\QT -- 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 offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
Re: [CMake] [Error] While compiling as a pre requirement of a software
You need a binary CMake to compile CMake from source code. `apt-get install cmake` should be more appropriate here... Btw, CMake 2.8 is a pretty old version. If possible, you should use CMake >= 3.0. On Mon, Jul 2, 2018 at 9:39 AM canny georgina wrote: > Dear all, > I've been trying to use a factorization software (CADO-NFS), before I > can use it, I need to compile it, but in order to successfully compile > it, i need Cmake as pre requirement (CADO-NFS developer said that it's > mandatory to have it (Cmake) perfectly installed and compiled). When i > try to compile the CADO-NFS, because i don't have cmake installed, the > software took the initiative to download suitable Cmake and compile by > itself. However, as i face it, there are unexpected error when Cmake > is being compiled. For your information, i installed Cmake on Virtual > Machine (with ubuntu desktop 16.04 as an OS) with 2 GB as RAM. As for > the error information, i got this: > > root@ubuntu:/home/chunnie/Desktop/Math3/cado-nfs# make > CMake not found > I am about to download and compile a compatible version of Cmake. > Do you want to continue ? (y/n) > y > Need to get cmake first -- this takes long ! > installing cmake 2.8.12 in > /home/chunnie/Desktop/Math3/cado-nfs/cmake-installed > --2018-07-02 02:51:01-- > http://www.cmake.org/files/v2.8/cmake-2.8.12.tar.gz > Resolving www.cmake.org (www.cmake.org)... 66.194.253.19 > Connecting to www.cmake.org (www.cmake.org)|66.194.253.19|:80... > connected. > HTTP request sent, awaiting response... 301 Moved Permanently > Location: http://cmake.org/files/v2.8/cmake-2.8.12.tar.gz [following] > --2018-07-02 02:51:03-- http://cmake.org/files/v2.8/cmake-2.8.12.tar.gz > Resolving cmake.org (cmake.org)... 66.194.253.19 > Reusing existing connection to www.cmake.org:80. > HTTP request sent, awaiting response... 301 Moved Permanently > Location: https://cmake.org/files/v2.8/cmake-2.8.12.tar.gz [following] > --2018-07-02 02:51:04-- https://cmake.org/files/v2.8/cmake-2.8.12.tar.gz > Connecting to cmake.org (cmake.org)|66.194.253.19|:443... connected. > HTTP request sent, awaiting response... 200 OK > Length: 6064138 (5.8M) [application/x-gzip] > Saving to: ‘cmake-2.8.12.tar.gz’ > > cmake-2.8.12.tar.gz 100%[===>] 5.78M 4.06KB/sin 13m > 11s > > 2018-07-02 03:04:39 (7.49 KB/s) - ‘cmake-2.8.12.tar.gz’ saved > [6064138/6064138] > > - > CMake 2.8.12, Copyright 2000-2012 Kitware, Inc. > Found GNU toolchain > C compiler on this system is: gcc > C++ compiler on this system is: g++ > Makefile processor on this system is: make > g++ is GNU compiler > g++ has setenv > g++ has unsetenv > g++ does not have environ in stdlib.h > g++ has STL in std:: namespace > g++ has ANSI streams > g++ has streams in std:: namespace > g++ has sstream > g++ has operator!=(string, char*) > g++ has stl iterator_traits > g++ has standard template allocator > g++ has allocator<>::rebind<> > g++ does not have non-standard allocator<>::max_size argument > g++ has stl containers supporting allocator objects > g++ has header cstddef > g++ requires template friends to use <> > g++ supports member templates > g++ has standard template specialization syntax > g++ has argument dependent lookup > g++ has struct stat with st_mtim member > g++ has ios::binary openmode > g++ has ANSI for scoping > - > make[1]: Entering directory > '/tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Bootstrap.cmk' > g++ -I/tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Bootstrap.cmk > -I/tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Source > -I/tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Bootstrap.cmk -c > /tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Source/cmStandardIncludes.cxx > -o cmStandardIncludes.o > g++ -I/tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Bootstrap.cmk > -I/tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Source > -I/tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Bootstrap.cmk -c > /tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Source/cmake.cxx -o cmake.o > In file included from > /tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Source/cmSystemTools.h:17:0, > from > /tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Source/cmake.h:16, > from > /tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Source/cmake.cxx:12: > > /tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Bootstrap.cmk/cmsys/SystemTools.hxx:633:5: > internal compiler error: Illegal instruction > double percent_bin = 0.05); > ^ > Please submit a full bug report, > with preprocessed source if appropriate. > See for instructions. > Makefile:6: recipe for target 'cmake.o' failed > make[1]: *** [cmake.o] Error 1 > make[1]: Leaving directory > '/tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Bootstrap.cmk' > - > Error when bootstrapping CMake: > Problem while running make > - > Log of errors: > /tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Bootstrap.cmk/cmake_bootstrap.log >
[Cmake-commits] CMake branch, master, updated. v3.12.0-rc2-113-g8ad3396
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 8ad33961582bd0a70bf8226558c28fb3829b99a7 (commit) via 19f338109d8909feba37513285afe4a583811d54 (commit) from 752c2721a17e95f642874562f6b406f1f05b4430 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8ad33961582bd0a70bf8226558c28fb3829b99a7 commit 8ad33961582bd0a70bf8226558c28fb3829b99a7 Merge: 752c272 19f3381 Author: Brad King AuthorDate: Mon Jul 2 15:48:51 2018 + Commit: Kitware Robot CommitDate: Mon Jul 2 11:48:56 2018 -0400 Merge topic 'policy_max_docs' 19f338109d Help: Clarify ... behavior for policy-related commands Acked-by: Kitware Robot Merge-request: !2180 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=19f338109d8909feba37513285afe4a583811d54 commit 19f338109d8909feba37513285afe4a583811d54 Author: Craig Scott AuthorDate: Sun Jul 1 08:05:01 2018 +1000 Commit: Craig Scott CommitDate: Mon Jul 2 08:41:46 2018 +1000 Help: Clarify ... behavior for policy-related commands Affects cmake_minimum_required() and cmake_policy(VERSION) diff --git a/Help/command/cmake_minimum_required.rst b/Help/command/cmake_minimum_required.rst index 7c02190..2f1ab60 100644 --- a/Help/command/cmake_minimum_required.rst +++ b/Help/command/cmake_minimum_required.rst @@ -13,6 +13,10 @@ If the running version of CMake is lower than the required version it will stop processing the project and report an error. The optional version, if specified, must be at least the version and affects policy settings as described below. +If the running version of CMake is older than 3.12, the extra ``...`` +dots will be seen as version component separators, resulting in the +``...`` part being ignored and preserving the pre-3.12 behavior +of basing policies on . The ``FATAL_ERROR`` option is accepted but ignored by CMake 2.6 and higher. It should be specified so CMake versions 2.4 and lower fail diff --git a/Help/command/cmake_policy.rst b/Help/command/cmake_policy.rst index 6a8dd62..c3f7cfb 100644 --- a/Help/command/cmake_policy.rst +++ b/Help/command/cmake_policy.rst @@ -30,7 +30,10 @@ encourage projects to set policies based on CMake versions:: ``major.minor[.patch[.tweak]]``, and the ``...`` is literal. The version must be at least ``2.4`` and at most the running version of CMake. The version, if specified, must be at least the version -but may exceed the running version of CMake. +but may exceed the running version of CMake. If the running version of +CMake is older than 3.12, the extra ``...`` dots will be seen as version +component separators, resulting in the ``...`` part being ignored and +preserving the pre-3.12 behavior of basing policies on . This specifies that the current CMake code is written for the given range of CMake versions. All policies known to the running version of CMake diff --git a/Help/release/3.12.rst b/Help/release/3.12.rst index 4d1135e..79ebc8e 100644 --- a/Help/release/3.12.rst +++ b/Help/release/3.12.rst @@ -34,7 +34,8 @@ Commands * The :command:`cmake_minimum_required` and :command:`cmake_policy(VERSION)` commands now accept a version range using the form ``[...]``. The version is required but policies are set based on the - version. This allows projects to specify a range of versions + older of the running CMake version and the version specified by + . This allows projects to specify a range of versions for which they have been updated and avoid explicit policy settings. * The :command:`file(GLOB)` and :command:`file(GLOB_RECURSE)` commands --- Summary of changes: Help/command/cmake_minimum_required.rst | 4 Help/command/cmake_policy.rst | 5 - Help/release/3.12.rst | 3 ++- 3 files changed, 10 insertions(+), 2 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org https://cmake.org/mailman/listinfo/cmake-commits
Re: [CMake] ccmake command missing from 3.12.0 RC releases
Thanks! On Mon, 2 Jul 2018 at 16:40, Brad King wrote: > On 07/02/2018 08:43 AM, Robert Maynard wrote: > > On Sun, Jul 1, 2018 at 6:18 PM Miklos Espak wrote: > >> the 'ccmake' command seems to be missing from the linux tarballs > >> from 3.12.0 RC1 and RC2. Not sure if you are aware of that. > > > > Thanks for reporting this. I am looking into it. > > Thanks for the report. See fix and explanation here: > > https://gitlab.kitware.com/cmake/cmake/merge_requests/2186 > > -Brad > -- 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 offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] ccmake command missing from 3.12.0 RC releases
On 07/02/2018 08:43 AM, Robert Maynard wrote: > On Sun, Jul 1, 2018 at 6:18 PM Miklos Espak wrote: >> the 'ccmake' command seems to be missing from the linux tarballs >> from 3.12.0 RC1 and RC2. Not sure if you are aware of that. > > Thanks for reporting this. I am looking into it. Thanks for the report. See fix and explanation here: https://gitlab.kitware.com/cmake/cmake/merge_requests/2186 -Brad -- 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 offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[cmake-developers] C# targets and content source files
In Visual Studio, I can add *.ico files to my C# project and in the CSPROJ XML, it shows up as a element. Is this supported in CMake for CSharp targets? -- 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 offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
Re: [CMake] [Error] While compiling as a pre requirement of a software
Hello! Did you try just to install CMake in your virtual machine? Best regards, Innokentiy Alaytsev -- Sent from: http://cmake.3232098.n2.nabble.com/ -- 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 offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[CMake] [Error] While compiling as a pre requirement of a software
Dear all, I've been trying to use a factorization software (CADO-NFS), before I can use it, I need to compile it, but in order to successfully compile it, i need Cmake as pre requirement (CADO-NFS developer said that it's mandatory to have it (Cmake) perfectly installed and compiled). When i try to compile the CADO-NFS, because i don't have cmake installed, the software took the initiative to download suitable Cmake and compile by itself. However, as i face it, there are unexpected error when Cmake is being compiled. For your information, i installed Cmake on Virtual Machine (with ubuntu desktop 16.04 as an OS) with 2 GB as RAM. As for the error information, i got this: root@ubuntu:/home/chunnie/Desktop/Math3/cado-nfs# make CMake not found I am about to download and compile a compatible version of Cmake. Do you want to continue ? (y/n) y Need to get cmake first -- this takes long ! installing cmake 2.8.12 in /home/chunnie/Desktop/Math3/cado-nfs/cmake-installed --2018-07-02 02:51:01-- http://www.cmake.org/files/v2.8/cmake-2.8.12.tar.gz Resolving www.cmake.org (www.cmake.org)... 66.194.253.19 Connecting to www.cmake.org (www.cmake.org)|66.194.253.19|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: http://cmake.org/files/v2.8/cmake-2.8.12.tar.gz [following] --2018-07-02 02:51:03-- http://cmake.org/files/v2.8/cmake-2.8.12.tar.gz Resolving cmake.org (cmake.org)... 66.194.253.19 Reusing existing connection to www.cmake.org:80. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://cmake.org/files/v2.8/cmake-2.8.12.tar.gz [following] --2018-07-02 02:51:04-- https://cmake.org/files/v2.8/cmake-2.8.12.tar.gz Connecting to cmake.org (cmake.org)|66.194.253.19|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 6064138 (5.8M) [application/x-gzip] Saving to: ‘cmake-2.8.12.tar.gz’ cmake-2.8.12.tar.gz 100%[===>] 5.78M 4.06KB/sin 13m 11s 2018-07-02 03:04:39 (7.49 KB/s) - ‘cmake-2.8.12.tar.gz’ saved [6064138/6064138] - CMake 2.8.12, Copyright 2000-2012 Kitware, Inc. Found GNU toolchain C compiler on this system is: gcc C++ compiler on this system is: g++ Makefile processor on this system is: make g++ is GNU compiler g++ has setenv g++ has unsetenv g++ does not have environ in stdlib.h g++ has STL in std:: namespace g++ has ANSI streams g++ has streams in std:: namespace g++ has sstream g++ has operator!=(string, char*) g++ has stl iterator_traits g++ has standard template allocator g++ has allocator<>::rebind<> g++ does not have non-standard allocator<>::max_size argument g++ has stl containers supporting allocator objects g++ has header cstddef g++ requires template friends to use <> g++ supports member templates g++ has standard template specialization syntax g++ has argument dependent lookup g++ has struct stat with st_mtim member g++ has ios::binary openmode g++ has ANSI for scoping - make[1]: Entering directory '/tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Bootstrap.cmk' g++ -I/tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Bootstrap.cmk -I/tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Source -I/tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Bootstrap.cmk -c /tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Source/cmStandardIncludes.cxx -o cmStandardIncludes.o g++ -I/tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Bootstrap.cmk -I/tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Source -I/tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Bootstrap.cmk -c /tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Source/cmake.cxx -o cmake.o In file included from /tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Source/cmSystemTools.h:17:0, from /tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Source/cmake.h:16, from /tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Source/cmake.cxx:12: /tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Bootstrap.cmk/cmsys/SystemTools.hxx:633:5: internal compiler error: Illegal instruction double percent_bin = 0.05); ^ Please submit a full bug report, with preprocessed source if appropriate. See for instructions. Makefile:6: recipe for target 'cmake.o' failed make[1]: *** [cmake.o] Error 1 make[1]: Leaving directory '/tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Bootstrap.cmk' - Error when bootstrapping CMake: Problem while running make - Log of errors: /tmp/cmake-build.CZc7zfVj/cmake-2.8.12/Bootstrap.cmk/cmake_bootstrap.log - make[1]: Entering directory '/tmp/cmake-build.CZc7zfVj/cmake-2.8.12' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory '/tmp/cmake-build.CZc7zfVj/cmake-2.8.12' make[1]: Entering directory '/tmp/cmake-build.CZc7zfVj/cmake-2.8.12' make[1]: *** No rule to make target 'install'. Stop. make[1]: Leaving directory '/tmp/cmake-build.CZc7zfVj/cmake-2.8.12' ./scripts/call_cmake.sh: line 152:
Re: [CMake] [ANNOUNCE] CMake 3.12.0-rc2 is ready for testing
> Users of the old function cannot use the new syntax in older cmake versions The new cmake_minimum_required syntax of MIN...POLICY_MAX is entirely backwards compatible and will just be ignored by cmake < 3.12. On Sat, Jun 30, 2018 at 1:14 AM Hendrik Sattler wrote: > > It would actually make even more sense to rename cmake_minimum_required() to > cmake_version_required() with the new syntax or something similar. Users of > the old function cannot use the new syntax in older cmake versions and the > old name does not actually fit the new functionality. > > > Am 30. Juni 2018 00:05:25 MESZ schrieb "Alan W. Irwin" > : > >On 2018-06-29 14:46-0400 Robert Maynard wrote: > >[...] > >> * The "cmake_minimum_required()" and "cmake_policy(VERSION)" > >> commands now accept a version range using the form > >> "[...]". The "" version is required but policies are > >> set based on the "" version. This allows projects to specify a > >> range of versions for which they have been updated and avoid > >> explicit policy settings. > >[...] > > > >I suggest the following change to the above description: > > > >but policies are set based on the "" version. > > > >==> > > > >but policies are set based on the minimum of the running CMake and > >"" versions. > > > >I prefer the latter because it immediately answers the question implied > >by the former, i.e., > >what happens if the running version is less than max? > > > >Alan > >__ > >Alan W. Irwin > > > >Programming affiliations with the FreeEOS equation-of-state > >implementation for stellar interiors (freeeos.sf.net); the Time > >Ephemerides project (timeephem.sf.net); PLplot scientific plotting > >software package (plplot.sf.net); the libLASi project > >(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); > >and the Linux Brochure Project (lbproject.sf.net). > >__ > > > >Linux-powered Science > >__ > -- > > 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 offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake -- 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 offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] ccmake command missing from 3.12.0 RC releases
Thanks for reporting this. I am looking into it. On Sun, Jul 1, 2018 at 6:18 PM Miklos Espak wrote: > > Hi, > > the 'ccmake' command seems to be missing from the linux tarballs from 3.12.0 > RC1 and RC2. Not sure if you are aware of that. > > The release notes does not mention that it should be removed, so I hope the > final release is going to have it. :) > > Maybe the curses dev package isn't installed on the build machine? > > Cheers, > Miklos > > -- > > 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 offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake -- 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 offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] Changes to cmake_minimum_required() for 3.12
Hi, Just giving my 2 cents: If the preferred solution is the "POLICY_NEW_UNTIL" wording, then why not make this accepted as well? This way, you can deprecate the backwards-compatible version in a few years and remove it some time thereafter. In the end, you'll get a cleaner solution... Cheers, Johannes On Montag, 2. Juli 2018 08:43:57 CEST Craig Scott wrote: > On Mon, Jul 2, 2018 at 4:04 AM, Alan W. Irwin > > wrote: > > On 2018-07-01 08:12+1000 Craig Scott wrote: > > > > Older CMake versions > > > >> will see the extra dots as being version component separators and will > >> end > >> up effectively ignoring the max part. > > > > This explanation of how "..." will be interpreted by older CMake > > versions makes sense, but it wasn't obvious to me without that > > explanation. And I suspect other build-system developers/maintainers > > would also benefit from the explanation. Therefore, please explicitly > > include the above explanation in the latest documentation of both the > > cmake_minimum_required and cmake_policy commands. > > I've updated the merge request to incorporate this feedback. > > https://gitlab.kitware.com/cmake/cmake/merge_requests/2180 -- Johannes Zarl-Zierl Information management JOHANNES KEPLER UNIVERSITY LINZ Altenberger Straße 69 4040 Linz, Austria P +43 732 2468 3898 johannes.zarl-zi...@jku.at www.jku.at -- 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 offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[CMake] .def files since CMake 3.10 in Linux
Hi, I (and someone else) stumbled upon a problem when using the Azure IOTHUB SDK for C on a Linux platform using cmake 3.10+: https://github.com/Azure/azure-iot-sdk-c/issues/505 The problem seems to be triggered by having two .def-files as add_library()-source-files. During the build cmake generates a command which does: cmake -E __create_def This fails as unknown to cmake. Is this a cmake-bug or is Azure using .def-files the wrong way? A quick additional test show that the problem is coming from having 2 .def-files as sources. Having just one is OK. -- Patrick. -- 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 offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] how to deprecate a target?
FYI: Starting with CMake 3.11, it is now possible to define an alias of an imported target. Le lun. 2 juil. 2018 à 09:27, Petr Kmoch a écrit : > Hi Bram. > > Wild idea: could you also define a non-namespaced target `foo` and craft > it such that linking against it generates a linker warning? Something like > "Warning: symbol `Using_just_foo_is_deprecated_use_Foo_foo_instead` defined > twice, ignoring weak definition." > > Petr > > On 2 July 2018 at 00:11, Bram de Greve wrote: > >> That is unfortunate ... do you know any not-so-nice ways? >> >> So, what would you recommend here? >> >> I'm deprecating the old ways to use the Foo package (using Foo_LIBRARIES >> and Foo_INCLUDE_DIRS. You know, the cmake 2.x way of things). I can do that >> nicely with variable watches. >> >> But what about the target names? If I want to guarantee a seamless >> transition period, I should opt to keep using the "foo" target names. But >> then there's no way to "upgrade" to "Foo::foo" targets without breakage, >> since there's no deprecation strategy. And I can't use target aliases, >> since that is not allowed on imported targets. >> >> To answer my own question, I think the best thing is to move to the >> "Foo::foo" targets right now. There's at least one downstream package that >> will be hurt by this, but the damage is less than waiting for everyone to >> have moved to the "foo" target first. >> >> Best, >> >> Bram. >> >> >> >> On 6/29/2018 20:22, Robert Maynard wrote: >> >>> I am not aware of a nice way to setup CMake to error out if a user >>> links to `foo` instead of `Foo::foo`. >>> On Fri, Jun 29, 2018 at 2:05 AM Bram de Greve >>> wrote: >>> Hi all, Consider this situation. I'm building a Foo packaged, to be used by a Bar project. Foo used to export its target as simply foo. Now it exports its target as Foo::foo. Bar contains this: add_library(bar ...) target_link_libraries(bar foo) This of course must now be: add_library(bar ...) target_link_libraries(bar Foo::foo) But if bar still links to the foo instead of Foo::foo, then CMake doesn't really complain. foo doesn't exist, but configures and generates just fine. Of course, you'll face strange build errors, from which it isn't immediately apparent what's causing this ... How can I make sure CMake will complain loudly when bar still links to foo? Thanks, Bram. -- 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 offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake >>> >> -- >> >> 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 offering, please visit: >> >> CMake Support: http://cmake.org/cmake/help/support.html >> CMake Consulting: http://cmake.org/cmake/help/consulting.html >> CMake Training Courses: http://cmake.org/cmake/help/training.html >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Follow this link to subscribe/unsubscribe: >> https://cmake.org/mailman/listinfo/cmake >> > > -- > > 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 offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake > -- 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 offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at
Re: [CMake] how to deprecate a target?
Hi Bram. Wild idea: could you also define a non-namespaced target `foo` and craft it such that linking against it generates a linker warning? Something like "Warning: symbol `Using_just_foo_is_deprecated_use_Foo_foo_instead` defined twice, ignoring weak definition." Petr On 2 July 2018 at 00:11, Bram de Greve wrote: > That is unfortunate ... do you know any not-so-nice ways? > > So, what would you recommend here? > > I'm deprecating the old ways to use the Foo package (using Foo_LIBRARIES > and Foo_INCLUDE_DIRS. You know, the cmake 2.x way of things). I can do that > nicely with variable watches. > > But what about the target names? If I want to guarantee a seamless > transition period, I should opt to keep using the "foo" target names. But > then there's no way to "upgrade" to "Foo::foo" targets without breakage, > since there's no deprecation strategy. And I can't use target aliases, > since that is not allowed on imported targets. > > To answer my own question, I think the best thing is to move to the > "Foo::foo" targets right now. There's at least one downstream package that > will be hurt by this, but the damage is less than waiting for everyone to > have moved to the "foo" target first. > > Best, > > Bram. > > > > On 6/29/2018 20:22, Robert Maynard wrote: > >> I am not aware of a nice way to setup CMake to error out if a user >> links to `foo` instead of `Foo::foo`. >> On Fri, Jun 29, 2018 at 2:05 AM Bram de Greve wrote: >> >>> Hi all, >>> >>> Consider this situation. I'm building a Foo packaged, to be used by a >>> Bar project. >>> >>> Foo used to export its target as simply foo. >>> Now it exports its target as Foo::foo. >>> >>> Bar contains this: >>> add_library(bar ...) >>> target_link_libraries(bar foo) >>> >>> This of course must now be: >>> add_library(bar ...) >>> target_link_libraries(bar Foo::foo) >>> >>> But if bar still links to the foo instead of Foo::foo, then CMake >>> doesn't really complain. foo doesn't exist, but configures and >>> generates just fine. Of course, you'll face strange build errors, from >>> which it isn't immediately apparent what's causing this ... >>> >>> How can I make sure CMake will complain loudly when bar still links to >>> foo? >>> >>> Thanks, >>> Bram. >>> >>> -- >>> >>> 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 offering, please visit: >>> >>> CMake Support: http://cmake.org/cmake/help/support.html >>> CMake Consulting: http://cmake.org/cmake/help/consulting.html >>> CMake Training Courses: http://cmake.org/cmake/help/training.html >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Follow this link to subscribe/unsubscribe: >>> https://cmake.org/mailman/listinfo/cmake >>> >> > -- > > 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 offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake > -- 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 offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
