[Cmake-commits] CMake branch, master, updated. v3.9.0-rc3-120-g3558fe0

[Kitware Robot]

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  3558fe06579d4c4148c01ee112cc492f91fd3045 (commit)
  from  e10c9ef1eb937abe8ace0aca7a5ad4d812e19b09 (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=3558fe06579d4c4148c01ee112cc492f91fd3045
commit 3558fe06579d4c4148c01ee112cc492f91fd3045
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Mon Jun 19 00:01:04 2017 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Mon Jun 19 00:01:04 2017 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 2088242..ec2cdd6 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 9)
-set(CMake_VERSION_PATCH 20170618)
+set(CMake_VERSION_PATCH 20170619)
 #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

Re: [CMake] Multiple projects in a single repo

[Sean Wayland]

Hi Dushara and all ,
I am another Aussie working on something similar ( each of our
applications also has a test application also ) ..
At the moment we have :
add_subdirectory in the top level cmakelists file
In each subdirectory the cmakelists file adds targets ..
some of the subdirectories are for libraries
some are for executables .
As well as our own library we also use other libraries like gtest,
boost, libmusicxml
We have had a bit of luck but getting everything to link properly is tricky.
Please let me know if you get anywhere!
If anyone can shed some light it might save me a lot of time ..
Linking boost or gtest are pretty simple its the shared library we
have written ourselves which is giving me a headache!

Best Sean


On Sun, Jun 18, 2017 at 10:02 PM, Dushara Jayasinghe
 wrote:
> Hi all,
>
> Here's a little puzzle that's got me scratching my head a bit. I've got a
> CMake project that is composed of two separate applications - let's call
> them system and recovery - that share a common library framework. I'd like
> to keep it all within a single repository.
>
> The applications are composed of multiple executables and shared libraries.
> What I would like to be able to do is to produces two install trees for the
> two applications with their respective library dependencies.
>
> Things I have attempted so far are:
>
> 1. Perform the build + install in sub-directories of each application:
>With this approach, the shared library files that the applications
>depend on don't get installed (they're in a sibling directory of the
>applications)
> 2. Creating two top level custom targets with the the application
>binaries as their dependencies: The build part works great (only the
>required binaries and libraries are built), but the install rule
>causes everything to be built (due to it's dependency on ALL)
>
> Method 2 seems promising if I can have a rule such as install/recovery or
> some such, but that doesn't seem possible for a custom target that doesn't
> generate anything.
>
> Has anyone else solved something like this before? Any suggestions?
>
> Thank you,
>
> Dushara
>
> --
>
> 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



-- 
www.seanwayland.com

Sean Wayland

licensed real estate salesperson
phone: 3475231455
-- 

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] Multiple projects in a single repo

[Dushara Jayasinghe]

Hi all,

Here's a little puzzle that's got me scratching my head a bit. I've got 
a CMake project that is composed of two separate applications - let's 
call them system and recovery - that share a common library framework. 
I'd like to keep it all within a single repository.


The applications are composed of multiple executables and shared 
libraries. What I would like to be able to do is to produces two install 
trees for the two applications with their respective library dependencies.


Things I have attempted so far are:

1. Perform the build + install in sub-directories of each application:
   With this approach, the shared library files that the applications
   depend on don't get installed (they're in a sibling directory of the
   applications)
2. Creating two top level custom targets with the the application
   binaries as their dependencies: The build part works great (only the
   required binaries and libraries are built), but the install rule
   causes everything to be built (due to it's dependency on ALL)

Method 2 seems promising if I can have a rule such as install/recovery 
or some such, but that doesn't seem possible for a custom target that 
doesn't generate anything.


Has anyone else solved something like this before? Any suggestions?

Thank you,

Dushara

--

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 PCH Prototype

[Daniel Pfeifer]

Hi Julian,

I have rebased my old precompiled-headers branch on master and created a
work-in-progress merge-request here:
https://gitlab.kitware.com/cmake/cmake/merge_requests/984

Cheers, Daniel


2017-06-15 13:38 GMT+02:00 Julian Landesberger :

> Hallo Daniel,
>
> wir hatten uns nach deinem Meetup-Vortrag letzte Woche kurz über die
> Verwaltung von precompiled headers in CMake unterhalten. Du meintest
> damals, du hättest bereits eine Art Prototyp dafür geschrieben, der aber
> noch nicht an "großen" Projekten getestet wurde, und, dass du ihn dafür zur
> Verfügung stellen könntest.
> Ich würde den Prototypen gerne am Simulationscode des Lehrstuhls für
> Computation in Engineering der TU München ausprobieren. Der hat immerhin
> über 6000 source- und header-Dateien, ist also kein kompaktes
> Beispielprojekt mehr.
>
> Würde mich freuen wenn wir da was machen könnten und beste Grüße!
>
> Julian Landesberger
>
-- 

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