[Cmake-commits] CMake branch, master, updated. v3.14.1-613-g7a5adae
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 7a5adae94dc8ca38fb2323742c6e4164682a876f (commit) from ffcb4f7ec5789fb62812b88f3909100a29277e44 (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=7a5adae94dc8ca38fb2323742c6e4164682a876f commit 7a5adae94dc8ca38fb2323742c6e4164682a876f Author: Kitware Robot AuthorDate: Sat Apr 6 00:01:08 2019 -0400 Commit: Kitware Robot CommitDate: Sat Apr 6 00:01:08 2019 -0400 CMake Nightly Date Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index f4dacb4..31c3ba8 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 14) -set(CMake_VERSION_PATCH 20190405) +set(CMake_VERSION_PATCH 20190406) #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
Re: [CMake] Better way than: SET(CMAKE_C_ARCHIVE_CREATE " my_flags ... ?
Additional issue with this CMAKE_C_ARCHIVE_CREATE hack: it's ignored and reverts back to the default in link.txt when building a "pure assembly" library without any .c file. Adding an empty.c file works around the problem. Is this expected? Reproduced with CMake 3.13 and 3.14.0. Le lun. 25 févr. 2019 à 11:41, Marc Herbert a écrit : > Hi, > > 1. I found the hack below in the list's archive. However it seems... > hackish. Among others it can't _append_ a flag, it can only replace all > flags. Any newer and better way to append some extra flags? > > 2. Bonus question: how would you query "ar" and append some extra flags > *only* when ar/ranlib are new enough to support them? > > Thanks in advance, > > Marc > > SET(CMAKE_C_ARCHIVE_CREATE " -qcD > ") > SET(CMAKE_C_ARCHIVE_FINISH " -D ") > > -- 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] Remove compilation flags for a given target
> > > in our code base we would like to add a warning compilation flags. > Nevertheless, this flag prevents us from compiling a few targets so we > would like to remove this flag for the given targets. > > Since I don't want to *add* a compilation flags but remove one, I would > like to retrieve the properties of the target > (get_target_property(my_compilation_flags TARGET COMPILE_FLAGS)), and > then modify those and use it to set the properties of the target. > Instead of removing, have you tried appending the -Wno-fubar flag that turns back off these specific warnings for these specific files? With gcc for instance: https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html "Each of these specific warning options also has a negative form beginning ‘-Wno-’ to turn off warnings; for example, -Wno-implicit. [...] For options of the same specificity, the last one takes effect" -- 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] Ubuntu CMake Repository Now Available
It would be great to see officialy supported rpm repository for CentOS/Fedora as well! Thank you in advance. пт, 5 апр. 2019 г., 22:17 Kyle Edwards via CMake : > All, > > I am pleased to announce that Kitware is now offering an > officially-supported set of Ubuntu packages for CMake. These CMake > packages can be installed with apt-get, just like other Ubuntu > packages. We currently support Ubuntu 16.04 and 18.04. > > The following packages are available: > > * cmake - Contains the CMake command line executable, CTest, and CPack. > * cmake-curses-gui - Contains ccmake. > * cmake-qt-gui - Contains cmake-gui. > * cmake-doc - Contains the CMake documentation. > > To use these packages, follow the instructions at > > https://apt.kitware.com/ > > to add our APT repository to your Ubuntu installation, and then use > apt-get install to install one or all of the above packages. > > We currently offer CMake 3.14.1, and will continue to update the > repository as new CMake releases are issued. > > Kyle > -- > > 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] Ubuntu CMake Repository Now Available
Thats great! Thank you! пт, 5 апр. 2019 г. в 22:17, Kyle Edwards via CMake : > > All, > > I am pleased to announce that Kitware is now offering an > officially-supported set of Ubuntu packages for CMake. These CMake > packages can be installed with apt-get, just like other Ubuntu > packages. We currently support Ubuntu 16.04 and 18.04. > > The following packages are available: > > * cmake - Contains the CMake command line executable, CTest, and CPack. > * cmake-curses-gui - Contains ccmake. > * cmake-qt-gui - Contains cmake-gui. > * cmake-doc - Contains the CMake documentation. > > To use these packages, follow the instructions at > > https://apt.kitware.com/ > > to add our APT repository to your Ubuntu installation, and then use > apt-get install to install one or all of the above packages. > > We currently offer CMake 3.14.1, and will continue to update the > repository as new CMake releases are issued. > > Kyle > -- > > 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
[CMake] Ubuntu CMake Repository Now Available
All, I am pleased to announce that Kitware is now offering an officially-supported set of Ubuntu packages for CMake. These CMake packages can be installed with apt-get, just like other Ubuntu packages. We currently support Ubuntu 16.04 and 18.04. The following packages are available: * cmake - Contains the CMake command line executable, CTest, and CPack. * cmake-curses-gui - Contains ccmake. * cmake-qt-gui - Contains cmake-gui. * cmake-doc - Contains the CMake documentation. To use these packages, follow the instructions at https://apt.kitware.com/ to add our APT repository to your Ubuntu installation, and then use apt-get install to install one or all of the above packages. We currently offer CMake 3.14.1, and will continue to update the repository as new CMake releases are issued. Kyle -- 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] Ubuntu CMake Repository Now Available
All, I am pleased to announce that Kitware is now offering an officially-supported set of Ubuntu packages for CMake. These CMake packages can be installed with apt-get, just like other Ubuntu packages. We currently support Ubuntu 16.04 and 18.04. The following packages are available: * cmake - Contains the CMake command line executable, CTest, and CPack. * cmake-curses-gui - Contains ccmake. * cmake-qt-gui - Contains cmake-gui. * cmake-doc - Contains the CMake documentation. To use these packages, follow the instructions at https://apt.kitware.com/ to add our APT repository to your Ubuntu installation, and then use apt-get install to install one or all of the above packages. We currently offer CMake 3.14.1, and will continue to update the repository as new CMake releases are issued. Kyle -- 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] Eclipse generator question
Am Freitag, 5. April 2019, 00:07:08 CEST schrieb Benjamin Shadwick: > Ah, it seems my CMake is too old to produce compile_commands.json. Maybe > this is part of why other IDEs are working better at home on Ubuntu MATE > LTS. > > Unfortunately Red Hat ships CMake 2.8.12.2 even in recent RHEL releases, > which is now approaching 5 years old (yikes!). Apparently they ship CMake > 3.13.4 as a 'cmake3' package and I didn't catch it - will see if I can > upgrade at least some of my machines. They don't! Maybe you find a more recent RPM at https://build.opensuse.org/ and ask the package maintainer there to also build it for RHEL. I took the same approach on our company-internal OBS. -- Cd wrttn wtht vwls s mch trsr. -- 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.14.1-612-gffcb4f7
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 ffcb4f7ec5789fb62812b88f3909100a29277e44 (commit)
via a9b38a17571bca0801594adf85fef59fac51d6ba (commit)
via 2024327746747989f47dec3859e2ca4bc66267c3 (commit)
from 52fb35bd69ec2fa1a5307695cb22c3f125debf4f (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=ffcb4f7ec5789fb62812b88f3909100a29277e44
commit ffcb4f7ec5789fb62812b88f3909100a29277e44
Merge: 52fb35b a9b38a1
Author: Brad King
AuthorDate: Fri Apr 5 12:51:18 2019 +
Commit: Kitware Robot
CommitDate: Fri Apr 5 08:51:25 2019 -0400
Merge topic 'rst-bad-markup-block'
a9b38a1757 cmRST: Fix crash on empty markup block
2024327746 Help: Remove empty literal block markup in RESOURCE target
property
Acked-by: Kitware Robot
Merge-request: !3197
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a9b38a17571bca0801594adf85fef59fac51d6ba
commit a9b38a17571bca0801594adf85fef59fac51d6ba
Author: Brad King
AuthorDate: Fri Apr 5 08:13:43 2019 -0400
Commit: Brad King
CommitDate: Fri Apr 5 08:18:14 2019 -0400
cmRST: Fix crash on empty markup block
diff --git a/Source/cmRST.cxx b/Source/cmRST.cxx
index b7216b0..2064275 100644
--- a/Source/cmRST.cxx
+++ b/Source/cmRST.cxx
@@ -457,6 +457,12 @@ void cmRST::UnindentLines(std::vector& lines)
size_t trailingEmpty =
std::distance(rit, cmFindNot(cmReverseRange(lines), std::string()));
+ if ((leadingEmpty + trailingEmpty) >= lines.size()) {
+// All lines are empty. The markup block is empty. Leave only one.
+lines.resize(1);
+return;
+ }
+
std::vector::iterator contentEnd = cmRotate(
lines.begin(), lines.begin() + leadingEmpty, lines.end() - trailingEmpty);
lines.erase(contentEnd, lines.end());
diff --git a/Tests/CMakeLib/testRST.expect b/Tests/CMakeLib/testRST.expect
index d7b91d1..c19ee94 100644
--- a/Tests/CMakeLib/testRST.expect
+++ b/Tests/CMakeLib/testRST.expect
@@ -83,6 +83,10 @@ or after a paragraph ending in two colons::
but not after a line ending in two colons::
in the middle of a paragraph.
+A literal block can be empty::
+
+
+
.. productionlist::
grammar: `production`
production: "content rendered"
diff --git a/Tests/CMakeLib/testRST.rst b/Tests/CMakeLib/testRST.rst
index 633219f..d2d1140 100644
--- a/Tests/CMakeLib/testRST.rst
+++ b/Tests/CMakeLib/testRST.rst
@@ -90,6 +90,10 @@ or after a paragraph ending in two colons::
but not after a line ending in two colons::
in the middle of a paragraph.
+A literal block can be empty::
+
+
+
.. productionlist::
grammar: `production`
production: "content rendered"
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2024327746747989f47dec3859e2ca4bc66267c3
commit 2024327746747989f47dec3859e2ca4bc66267c3
Author: Brad King
AuthorDate: Fri Apr 5 08:12:39 2019 -0400
Commit: Brad King
CommitDate: Fri Apr 5 08:18:14 2019 -0400
Help: Remove empty literal block markup in RESOURCE target property
This was added accidentally by commit 456e0fb64f (Help: Improve
documentation formating, 2019-04-01).
diff --git a/Help/prop_tgt/RESOURCE.rst b/Help/prop_tgt/RESOURCE.rst
index 6ada637..e5a1cb6 100644
--- a/Help/prop_tgt/RESOURCE.rst
+++ b/Help/prop_tgt/RESOURCE.rst
@@ -11,7 +11,7 @@ directory (eg. ``Resources`` directory for macOS) inside the
bundle.
On non-Apple platforms these files may be installed using the ``RESOURCE``
option to the :command:`install(TARGETS)` command.
-Following example of Application Bundle::
+Following example of Application Bundle:
.. code-block:: cmake
---
Summary of changes:
Help/prop_tgt/RESOURCE.rst| 2 +-
Source/cmRST.cxx | 6 ++
Tests/CMakeLib/testRST.expect | 4
Tests/CMakeLib/testRST.rst| 4
4 files changed, 15 insertions(+), 1 deletion(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits
Re: [CMake] Setting permissions with CPack/WiX installer
On Fri, Apr 5, 2019 at 5:25 AM Cook, Steven (G) wrote: > Hi all, > > > > I would like to set the permissions on some files and directories in my > WiX installer. It looks like the CPACK_WIX_ACL property should be suitable, > but I can’t get it to work. There are examples of its usage in this project: > > https://github.com/ngladitz/cmake-wix-testsuite/tree/master/properties > > > > Typically something like this: > > set_property(INSTALL > > empty_directory_with_property > > non_empty_directory_with_property > > PROPERTY CPACK_WIX_ACL “Everyone=GenericRead,GenericWrite,CreateFile” > > ) > > > > but this example doesn’t work for me with cmake 3.14.0. None of the .wxs > files that are produced contain the expected Permission property. After > adding some debugging to cmake, I found that > cmCPackWIXGenerator::AddDirectoryAndFileDefinitions calls GetInstalledFile, > which always returns NULL. This prevents the ACL from being applied. > Been a while since I looked at this but it still seems to work for me in 3.14.0. Corresponding elements are generated in files.wxs: Nils -- 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] Fake dependencies of executables to static libs
Hello Francis, On Thu, Apr 4, 2019 at 6:49 PM Francis Giraldeau < francis.girald...@gmail.com> wrote: > Maybe the problem is related to Cotire? I see that it is used in > mredis. I tried to reproduce the issue, and it behaves correctly. You > might want to try to reproduce using the following minimal repo: Alas, I can safely rule out cotire. I only included it a few months ago and the issue was already ages old by then. Also, it is optional and some use it, some don't. What comes to mind now as a possible explanation, as I just a minute ago noticed is what button to press. Perhaps it is a Visual Studio thing. When I, for example, work on the mredis lib I do that test driven using the various testing tools. Now in order to do this, I generally set the testing suite as "StartUp Project", as VC calls the currently active target. Then I press 'build target' (as opposed to 'build solution') or simply just "Debug", the green play button to run a test. When the source to the testing suite is changed, both operations cause build and link of the tool and then run it as they should. When I change a source in the lib they do not. However, when I press 'build solution', all dependent binaries do seem to be relinked. I just tested this. It's simply that I normally don't do this for low level testing builds because I don't need to build the whole solution just for one test. Interesting. I never noticed that. May this shed some light on the issue? Cheers, Stephan -- 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
