Re: [CMake] [CPACK] [RPM] Using %if in %file section
Am Donnerstag, 14. Mai 2015, 05:02:57 schrieb Luc J. Bourhis: I would like to end up with the following in the specs file: I tried to use CPACK_RPM_USER_FILELIST as but this results in which is not quite right. Well, yes, this is just one newline instead of 3. Try adding \n\n. Or use a mail client that doesn't mangle what you send, so we can actually help you ;) Eike signature.asc Description: This is a digitally signed message part. -- 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: http://public.kitware.com/mailman/listinfo/cmake
[Cmake-commits] CMake branch, next, updated. v3.2.2-2713-g85333e1
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 85333e13fc6b2089d9540069d1a9f4bf216f6894 (commit) via 12b85b17911bbba871ffecf485878091b1be50b6 (commit) via ee58e94d62e33a06625f09b6a89ff3bbdeaf510e (commit) from 472df2c2b26005bd9f74f26ddfbbf3a8eef0e366 (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 - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=85333e13fc6b2089d9540069d1a9f4bf216f6894 commit 85333e13fc6b2089d9540069d1a9f4bf216f6894 Merge: 472df2c 12b85b1 Author: Brad King brad.k...@kitware.com AuthorDate: Thu May 14 08:54:15 2015 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Thu May 14 08:54:15 2015 -0400 Merge topic 'FindSquish-sh-exit' into next 12b85b17 FindSquish: Avoid bash-specific behavior in test script (#15568) ee58e94d CMake Nightly Date Stamp http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=12b85b17911bbba871ffecf485878091b1be50b6 commit 12b85b17911bbba871ffecf485878091b1be50b6 Author: Felix Geyer de...@ubuntu.com AuthorDate: Thu May 14 05:31:00 2015 -0400 Commit: Brad King brad.k...@kitware.com CommitDate: Thu May 14 08:53:33 2015 -0400 FindSquish: Avoid bash-specific behavior in test script (#15568) Fix Squish4RunTestCase.sh to be POSIX compliant by exiting with 255 explicitly instead of depending on bash to translate -1 to 255. This script is used by the SQUISH_V3_ADD_TEST and SQUISH_V4_ADD_TEST macros provided by FindSquish. diff --git a/Modules/Squish4RunTestCase.sh b/Modules/Squish4RunTestCase.sh index abd5deb..39a3907 100755 --- a/Modules/Squish4RunTestCase.sh +++ b/Modules/Squish4RunTestCase.sh @@ -11,11 +11,11 @@ SETTINGSGROUP=$7 $SQUISHSERVER --stop /dev/null 21 echo Adding AUT... $SQUISHSERVER --settingsGroup $SETTINGSGROUP --config addAUT $AUT $AUTDIR -$SQUISHSERVER --settingsGroup $SETTINGSGROUP --config addAUT $AUT $AUTDIR || exit -1 +$SQUISHSERVER --settingsGroup $SETTINGSGROUP --config addAUT $AUT $AUTDIR || exit 255 # sleep 1 echo Starting the squish server... $SQUISHSERVER --daemon -$SQUISHSERVER --daemon || exit -1 +$SQUISHSERVER --daemon || exit 255 # sleep 2 echo Running the test case...$SQUISHRUNNER --settingsGroup $SETTINGSGROUP --testsuite $TESTSUITE --testcase $TESTCASE --- Summary of changes: Modules/Squish4RunTestCase.sh |4 ++-- Source/CMakeVersion.cmake |2 +- 2 files changed, 3 insertions(+), 3 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v3.2.2-1120-geb9323e
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 eb9323eb1aa2beb32d933c3e09a160939ff31682 (commit) via 7953867ba46223dfab373ce58cff0a4bc20c3864 (commit) from ee58e94d62e33a06625f09b6a89ff3bbdeaf510e (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 - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=eb9323eb1aa2beb32d933c3e09a160939ff31682 commit eb9323eb1aa2beb32d933c3e09a160939ff31682 Merge: ee58e94 7953867 Author: Brad King brad.k...@kitware.com AuthorDate: Thu May 14 10:27:40 2015 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Thu May 14 10:27:40 2015 -0400 Merge topic 'FindJava-openjdk-8' 7953867b FindJava: Fix OpenJDK 8 version detection (#15565) --- Summary of changes: Modules/FindJava.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v3.2.2-1127-g36c275d
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 36c275d857d1764f37df450361ed816d24091300 (commit) via 576ef8c56ef68b94340f95854a8211fb6f3562f1 (commit) via c9709dffb0856c140f39c5db1525bccc74771c92 (commit) via 3b815ed283eb8d59c4e46dd89aa1e17c9f4deee6 (commit) from a86ddbe56e1659ca1385514e1ffe1a9389d9ca62 (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 - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=36c275d857d1764f37df450361ed816d24091300 commit 36c275d857d1764f37df450361ed816d24091300 Merge: a86ddbe 576ef8c Author: Brad King brad.k...@kitware.com AuthorDate: Thu May 14 10:27:44 2015 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Thu May 14 10:27:44 2015 -0400 Merge topic 'update-kwsys' 576ef8c5 KWSys: Tell Git not to export .gitattributes c9709dff Merge branch 'upstream-kwsys' into update-kwsys 3b815ed2 KWSys 2015-05-12 (b1d560a0) --- Summary of changes: Source/kwsys/.gitattributes |4 Source/kwsys/CPU.h.in | 10 +- 2 files changed, 9 insertions(+), 5 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/mailman/listinfo/cmake-commits
[CMake] [CPACK] [RPM] Using %if in %file section
I would like to end up with the following in the specs file: I tried to use CPACK_RPM_USER_FILELIST as but this results in which is not quite right. Is there something I am missing? Or is it a fundamental limitation of CPack RPM generator? If so, would there be any workaround? Thanks in advance for any help. - -- Luc J. Bourhis -- View this message in context: http://cmake.3232098.n2.nabble.com/CPACK-RPM-Using-if-in-file-section-tp7590576.html Sent from the CMake mailing list archive at 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: http://public.kitware.com/mailman/listinfo/cmake
[Cmake-commits] CMake branch, master, updated. v3.2.2-1123-ga86ddbe
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 a86ddbe56e1659ca1385514e1ffe1a9389d9ca62 (commit) via 5685817874e25bb1e8b112e66186eec4345c4635 (commit) via 4bd122ad9c82464d8d1271e448e510a5d40f4596 (commit) from eb9323eb1aa2beb32d933c3e09a160939ff31682 (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 - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a86ddbe56e1659ca1385514e1ffe1a9389d9ca62 commit a86ddbe56e1659ca1385514e1ffe1a9389d9ca62 Merge: eb9323e 5685817 Author: Brad King brad.k...@kitware.com AuthorDate: Thu May 14 10:27:42 2015 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Thu May 14 10:27:42 2015 -0400 Merge topic 'FindHDF5-version-support' 56858178 FindHDF5: Add version support 4bd122ad FindHDF5: Check for a few H5pubconf*.h name variants --- Summary of changes: Modules/FindHDF5.cmake| 25 - Tests/CMakeOnly/AllFindModules/CMakeLists.txt |4 ++-- 2 files changed, 22 insertions(+), 7 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/mailman/listinfo/cmake-commits
Re: [CMake] [CPACK] [RPM] Using %if in %file section
I forgot to mention this is with cpack version 3.2.1 - -- Luc J. Bourhis -- View this message in context: http://cmake.3232098.n2.nabble.com/CPACK-RPM-Using-if-in-file-section-tp7590576p7590577.html Sent from the CMake mailing list archive at 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: http://public.kitware.com/mailman/listinfo/cmake
[Cmake-commits] CMake branch, next, updated. v3.2.2-2720-g9974c7a
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 9974c7a0ee2db94a12bcc432b8316aaa5b68 (commit) via 36c275d857d1764f37df450361ed816d24091300 (commit) via a86ddbe56e1659ca1385514e1ffe1a9389d9ca62 (commit) via eb9323eb1aa2beb32d933c3e09a160939ff31682 (commit) from e446de702c6c4585b387f5127c299092826fad34 (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 - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9974c7a0ee2db94a12bcc432b8316aaa5b68 commit 9974c7a0ee2db94a12bcc432b8316aaa5b68 Merge: e446de7 36c275d Author: Brad King brad.k...@kitware.com AuthorDate: Thu May 14 10:28:51 2015 -0400 Commit: Brad King brad.k...@kitware.com CommitDate: Thu May 14 10:28:51 2015 -0400 Merge branch 'master' into next --- Summary of changes: hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/mailman/listinfo/cmake-commits
Re: [CMake] FindModules.cmake quality + Kitware proposition
Nagy-Egri Máté Ferenc via CMake wrote: ... NMake batch mode support for multicore build, etc. I suggest you look into 'jom'. Thanks, Steve. -- 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: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] CMAKE_CXX_COMPILER_VERSION quite a useful variable, right?
Thanks to both Rolf Eike Beer and Petr Kmoch for showing me that the variable is documented as CMAKE_LANG_COMPILER_VERSION. :-) Kind regards, Niels -- 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: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] [CPACK] [RPM] Using %if in %file section
Ok, sorry, I used the online nabble interface to cmake mailing list actually
but here is my original message without any formatting, after the marker
-. I'll take the opportunity to explain the rationales. I found out that
the time spent by CPack running rpmbuild is only a very small portion of the
total runtime and I need to build the same package on different platforms.
So I thought of simply running CPack once and then copying over the
_CPack_Packages/... directory and run rpmbuild directly.
---
I would like to end up with the following in the specs file:
...
%file
...
%if 0%{fedora} = 14
/path/to/some/file
%endif
I tried to use CPACK_RPM_USER_FILELIST as
set(CPACK_RPM_USER_FILELIST ${CPACK_RPM_USER_FILELIST}
%if 0%{fedora} = 14
/path/to/some/file
%endif
)
but this results in
%if 0%{fedora} = 14
/path/to/some/file
%endif %endif
which is not quite right.
Is there something I am missing? Or is it a fundamental limitation of CPack
RPM generator? If so, would there be any workaround? Thanks in advance for
any help.
-
--
Luc J. Bourhis
--
View this message in context:
http://cmake.3232098.n2.nabble.com/CPACK-RPM-Using-if-in-file-section-tp7590576p7590586.html
Sent from the CMake mailing list archive at 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:
http://public.kitware.com/mailman/listinfo/cmake
[Cmake-commits] CMake branch, next, updated. v3.2.2-2723-g355a81a
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 355a81aed21eaa1a8ba74c981624501344157109 (commit)
via f79d60255ecdefd51750aed1f2fcc86df280c984 (commit)
via 501c237a83001a8783b2249bd5f5066c3472a2aa (commit)
from 9974c7a0ee2db94a12bcc432b8316aaa5b68 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=355a81aed21eaa1a8ba74c981624501344157109
commit 355a81aed21eaa1a8ba74c981624501344157109
Merge: 9974c7a f79d602
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Thu May 14 13:09:39 2015 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Thu May 14 13:09:39 2015 -0400
Merge topic 'disallow-install-of-export' into next
f79d6025 install: Disallow installing export() result.
501c237a install: Use an intermediate filesVector variable.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f79d60255ecdefd51750aed1f2fcc86df280c984
commit f79d60255ecdefd51750aed1f2fcc86df280c984
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Thu May 14 19:08:27 2015 +0200
Commit: Stephen Kelly steve...@gmail.com
CommitDate: Thu May 14 19:08:58 2015 +0200
install: Disallow installing export() result.
diff --git a/Help/manual/cmake-policies.7.rst b/Help/manual/cmake-policies.7.rst
index e59cce7..2cc3a47 100644
--- a/Help/manual/cmake-policies.7.rst
+++ b/Help/manual/cmake-policies.7.rst
@@ -119,3 +119,4 @@ All Policies
/policy/CMP0059
/policy/CMP0060
/policy/CMP0061
+ /policy/CMP0062
diff --git a/Help/policy/CMP0062.rst b/Help/policy/CMP0062.rst
new file mode 100644
index 000..632cfc2
--- /dev/null
+++ b/Help/policy/CMP0062.rst
@@ -0,0 +1,27 @@
+CMP0062
+---
+
+Disallow install() of export() result.
+
+The :command:`export()` command generates a file containing
+:ref:`Imported Targets`, which is suitable for use from the build
+directory. It is not suitable for installation because it contains absolute
+paths to buildsystem locations, and is particular to a single build
+configuration.
+
+The :command:`install(EXPORT)` generates and installs files which contain
+:ref:`Imported Targets`. These files are generated with relative paths
+(unless the user specifies absolute paths), and are designed for
+multi-configuration use.
+
+CMake 3.3 no longer allows the use of the :command:`install(FILES)` command
+with the result of the :command:`export()` command.
+
+The ``OLD`` behavior for this policy is to allow installing the result of
+an :command:`export()` command. The ``NEW`` behavior for this policy is
+not to allow installing the result of an :command:`export()` command.
+
+This policy was introduced in CMake version 3.3. CMake version
+|release| warns when the policy is not set and uses ``OLD`` behavior. Use
+the :command:`cmake_policy()` command to set it to ``OLD`` or ``NEW``
+explicitly.
diff --git a/Source/cmInstallCommand.cxx b/Source/cmInstallCommand.cxx
index 24de1b5..899b088 100644
--- a/Source/cmInstallCommand.cxx
+++ b/Source/cmInstallCommand.cxx
@@ -871,6 +871,47 @@ bool
cmInstallCommand::HandleFilesMode(std::vectorstd::string const args)
return false;
}
+ cmPolicies::PolicyStatus status =
+ this-Makefile-GetPolicyStatus(cmPolicies::CMP0062);
+
+ cmGlobalGenerator *gg = this-Makefile-GetGlobalGenerator();
+ for(std::vectorstd::string::const_iterator fileIt = filesVector.begin();
+ fileIt != filesVector.end(); ++fileIt)
+{
+if (gg-IsExportedTargetsFile(*fileIt))
+ {
+ const char *modal = 0;
+ std::ostringstream e;
+ cmake::MessageType messageType = cmake::AUTHOR_WARNING;
+
+ switch(status)
+{
+case cmPolicies::WARN:
+ e cmPolicies::GetPolicyWarning(cmPolicies::CMP0062) \n;
+ modal = should;
+case cmPolicies::OLD:
+ break;
+case cmPolicies::REQUIRED_IF_USED:
+case cmPolicies::REQUIRED_ALWAYS:
+case cmPolicies::NEW:
+ modal = may;
+ messageType = cmake::FATAL_ERROR;
+}
+ if (modal)
+{
+e The file\n*fileIt \nwas generated by the export()
+ command. It modal not be installed with the
+ install() command. Use the install(EXPORT) mechanism
+ instead. See the cmake-packages(7) manual for more.\n;
+this-Makefile-IssueMessage(messageType, e.str());
+if (messageType == cmake::FATAL_ERROR)
+ {
+ return false;
+ }
+}
+ }
+}
+
if (!ica.Finalize())
{
return false;
diff --git a/Source/cmPolicies.h b/Source/cmPolicies.h
index 536dcdc..7df4ee2
Re: [CMake] Alias of imported target
Ruslan Baratov via CMake wrote: It may be helpful in situations when you build package with examples. In case when you want examples to work both as a part of a project (add_subdirectory) or stand-alone (find_package). I expect external_project may lead to more readability for this case, though the case you described also makes sense. Thanks, Steve. -- 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: http://public.kitware.com/mailman/listinfo/cmake
[cmake-developers] [CMake 0015569]: Allow ALIAS of IMPORTED targets
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15569 == Reported By:Stephen Kelly Assigned To: == Project:CMake Issue ID: 15569 Category: (No Category) Reproducibility:have not tried Severity: minor Priority: normal Status: new == Date Submitted: 2015-05-14 19:16 CEST Last Modified: 2015-05-14 19:16 CEST == Summary:Allow ALIAS of IMPORTED targets Description: As discussed in http://thread.gmane.org/gmane.comp.programming.tools.cmake.user/52452 == Issue History Date ModifiedUsername FieldChange == 2015-05-14 19:16 Stephen Kelly New Issue == -- 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: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [CMake] Making the export function output relative paths
John van der Burg wrote:
I basically need everything relative to the ${CUSTOM_ROOT} folder.
Any hints/help would be appreciated :)
Use install(EXPORT) instead:
http://www.cmake.org/cmake/help/v3.0/manual/cmake-packages.7.html
http://www.cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f79d6025
Thanks,
Steve.
--
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:
http://public.kitware.com/mailman/listinfo/cmake
[Cmake-commits] CMake branch, next, updated. v3.2.2-2725-gcb96996
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 cb96996cfef31f71e2a9443897369cdeab79728c (commit) via e1f35f1fd2dc620b9f8e030e2daa960dc2908222 (commit) from 355a81aed21eaa1a8ba74c981624501344157109 (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 - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=cb96996cfef31f71e2a9443897369cdeab79728c commit cb96996cfef31f71e2a9443897369cdeab79728c Merge: 355a81a e1f35f1 Author: Stephen Kelly steve...@gmail.com AuthorDate: Thu May 14 13:20:10 2015 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Thu May 14 13:20:10 2015 -0400 Merge topic 'disallow-install-of-export' into next e1f35f1f fixup! install: Disallow installing export() result. http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e1f35f1fd2dc620b9f8e030e2daa960dc2908222 commit e1f35f1fd2dc620b9f8e030e2daa960dc2908222 Author: Stephen Kelly steve...@gmail.com AuthorDate: Thu May 14 19:19:52 2015 +0200 Commit: Stephen Kelly steve...@gmail.com CommitDate: Thu May 14 19:19:52 2015 +0200 fixup! install: Disallow installing export() result. diff --git a/Help/policy/CMP0062.rst b/Help/policy/CMP0062.rst index 632cfc2..e2f5a5a 100644 --- a/Help/policy/CMP0062.rst +++ b/Help/policy/CMP0062.rst @@ -12,7 +12,7 @@ configuration. The :command:`install(EXPORT)` generates and installs files which contain :ref:`Imported Targets`. These files are generated with relative paths (unless the user specifies absolute paths), and are designed for -multi-configuration use. +multi-configuration use. See :ref:`Creating Packages` for more. CMake 3.3 no longer allows the use of the :command:`install(FILES)` command with the result of the :command:`export()` command. --- Summary of changes: Help/policy/CMP0062.rst |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/mailman/listinfo/cmake-commits
[cmake-developers] [CMake 0015570]: Review POSITION_INDEPENDENT_CODE use of -fPIE
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15570 == Reported By:Stephen Kelly Assigned To: == Project:CMake Issue ID: 15570 Category: (No Category) Reproducibility:have not tried Severity: minor Priority: normal Status: new == Date Submitted: 2015-05-14 20:22 CEST Last Modified: 2015-05-14 20:22 CEST == Summary:Review POSITION_INDEPENDENT_CODE use of -fPIE Description: cmLocalGenerator::AddPositionIndependentFlags uses -fPIE for executables and -fPIC for libraries. This caused issues in Qt: https://bugreports.qt.io/browse/QTBUG-45755 https://codereview.qt-project.org/#/c/112060/ https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65886 Someone who understands the terms-of-art used in the discussion should review what cmake is doing here. == Issue History Date ModifiedUsername FieldChange == 2015-05-14 20:22 Stephen Kelly New Issue == -- 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: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [CMake] CMAKE_CXX_COMPILER_VERSION quite a useful variable, right?
Hi Niels.
I can't comment on the useful variable list, but I'd just like to point
out that the variable is not undocumented. It's listed normally in the
variables for languages section (
http://www.cmake.org/cmake/help/v3.2/manual/cmake-variables.7.html#variables-for-languages)
of the documentation as CMAKE_LANG_COMPILER_VERSION; that's because it
can be set for all enabled languages, not just CXX.
http://www.cmake.org/cmake/help/v3.2/variable/CMAKE_LANG_COMPILER_VERSION.html
Petr
On Thu, May 14, 2015 at 6:18 PM, Niels Dekker - address until 2018
niels_dekker_address_until_2...@xs4all.nl wrote:
When CMake (current version: 3.2.2) generates project files for Visual
Studio, it appears to define an undocumented variable that seems quite
useful to me: CMAKE_CXX_COMPILER_VERSION. It appears to be the full
compiler version. For example, for my VS2010 installation,
CMAKE_CXX_COMPILER_VERSION is 16.0.40219.1, and for my VS2013
installation, CMAKE_CXX_COMPILER_VERSION is 18.0.31101.0.
It seems useful to me to pass this CMake variable to the resource
compiler, which does not have direct access to the macro's predefined by
the C++ compiler (like _MSC_FULL_VER and _MSC_BUILD), for example by adding
a -D flag:
add_definitions(-DMY_COMPILER_VERSION=${CMAKE_CXX_COMPILER_VERSION})
Do you agree that it would be a good idea to add
CMAKE_CXX_COMPILER_VERSION to the list of useful CMake variables, at
http://www.cmake.org/Wiki/CMake_Useful_Variables ?
Kind regards, Niels
--
Niels Dekker
Scientific programmer at LKEB
Leiden University Medical Center
--
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:
http://public.kitware.com/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:
http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] CMAKE_CXX_COMPILER_VERSION quite a useful variable, right?
Am Donnerstag, 14. Mai 2015, 18:18:24 schrieb Niels Dekker - address until
2018:
When CMake (current version: 3.2.2) generates project files for Visual
Studio, it appears to define an undocumented variable that seems quite
useful to me: CMAKE_CXX_COMPILER_VERSION. It appears to be the full
compiler version. For example, for my VS2010 installation,
CMAKE_CXX_COMPILER_VERSION is 16.0.40219.1, and for my VS2013
installation, CMAKE_CXX_COMPILER_VERSION is 18.0.31101.0.
It seems useful to me to pass this CMake variable to the resource
compiler, which does not have direct access to the macro's predefined
by the C++ compiler (like _MSC_FULL_VER and _MSC_BUILD), for example
by adding a -D flag:
add_definitions(-DMY_COMPILER_VERSION=${CMAKE_CXX_COMPILER_VERSION})
Do you agree that it would be a good idea to add
CMAKE_CXX_COMPILER_VERSION to the list of useful CMake variables, at
http://www.cmake.org/Wiki/CMake_Useful_Variables ?
$ cmake --help-variable 'CMAKE_LANG_COMPILER_VERSION'
CMAKE_LANG_COMPILER_VERSION
-
Compiler version string.
Compiler version in major[.minor[.patch[.tweak]]] format. This
variable is not guaranteed to be defined for all compilers or
languages.
signature.asc
Description: This is a digitally signed message part.
--
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:
http://public.kitware.com/mailman/listinfo/cmake
[CMake] FindModules.cmake quality + Kitware proposition
This is more of a remark, or something to get the ball rolling, rather than anything else. I recently came across various FindModule.cmake files (FindOpenCL, FindOpenGL, FindGLEW, FindGLM, FindSFML) as a sideeffect of a project I am developing, but have had my share with quite a few others (FindQt, RustCMake, FindOpenAL, FindBoost, …). My overall impression is that the quality of these modules is highly fluctuating to say the least. While generally the FindModules shipping with CMake as built-in scripts are usable, there is a fair amount of room for improvement. FindGLEW.cmake for eg. is terrible. I have never imagined that such a widely used library has a 7 line FindModule script. On Windows it is practically useless. As for nearly all other FindModule scripts, nearly none of them use target_include_libraries() that would allow for end-users of the scripts to not have to worry about include directories. Some projects strive at being cross-platform, but compiling them on Windows (mostly the GNU projects that aim on being Windows friendly) is massive pain. libJPEG to name just one provides nmake makefiles that are capable of producing Visual Studio 2010 project files at best (huuraay), and have undocumented external dependencies. These projects (and their users) cry out for CMake support. Here is a proposition to consider: Kitware generally has the philosphy with CMake being: do it yourself or hire us to do it. While on a corporate basis this is a legitimate approach, I as a poor academic fellow do not have 10.000$ to spare for a feature I so wish, neither do I have the time to educate myself in the internal ways of CMake to contribute. So all I do is hack, hack, hack all day. The Chocolatey project (a package manager for Windows) recently won a massive Kickstarter campaign that aimed solely increasing the overall quality of the project. With this campaign they aimed on growing from an ‘interesting idea’ to begin ‘mainstream’. With the money they won, they hired full time package moderators, developed automated scripts of facilitating authoring, wrote tutorials, created templates, and even managed to get the ball rolling with OneGet (Powershell 5.0 package manager manager) to adopt Chocolatey as the first supported public repo. I would suggest Kitware start a similar community funded project to increase the overall quality of the software. While I do not have 10 grands to buy a feature, I do have 10 dollars pocket money to contribute (as do MANY others). As several levels of goals, the stock FindModules scripts could be brought to a homogenous quality, identical naming conventions (no more MYLIB_INC_DIR, MYLIB_INCLUDE_DIRS, MyLib_INCLUDE_DIR), high quality templates for new adopters, make the CMake Guide freely available online (epub, pdf, docx, whatever), convert 10 GNU projects to CMake, convert 50 GNU projects to CMake, create Snappy back-end of CPack, or my personal favorite (the feature I do not have 10.000 dollars for) is NMake batch mode support for multicore build, etc. There are so many places CMake itself can be improved, and so many users who really should be adopting, but have not started due to lacking man power. (These are the projects that would benefit the most from a freely available tutorial, because truth be told: writing capable, high-quality CMake scripts is no easy task.) If I were a charmismatic spokesperson I’d say: I RAISE 10 DOLLARS, WHO’S WITH ME?! But because I’m not, I’ll just leave it here as a suggestion. Ideas?-- 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: http://public.kitware.com/mailman/listinfo/cmake
[CMake] CMAKE_CXX_COMPILER_VERSION quite a useful variable, right?
When CMake (current version: 3.2.2) generates project files for Visual
Studio, it appears to define an undocumented variable that seems quite
useful to me: CMAKE_CXX_COMPILER_VERSION. It appears to be the full
compiler version. For example, for my VS2010 installation,
CMAKE_CXX_COMPILER_VERSION is 16.0.40219.1, and for my VS2013
installation, CMAKE_CXX_COMPILER_VERSION is 18.0.31101.0.
It seems useful to me to pass this CMake variable to the resource
compiler, which does not have direct access to the macro's predefined
by the C++ compiler (like _MSC_FULL_VER and _MSC_BUILD), for example
by adding a -D flag:
add_definitions(-DMY_COMPILER_VERSION=${CMAKE_CXX_COMPILER_VERSION})
Do you agree that it would be a good idea to add
CMAKE_CXX_COMPILER_VERSION to the list of useful CMake variables, at
http://www.cmake.org/Wiki/CMake_Useful_Variables ?
Kind regards, Niels
--
Niels Dekker
Scientific programmer at LKEB
Leiden University Medical Center
--
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:
http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Target_link_libraries imported library
Lars wrote: There is one problem with this setup and that is the IMPORTED_LINK_INTERFACE_LIBRARIES_RELEASE contains a static path to a boost lib. So the c:\boost\lib\boost_filesystem-vc110-mt-1_55.lib is appended to the linking of bar-library and this will fail if the path is incorrect. We cannot guarantee that boost is located at the same path on all Windows system. So how can we remove or update the boost path? The cmake-packages(7) manual in master describes this case (and used to mention Boost explicitly) http://www.cmake.org/cmake/help/git-master/manual/cmake-packages.7.html#creating-relocatable-packages http://www.cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3af13782 Another option not listed at the end there would be to create IMPORTED targets for Boost yourself and maintain that. You could create a wrapper around FindBoost. The ideal situation would be for Boost to ship cmake-config-packages itself, but that suggestion doesn't get much support from Boost devs (probably because they are not cmake fans :) ). Thanks, Steve. -- 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: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] [CPACK] [RPM] Using %if in %file section
I would like to end up with the following in the specs file:
...
%file
...
%if 0%{fedora} = 14
/path/to/some/file
%endif
I tried to use CPACK_RPM_USER_FILELIST as
set(CPACK_RPM_USER_FILELIST ${CPACK_RPM_USER_FILELIST}
%if 0%{fedora} = 14
/path/to/some/file
%endif
)
but this results in
%if 0%{fedora} = 14
/path/to/some/file
%endif %endif
which is not quite right.
Is there something I am missing? Or is it a fundamental limitation of CPack
RPM generator?
This seems to be a bug in CPackRPM. Please report it in bug tracker.
If so, would there be any workaround? Thanks in advance for
any help.
You could either fix it in CPackRPM.cmake and provide a patch.
Alternatively you could simply copy spec file template from
CPackRPM.cmake, save it into your own spec template file and extend it
with your own CPACK_* variable that will be substituted during
packaging. Then use CPACK_RPM_USER_BINARY_SPECFILE or
CPACK_RPM_COMPONENT_USER_BINARY_SPECFILE for component packages.
See documentation of this variable for details:
http://www.cmake.org/cmake/help/v3.2/module/CPackRPM.html
Regards,
Domen
--
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:
http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] FindModules.cmake quality + Kitware proposition
Tried jom years ago. Still chokes on Unicode paths. Thanks, Máté ps.: I had a feeling this is as much feedback as I’ll get. Feladó: Stephen Kelly Elküldve: csütörtök, 2015. május 14. 18:08 Címzett: cmake@cmake.org Nagy-Egri Máté Ferenc via CMake wrote: ... NMake batch mode support for multicore build, etc. I suggest you look into 'jom'. Thanks, Steve. -- 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: http://public.kitware.com/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: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] FindModules.cmake quality + Kitware proposition
On 14-May-15 14:01, Nagy-Egri Máté Ferenc via CMake wrote: This is more of a remark, or something to get the ball rolling, rather than anything else. I recently came across various FindModule.cmake files (FindOpenCL, FindOpenGL, FindGLEW, FindGLM, FindSFML) as a sideeffect of a project I am developing, but have had my share with quite a few others (FindQt, RustCMake, FindOpenAL, FindBoost, …). My overall impression is that the quality of these modules is highly fluctuating to say the least. While generally the FindModules shipping with CMake as built-in scripts are usable, there is a fair amount of room for improvement. FindGLEW.cmake for eg. is terrible. I have never imagined that such a widely used library has a 7 line FindModule script. On Windows it is practically useless. As for nearly all other FindModule scripts, nearly none of them use target_include_libraries() that would allow for end-users of the scripts to not have to worry about include directories. Some projects strive at being cross-platform, but compiling them on Windows (mostly the GNU projects that aim on being Windows friendly) is massive pain. libJPEG to name just one provides nmake makefiles that are capable of producing Visual Studio 2010 project files at best (huuraay), and have undocumented external dependencies. These projects (and their users) cry out for CMake support. Here is a proposition to consider: This sounds like a workaround for the existing problems. What we really need to do to solve this issue completely is to use automatically generated Find-like modules - PackageConfig.cmake. See: http://www.cmake.org/cmake/help/v3.2/manual/cmake-packages.7.html#creating-packages Kitware generally has the philosphy with CMake being: do it yourself or hire us to do it. While on a corporate basis this is a legitimate approach, I as a poor academic fellow do not have 10.000$ to spare for a feature I so wish, neither do I have the time to educate myself in the internal ways of CMake to contribute. So all I do is hack, hack, hack all day. The Chocolatey project (a package manager for Windows) recently won a massive Kickstarter campaign that aimed solely increasing the overall quality of the project. With this campaign they aimed on growing from an ‘interesting idea’ to begin ‘mainstream’. With the money they won, they hired full time package moderators, developed automated scripts of facilitating authoring, wrote tutorials, created templates, and even managed to get the ball rolling with OneGet (Powershell 5.0 package manager manager) to adopt Chocolatey as the first supported public repo. I would suggest Kitware start a similar community funded project to increase the overall quality of the software. While I do not have 10 grands to buy a feature, I do have 10 dollars pocket money to contribute (as do MANY others). As several levels of goals, the stock FindModules scripts could be brought to a homogenous quality, identical naming conventions (no more MYLIB_INC_DIR, MYLIB_INCLUDE_DIRS, MyLib_INCLUDE_DIR), high quality templates for new adopters, make the CMake Guide freely available online (epub, pdf, docx, whatever), convert 10 GNU projects to CMake, convert 50 GNU projects to CMake, create Snappy back-end of CPack, or my personal favorite (the feature I do not have 10.000 dollars for) is NMake batch mode support for multicore build, etc. There are so many places CMake itself can be improved, and so many users who really should be adopting, but have not started due to lacking man power. (These are the projects that would benefit the most from a freely available tutorial, because truth be told: writing capable, high-quality CMake scripts is no easy task.) If I were a charmismatic spokesperson I’d say: I RAISE 10 DOLLARS, WHO’S WITH ME?! But because I’m not, I’ll just leave it here as a suggestion. Ideas? Have you seen https://www.bountysource.com/ ? Ruslo -- 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: http://public.kitware.com/mailman/listinfo/cmake
[CMake] Trouble getting install script to actually run during packaging
I have a bit of Cmake code that I can not seem to figure out how to get to
actually run during cpack. HEre is the code:
GET_FILENAME_COMPONENT (SELF_DIR ${CMAKE_CURRENT_LIST_FILE} PATH)
configure_file(${SELF_DIR}/Deploy_ITK_Libs.sh.in
${DREAM3DProj_BINARY_DIR}/Deploy_ITK_Libs.sh @ONLY
IMMEDIATE)
FILE(WRITE ${DREAM3DProj_BINARY_DIR}/Deploy_ITK_Libs.cmake
execute_process(COMMAND \/bin/bash
${DREAM3DProj_BINARY_DIR}/Deploy_ITK_Libs.sh \${CMAKE_INSTALL_PREFIX}\) )
FILE(APPEND ${DREAM3DProj_BINARY_DIR}/Deploy_ITK_Libs.cmake
\n\nMESSAGE(STATUS \@ THIS IS DONE @@@\)\n)
INSTALL(CODE execute_process(COMMAND \/bin/bash
${DREAM3DProj_BINARY_DIR}/Deploy_ITK_Libs.sh \${CMAKE_INSTALL_PREFIX}\)
COMPONENT Applications)
install(SCRIPT ${DREAM3DProj_BINARY_DIR}/Deploy_ITK_Libs.cmake
COMPONENT Applications)
After I build I run cpack from the command line. I see _other_ scripts
that I have configured run but not _this_ script. I have verified that the
cmake code is actually executing as I get a new script file each time I run
cmake. I am sure I am missing something simple at this point but I just can
not see it.
This is on Linux Mint 17.x with CMake 3.1.0.
Thanks for any help
_
Mike Jackson mike.jack...@bluequartz.net
BlueQuartz Softwarewww.bluequartz.net
Principal Software Engineer Dayton, Ohio
--
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:
http://public.kitware.com/mailman/listinfo/cmake
[Cmake-commits] CMake branch, next, updated. v3.2.2-2749-gd323bfa
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 d323bfaf8284f2b16474fb3794b23b3b57e5b653 (commit) via 5c2524334f83eab94d73dd10dc630f71a6892592 (commit) via 8d55f802870a31cc053fe55a5ec0ea630c1b647f (commit) from 227ca70895241d98aa6a5bc480290968692ad8c4 (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 - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d323bfaf8284f2b16474fb3794b23b3b57e5b653 commit d323bfaf8284f2b16474fb3794b23b3b57e5b653 Merge: 227ca70 5c25243 Author: Stephen Kelly steve...@gmail.com AuthorDate: Thu May 14 15:38:19 2015 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Thu May 14 15:38:19 2015 -0400 Merge topic 'disallow-install-of-export' into next 5c252433 fixup! install: Disallow installing export() result. 8d55f802 fixup! install: Disallow installing export() result. http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5c2524334f83eab94d73dd10dc630f71a6892592 commit 5c2524334f83eab94d73dd10dc630f71a6892592 Author: Stephen Kelly steve...@gmail.com AuthorDate: Thu May 14 21:31:51 2015 +0200 Commit: Stephen Kelly steve...@gmail.com CommitDate: Thu May 14 21:33:56 2015 +0200 fixup! install: Disallow installing export() result. diff --git a/Help/release/dev/disallow-install-of-export.rst b/Help/release/dev/disallow-install-of-export.rst new file mode 100644 index 000..baee26d --- /dev/null +++ b/Help/release/dev/disallow-install-of-export.rst @@ -0,0 +1,5 @@ +disallow-install-of-export +-- + +* Using the output of :command:`export()` with the :command:`install(FILES)` + command is no longer allowed. See policy :policy:`CMP0062` for details. http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8d55f802870a31cc053fe55a5ec0ea630c1b647f commit 8d55f802870a31cc053fe55a5ec0ea630c1b647f Author: Stephen Kelly steve...@gmail.com AuthorDate: Thu May 14 21:29:55 2015 +0200 Commit: Stephen Kelly steve...@gmail.com CommitDate: Thu May 14 21:33:56 2015 +0200 fixup! install: Disallow installing export() result. diff --git a/Source/cmPolicies.h b/Source/cmPolicies.h index 7df4ee2..eb56494 100644 --- a/Source/cmPolicies.h +++ b/Source/cmPolicies.h @@ -213,7 +213,7 @@ class cmPolicy; CTest does not by default tell make to ignore errors (-i)., \ 3, 3, 0, cmPolicies::WARN) \ SELECT(POLICY, CMP0062, \ -Disallow install() of export() result, \ +Disallow install() of export() result., \ 3, 3, 0, cmPolicies::WARN) #define CM_SELECT_ID(F, A1, A2, A3, A4, A5, A6) F(A1) diff --git a/Tests/RunCMake/install/CMP0062-WARN-stderr.txt b/Tests/RunCMake/install/CMP0062-WARN-stderr.txt index 64e3c81..12ae745 100644 --- a/Tests/RunCMake/install/CMP0062-WARN-stderr.txt +++ b/Tests/RunCMake/install/CMP0062-WARN-stderr.txt @@ -1,7 +1,7 @@ CMake Warning \(dev\) at CMP0062-WARN.cmake:[0-9]+ \(install\): - Policy CMP0062 is not set: Disallow install\(\) of export\(\) result Run cmake - --help-policy CMP0062 for policy details. Use the cmake_policy command to - set the policy and suppress this warning. + Policy CMP0062 is not set: Disallow install\(\) of export\(\) result. Run + cmake --help-policy CMP0062 for policy details. Use the cmake_policy + command to set the policy and suppress this warning. The file --- Summary of changes: Help/release/dev/disallow-install-of-export.rst |5 + Source/cmPolicies.h |2 +- Tests/RunCMake/install/CMP0062-WARN-stderr.txt |6 +++--- 3 files changed, 9 insertions(+), 4 deletions(-) create mode 100644 Help/release/dev/disallow-install-of-export.rst hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, next, updated. v3.2.2-2751-g6b5cb92
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 6b5cb9289b4d9d5918159a53c870ea9f84cc9e02 (commit)
via b85d3b66c63afa1ce7f30439deee524241b1efdc (commit)
from d323bfaf8284f2b16474fb3794b23b3b57e5b653 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6b5cb9289b4d9d5918159a53c870ea9f84cc9e02
commit 6b5cb9289b4d9d5918159a53c870ea9f84cc9e02
Merge: d323bfa b85d3b6
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Thu May 14 15:38:41 2015 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Thu May 14 15:38:41 2015 -0400
Merge topic 'disallow-install-of-export' into next
b85d3b66 install: Disallow installing export() result.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b85d3b66c63afa1ce7f30439deee524241b1efdc
commit b85d3b66c63afa1ce7f30439deee524241b1efdc
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Thu May 14 19:08:27 2015 +0200
Commit: Stephen Kelly steve...@gmail.com
CommitDate: Thu May 14 21:38:29 2015 +0200
install: Disallow installing export() result.
diff --git a/Help/manual/cmake-policies.7.rst b/Help/manual/cmake-policies.7.rst
index e59cce7..2cc3a47 100644
--- a/Help/manual/cmake-policies.7.rst
+++ b/Help/manual/cmake-policies.7.rst
@@ -119,3 +119,4 @@ All Policies
/policy/CMP0059
/policy/CMP0060
/policy/CMP0061
+ /policy/CMP0062
diff --git a/Help/policy/CMP0062.rst b/Help/policy/CMP0062.rst
new file mode 100644
index 000..e2f5a5a
--- /dev/null
+++ b/Help/policy/CMP0062.rst
@@ -0,0 +1,27 @@
+CMP0062
+---
+
+Disallow install() of export() result.
+
+The :command:`export()` command generates a file containing
+:ref:`Imported Targets`, which is suitable for use from the build
+directory. It is not suitable for installation because it contains absolute
+paths to buildsystem locations, and is particular to a single build
+configuration.
+
+The :command:`install(EXPORT)` generates and installs files which contain
+:ref:`Imported Targets`. These files are generated with relative paths
+(unless the user specifies absolute paths), and are designed for
+multi-configuration use. See :ref:`Creating Packages` for more.
+
+CMake 3.3 no longer allows the use of the :command:`install(FILES)` command
+with the result of the :command:`export()` command.
+
+The ``OLD`` behavior for this policy is to allow installing the result of
+an :command:`export()` command. The ``NEW`` behavior for this policy is
+not to allow installing the result of an :command:`export()` command.
+
+This policy was introduced in CMake version 3.3. CMake version
+|release| warns when the policy is not set and uses ``OLD`` behavior. Use
+the :command:`cmake_policy()` command to set it to ``OLD`` or ``NEW``
+explicitly.
diff --git a/Help/release/dev/disallow-install-of-export.rst
b/Help/release/dev/disallow-install-of-export.rst
new file mode 100644
index 000..baee26d
--- /dev/null
+++ b/Help/release/dev/disallow-install-of-export.rst
@@ -0,0 +1,5 @@
+disallow-install-of-export
+--
+
+* Using the output of :command:`export()` with the :command:`install(FILES)`
+ command is no longer allowed. See policy :policy:`CMP0062` for details.
diff --git a/Source/cmInstallCommand.cxx b/Source/cmInstallCommand.cxx
index 24de1b5..899b088 100644
--- a/Source/cmInstallCommand.cxx
+++ b/Source/cmInstallCommand.cxx
@@ -871,6 +871,47 @@ bool
cmInstallCommand::HandleFilesMode(std::vectorstd::string const args)
return false;
}
+ cmPolicies::PolicyStatus status =
+ this-Makefile-GetPolicyStatus(cmPolicies::CMP0062);
+
+ cmGlobalGenerator *gg = this-Makefile-GetGlobalGenerator();
+ for(std::vectorstd::string::const_iterator fileIt = filesVector.begin();
+ fileIt != filesVector.end(); ++fileIt)
+{
+if (gg-IsExportedTargetsFile(*fileIt))
+ {
+ const char *modal = 0;
+ std::ostringstream e;
+ cmake::MessageType messageType = cmake::AUTHOR_WARNING;
+
+ switch(status)
+{
+case cmPolicies::WARN:
+ e cmPolicies::GetPolicyWarning(cmPolicies::CMP0062) \n;
+ modal = should;
+case cmPolicies::OLD:
+ break;
+case cmPolicies::REQUIRED_IF_USED:
+case cmPolicies::REQUIRED_ALWAYS:
+case cmPolicies::NEW:
+ modal = may;
+ messageType = cmake::FATAL_ERROR;
+}
+ if (modal)
+{
+e The file\n*fileIt \nwas generated by the export()
+ command. It modal not be installed with the
+ install() command. Use the install(EXPORT) mechanism
+ instead.
Re: [CMake] FindModules.cmake quality + Kitware proposition
Nagy-Egri MC!tC\) Ferenc via CMake wrote: Tried jom years ago. Still chokes on Unicode paths. Ok, I guess the jom developers are the ones to discuss that issue with. Thanks, Steve. -- 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: http://public.kitware.com/mailman/listinfo/cmake
[Cmake-commits] CMake branch, next, updated. v3.2.2-2746-g227ca70
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 227ca70895241d98aa6a5bc480290968692ad8c4 (commit)
via ce167b546d078d9f699248688ff5f16c7ecf15c7 (commit)
via 7baef756493caaabc226c39c4a8dad669b883d4d (commit)
via 63255342c63fa60926c8cef5d0cdcf372f977b5f (commit)
via 894961af16c83beb785b3d0fa7d1e6b80946eaac (commit)
via 115e9199822a6c9395cc3bb55c57e061b5fc6315 (commit)
via c5059c900036fd9500d64fbd7f9d2d3631152295 (commit)
via b17686d2bbc193f19c60cdf44a228e49b4ffe386 (commit)
via ed41a8e7b4cf665ebab8e4780f8b0b299113fd11 (commit)
via 48a9e91b02090ba263cd46ef5c33ba3d2aa873ba (commit)
via e7f7c2e208a62c60e4a20ef115ba47a2ff7194a1 (commit)
via c5cb3a734dd6d2472f10379d45dcec7ce03293d9 (commit)
via 76b598319ffe507870f918cdafe7ba7d43d9e195 (commit)
via 34c9ee2ed75e12c713bb49c699ac1dd882d1b8fa (commit)
via 3837c48334ff670d9132f80e35a31e263b21d3a1 (commit)
via b317b38d3345a648c99a549e30cc50868e89c516 (commit)
via 948676981e3aa76dd588ca5a7466e2969dc3 (commit)
via a3139d4b1512195485cde49d919a13cdaec62660 (commit)
via 443f041c2fa0355b9b622337da0612ce48cf29b6 (commit)
from 00d5f20395866c70ed04842685290554d97daf64 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=227ca70895241d98aa6a5bc480290968692ad8c4
commit 227ca70895241d98aa6a5bc480290968692ad8c4
Merge: 00d5f20 ce167b5
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Thu May 14 15:28:37 2015 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Thu May 14 15:28:37 2015 -0400
Merge topic 'refactor-cmLocalGenerator' into next
ce167b54 cmMakefile: Handle CMP0014 before configuring the generator.
7baef756 cmLocalGenerator: Assert that there is a parent.
63255342 cmMakefile: Remove redundant variable set.
894961af cmMakefile: Use the state to determine the parent directory.
115e9199 Use new top-level check abstraction.
c5059c90 cmLocalGenerator: Add abstraction to check if top-level.
b17686d2 cmGlobalGenerator: Move some flags from cmLocalGenerator.
ed41a8e7 cmLocalGenerator: Port loops to cmState::Snapshot.
48a9e91b cmState: Add an accessor for Parent snapshot and a validity check.
e7f7c2e2 cmLocalGenerator: Convert two recursive methods to loops.
c5cb3a73 cmLocalGenerator: Get project directories from the cmState.
76b59831 cmLocalGenerator: Initialize state before creating cmMakefile.
34c9ee2e cmLocalGenerator: Require a global generator in the constructor.
3837c483 Tests: Add case for 'ctest' run with bad CTestTestfile
b317b38d cmGlobalBorlandMakefileGenerator: Do not inherit from NMake
generator
94867698 Don't use a cmLocalGenerator instance to call static methods.
...
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ce167b546d078d9f699248688ff5f16c7ecf15c7
commit ce167b546d078d9f699248688ff5f16c7ecf15c7
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Thu May 14 21:18:06 2015 +0200
Commit: Stephen Kelly steve...@gmail.com
CommitDate: Thu May 14 21:26:13 2015 +0200
cmMakefile: Handle CMP0014 before configuring the generator.
diff --git a/Source/cmLocalGenerator.cxx b/Source/cmLocalGenerator.cxx
index 492ea9d..74362ae 100644
--- a/Source/cmLocalGenerator.cxx
+++ b/Source/cmLocalGenerator.cxx
@@ -192,43 +192,8 @@ void cmLocalGenerator::ReadInputFile()
// Look for the CMakeLists.txt file.
std::string currentStart = this-StateSnapshot.GetCurrentSourceDirectory();
currentStart += /CMakeLists.txt;
- if(cmSystemTools::FileExists(currentStart.c_str(), true))
-{
-this-Makefile-ProcessBuildsystemFile(currentStart.c_str());
-return;
-}
-
- assert(this-Parent);
-
- // The file is missing. Check policy CMP0014.
- cmMakefile* mf = this-Parent-GetMakefile();
- std::ostringstream e;
- e The source directory\n
- this-StateSnapshot.GetCurrentSourceDirectory() \n
- does not contain a CMakeLists.txt file.;
- switch (mf-GetPolicyStatus(cmPolicies::CMP0014))
-{
-case cmPolicies::WARN:
- // Print the warning.
- e \n
- CMake does not support this case but it used
- to work accidentally and is being allowed for
- compatibility.
- \n
- cmPolicies::GetPolicyWarning(cmPolicies::CMP0014);
- mf-IssueMessage(cmake::AUTHOR_WARNING, e.str());
-case cmPolicies::OLD:
- // OLD behavior does not warn.
- return;
-case cmPolicies::REQUIRED_IF_USED:
-case cmPolicies::REQUIRED_ALWAYS:
- e \n
-
[CMake] OSX xcodebuild not rebuilding objects?
Has anyone else run into errors rebuilding objects using the Xcode generator? I imagine it would be a bug in xcodebuild, not cmake. We've been using incremental builds, rather than clean builds, for years with cmake on GNU/Linux (make), OSX (Xcode), and Windows (MSVC) and this is the first time I've ever seen this. One of our C++ unit tests got a bus error on OSX and while debugging it became clear that one of our object files was not rebuilt after a header file had changed (obviously very bad). Looking at the build directory, the object file was definitely NOT rebuilt when it should have been: the object file's time-last-modified was April 29, the object file's .d file contained the fully-qualified path to the header file in question, and the time-last-modified on the header file was May 12. The build log shows other object files being rebuilt, but not this one. There's absolutely nothing special about this file: it's just a standard C++ source file and appears in a list of similar C++ files in my CMakeLists.txt file. I've never seen this happen before, has anyone else run into it? This makes me very concerned! $ cmake --version cmake version 3.1.0 $ xcodebuild -version Xcode 6.2 Build version 6C131e $ sw_vers ProductName:Mac OS X ProductVersion: 10.9.5 BuildVersion: 13F1066 -- 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: http://public.kitware.com/mailman/listinfo/cmake
[CMake] Where do all the extra clang flags come from in Xcode?
I was comparing the command line used when we choose an Xcode generator on our OSX systems, vs. the command line used when we choose a Makefile generator. We certainly have nothing in our CMakeLists.txt which sets compiler flags based on the type of generator, only based on the type of compiler (GCC, Clang, etc.) But, when I look at the compiler and flags used by the Makefile generator it uses /usr/bin/c++ (which is clang++ underneath) and it's basically only the the compiler flags that we provided. When I look at the compiler and flags used by the Xcode generator, not only does it use a different path to the compiler (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x c++) but, more concerning (because I assume that /usr/bin/clang++ eventually gets down to the same actual compiler as above) but it contains a huge number of extra flags, for example it appears to disable all sorts of warnings (that we don't want disabled): -Wno-missing-prototypes, -Wno-return-type, -Wno-non-virtual-dtor, -Wno-overloaded-virtual, etc. etc. This means people who build on OSX using Makefile generators see extra warnings that people who build on OSX using Xcode don't see. Where are these extra flags all coming from? Is it from Xcode itself somehow? Can I keep them from being added? I don't want peoples' personal Xcode settings to disable warnings during compilation! Note these are build servers and so no one is actually invoking Xcode: we log in via SSH, use cmake to generate the Xcode project files, then use cmake -build (which runs xcodebuild) to run the build itself. -- 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: http://public.kitware.com/mailman/listinfo/cmake
[cmake-developers] [CMake 0015568]: Bashism in Squish4RunTestCase.sh
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=15568 == Reported By:Felix Geyer Assigned To: == Project:CMake Issue ID: 15568 Category: Modules Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2015-05-14 05:31 EDT Last Modified: 2015-05-14 05:31 EDT == Summary:Bashism in Squish4RunTestCase.sh Description: Squish4RunTestCase.sh is not POSIX complient as it calls exit with a negative number. bash translates -1 to 255 but other shells suchs as dash don't accept this. The attached patch fixes this by replacing -1 with 255. == Issue History Date ModifiedUsername FieldChange == 2015-05-14 05:31 Felix GeyerNew Issue 2015-05-14 05:31 Felix GeyerFile Added: Squish4RunTestCase_bashism.diff == -- 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: http://public.kitware.com/mailman/listinfo/cmake-developers
[Cmake-commits] CMake branch, master, updated. v3.2.2-1128-gf6a41a4
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 f6a41a441408cb32fcc5fee1a758627cdf4f9031 (commit) from 36c275d857d1764f37df450361ed816d24091300 (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 - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f6a41a441408cb32fcc5fee1a758627cdf4f9031 commit f6a41a441408cb32fcc5fee1a758627cdf4f9031 Author: Kitware Robot kwro...@kitware.com AuthorDate: Fri May 15 00:01:06 2015 -0400 Commit: Kitware Robot kwro...@kitware.com CommitDate: Fri May 15 00:01:06 2015 -0400 CMake Nightly Date Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 73cda83..bb3c25c 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 2) -set(CMake_VERSION_PATCH 20150514) +set(CMake_VERSION_PATCH 20150515) #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 http://public.kitware.com/mailman/listinfo/cmake-commits
