t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 4951c02..4571566 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 20190409)
+set(CMake_VER
> I have made a very simple example that generates a WIX installer for a
> single file but fails to set the permissions on the file. Do you have any
> suggestions of why this isn't working?
Problem solved - when cpack is run with no parameters, the permissions tags
are not generated, but when run
On April 9, 2019 1:51:52 PM MDT, "Gonzalo Garramuño" wrote:
>I had a resource.rc file and a resource.h file with just an ICON to
>provide the icon to my application. However, since a week or so ago,
>RC
>refuses to compile it, giving the not very helpful message:
>
>Microsoft (R) Windows (R)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, release has been updated
via 127d0ea2a660507c3f629bcf934e6863f60c09db (commit)
via
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 6aef0aa5fe2fa85342f3903f8e9ac0afdc62aa07 (commit)
via
Rebuilt for 18.04 and verified to depend on libcurl4. The new package
version is "3.14.1-0kitware1ubuntu18.04.1".
Kyle
On Tue, 2019-04-09 at 13:38 -0700, Benjamin Shadwick wrote:
> I believe it's possible to specify an "or" rule so that it would work
> with either package. It should probably
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 0a29875313566c12cbc16391fc23dbe2da8c5c18 (commit)
via
I believe it's possible to specify an "or" rule so that it would work with
either package. It should probably require the one it's built against
though, or at least prefer it if it works with both.
On Tue, Apr 9, 2019 at 12:32 PM Hahn, Steven E. via CMake
wrote:
> Would you consider updating
I had a resource.rc file and a resource.h file with just an ICON to
provide the icon to my application. However, since a week or so ago, RC
refuses to compile it, giving the not very helpful message:
Microsoft (R) Windows (R) Resource Compiler Version 6.3.9600.17336
Copyright (C) Microsoft
Would you consider updating the Ubuntu 18.04 package to depend on libcurl4?
Unfortunately libcurl3 conflicts with libcurl4, and I need to keep the later
installed for packages that depend on it. The Ubuntu-provided CMake package
appears to be built against libcurl4.
Steven
On 4/5/19, 3:17
I believe that your targets should be using something like:
target_compile_options(yourlib PRIVATE -Wwhatever)
They will be built with said warnings, but it won't be propagated to
consumers of the library. So you shouldn't have to remove anything.
On Tue, Apr 9, 2019 at 8:47 AM Benjamin Orgogozo
We are using a library that adds all of it's subdirectories to the include
search path (hundreds of directories and thousands of files). This is done
because they change their folder structure constantly (but we don't care as
we are upgrading every once in a while and can adjust).
We don't want
Hello,
We are using a large project that comes with it's own build and
configuration system.
We have multiple issues with this external build system and we want to move
the building of this project to cmake (as well as our code that depends on
it).
All the problems are related to the `build` step
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, release has been updated
via dff61585f3ed3973b52db9a90493f132d809677c (commit)
via
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 6b126c47bd0b90f2af9f800910054b3139667a73 (commit)
via
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 3d15ae4ea121ba68572f0314a93b756ed2659e09 (commit)
via
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 284429ac879a91fe00e6f2c773b9a0d187667b9b (commit)
via
On Fri, Apr 05, 2019 at 07:56:25PM -0700, Marc Herbert wrote:
>Instead of removing, have you tried appending the -Wno-fubar flag that
>turns back off these
>specific warnings for these specific files?
Ah, yes, it will actually work... Not the answer that I was expecting
but clearly a
On Thu, Apr 04, 2019 at 06:00:43PM +0200, Mateusz Loskot wrote:
> The list should rather be, in preference/priority order
>
> 1. https://cmake.org/cmake/help/latest/command/target_compile_options.html
> 2. add_compile_options
Yes, it's what I understood from documentation.
> Are you certain
Hi Nils,
> From a command line environment where your compiler is properly set up and
> ninja is in PATH configure the root of the project with the Ninja generator
> (currently hardcoded in the tests); use an out of source build directory and
> set the REFERENCE_CMAKE_BIN_DIR cache variable to
20 matches
Mail list logo
