[Ctk-developers] install CTK from ExternalProject_Add
Sascha Zelzer
s.zelzer at dkfz-heidelberg.de
Sun Jan 25 22:58:39 UTC 2015
Hi Miklos,
ExternalProject_Add() does not know if the external project has a
super-build structure itself or not. So calling "make install" on the
CTK superbuild level *should* do the right job, which it currently
doesn't (as you have described). In case of external dependencies which
the CTK superbuild resolved, you would typically want to install them as
well.
I am currently working on exactly this feature (we would like to do a
"make install" for CTK in MITK as well), see
https://github.com/commontk/CTK/issues/406
https://github.com/commontk/CTK/pull/466
Best,
Sascha
On 01/25/2015 12:21 PM, Miklos Espak wrote:
> Hi,
>
> we build CTK as an external project of our application. Instead of
> picking up the CTK headers and libraries from the build folder, we
> would like to install CTK and pick up them from the install directory.
> (The VS compiler cl.exe crashes because the accumulated list of
> include library paths causes an overflow. So we want to shorten the
> path list.)
>
> However, the ExternalProject_Add(CTK ...) call does not install the
> project correctly. It calls 'make install' from the CTK superbuild
> directory, not the CTK-build directory.
>
> Is it possible to change the working directory of the cmake ep
> install? (I'm afraid not, according to the docs.)
>
> Or, would it be possible to make the install work from the superbuild
> level?
>
> Cheers,
> Miklos
>
More information about the Ctk-developers
mailing list