Hei hei,
On Mon, May 13, 2013 at 06:17:58PM -0400, Matthew Woehlke wrote:
Another option to consider is keeping the file in an external
repository and using your VCS's external-repo support to bring it
into your other projects. This way the file exists in your source
tree, but your VCS is
Hi Matthew,
On Mon, 13 May 2013 18:17:58 -0400
Matthew Woehlke matthew.woeh...@kitware.com wrote:
On 2013-05-11 17:22, Shlomi Fish wrote:
many of my CMake-based projects carry a common top-level Common.cmake file
that I copy from one project to another and enhance, and since this is
Hi Jean-Christophe,
On Mon, 13 May 2013 18:27:03 -0400
Jean-Christophe Fillion-Robin jchris.filli...@kitware.com wrote:
Hi,
To download the common file(s) at configure time, you could follow the
approach discussed here:
Hi,
To download the common file(s) at configure time, you could follow the
approach discussed here:
http://cmake.3232098.n2.nabble.com/is-it-possible-to-download-CMake-modules-at-configure-time-td7583968.html#a7584113
Hth
Jc
On Mon, May 13, 2013 at 6:17 PM, Matthew Woehlke
Hi all,
many of my CMake-based projects carry a common top-level Common.cmake file
that I copy from one project to another and enhance, and since this is
duplicate code/functionality I would like to consolidate it.
What I want to be able to do is say something like:
CODE
INCLUDE(ShlomifCommon)
