On Mon, Aug 17, 2015 at 5:17 PM, James Johnston
wrote:
> [...] Your own CMake projects will be
> ExternalProjects to this high-level project and the superbuild would pass
> the location to your project via -D_DIR= so that
> find_package can locate the Config file.
>
I think a more convenient and
> -Original Message-
> From: rcdai...@gmail.com [mailto:rcdai...@gmail.com] On Behalf Of Robert
> Dailey
> Sent: Sunday, August 23, 2015 02:43
> To: James Johnston
> Cc: CMake
> Subject: Re: [CMake] How to depend on external cmake projects?
>
> On Mon, Aug
On Mon, Aug 17, 2015 at 10:17 AM, James Johnston
wrote:
> Well, you'd do this in conjunction with ExternalProject_Add. A well-written
> CMake external project will provide a Config.cmake file which you
> will then find using find_package.
After toying around with this idea for a bit, I've found
Robert,
1. If it's a library you are not modifying, only linking to, then you don't
need its targets in your projects. You just need to clone, build and
install it before running cmake for your actual project. It can be
accomplished in various ways:
- you can clone it as a submodule or manually b
> -Original Message-
> From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Robert
> Dailey
> Sent: Sunday, August 16, 2015 13:32
> To: CMake
> Subject: [CMake] How to depend on external cmake projects?
>
> There are certain repositories on Github I'd li
> -- Forwarded message --
> From: Robert Dailey
> To: CMake
> Cc:
> Date: Sun, 16 Aug 2015 08:32:08 -0500
> Subject: [CMake] How to depend on external cmake projects?
>
> There are certain repositories on Github I'd like to pull in as a
> depend
There are certain repositories on Github I'd like to pull in as a
dependency. These repositories already use CMake to build their source
code. Based on personal experience and reading material online, there
are a couple of different options:
1. Pull down the repository as a submodule to my own git
