t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index f90c0e7..0515f6c 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,7 +1,7 @@
# CMake version number components.
set(CMake_VERSION_MAJOR 3)
set(CMake_VERSION_MINOR 15)
-set(CMake_VERSION_PATCH 20191003)
+set(CMake_VER
On Fri, Oct 4, 2019 at 2:27 AM Dustyn Blasig wrote:
> Hi All,
>
> I have been cleaning up our legacy CMake to use newer features (available
> in 3.12+) including trying to use target_...() functions nearly
> exclusively. As part of this, I was toying with cleaning up our use cases
> for adding
On Thu, 2019-10-03 at 17:08 -0400, stefan wrote:
> Yes, that is exactly what I'm trying to do, but it doesn't seem to
> have any effect. That is, `dpkg --info ...` doesn't list the
> additional dependency, and correspondingly, running `apt-get install
> ...` on the component package file will
On 2019-10-03 4:59 p.m., Kyle Edwards wrote:
On Thu, 2019-10-03 at 16:42 -0400, stefan wrote:
My project is already using this style:
set(CPACK_COMPONENTS_ALL runtime development mstool)
i.e. all components are already defined. All that's missing is the
declaration of their
On 2019-10-03 4:37 p.m., Kyle Edwards wrote:
On Thu, 2019-10-03 at 16:30 -0400, stefan wrote:
Hi Kyle,
thanks for the quick followup.
On 2019-10-03 4:23 p.m., Kyle Edwards wrote:
Please take a look at cpack_add_component():
https://cmake.org/cmake/help/latest/module/CPackComponent.html
I'm
On Thu, 2019-10-03 at 16:30 -0400, stefan wrote:
> Hi Kyle,
> thanks for the quick followup.
> On 2019-10-03 4:23 p.m., Kyle Edwards wrote:
> > Please take a look at cpack_add_component():
> > https://cmake.org/cmake/help/latest/module/CPackComponent.html
> I'm not sure what specifically I should
Hi Kyle,
thanks for the quick followup.
On 2019-10-03 4:23 p.m., Kyle Edwards wrote:
Please take a look at cpack_add_component():
https://cmake.org/cmake/help/latest/module/CPackComponent.html
I'm not sure what specifically I should be looking for.
In general my setup is working fine, i.e.
On Thu, 2019-10-03 at 16:15 -0400, stefan wrote:
> I'm trying to generate (debian) packages for a project of mine using
> cmake. I need to generate multiple components ("runtime",
> "development", etc.). What is the expected way to have the
> "development" package depend on the "runtime" package ?
I'm trying to generate (debian) packages for a project of mine using
cmake. I need to generate multiple components ("runtime", "development",
etc.). What is the expected way to have the "development" package depend
on the "runtime" package ?
I'v been trying to play with the
Hi All,
I have been cleaning up our legacy CMake to use newer features (available
in 3.12+) including trying to use target_...() functions nearly
exclusively. As part of this, I was toying with cleaning up our use cases
for adding compiler flags and similar definitions using real targets and
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 d918b4a545fefd1593753189d83ec8590f430579 (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 4a68c85073f80fd8f96c93eb5b3ead3058c84391 (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, release has been updated
via b21e4e4a1511417956b1d6d07f49425747c400e2 (commit)
via
13 matches
Mail list logo
