[CMake] Building third party libraries along with normal targets

[Tamás Kenéz]

[about shell script portability]

We do use shell-scripts on Windows since git-bash comes with git for free.
Our workflow is centered around the command-line (git-bash for Windows) and
you can run shell scripts in git-bash, that's why compatibility is not a
problem. All our scripts and workflows are the same on all our platforms
(windows, linux, mac).

This is an issue only if you're not using git on Windows so adding git-bash
to the workflow would be an extra hassle.


On Thu, Mar 30, 2017 at 3:45 PM, Robert Dailey <rcdailey.lists at gmail.com>
wrote:

> On Thu, Mar 30, 2017 at 3:42 AM, Tamás Kenéz <tamas.kenez at gmail.com>
> wrote:
> > An alternative to the CMake superbuild: leave your actual project intact.
> > Simply create a separate shell script which builds all the dependencies
> (by
> > running cmake commands). Or, if you do like the ExternalProject stuff,
> > create a superbuild which builds only the dependencies.
>
> Problem with that is that it's not a portable solution. The #1 benefit
> of using CMake superbuilds (supplied with CMake build solution for the
> target library) is that it will function correctly on all platforms.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake/attachments/20170331/45d67da4/attachment.html>