OK, that's fine. Do I need to define the dependencies at both places? In
the mitkFunctionAddExternalProject macros in the top-level cmake and in
CMakeExternals/<project>.cmake files? Or the first way is replacing the
second one so that one is not needed any more?
Cheers,
Miklos
On 24 June 2015 at 06:36, Sascha Zelzer <[email protected]> wrote:
> Hi,
>
> It looks like you found a bug. The ITK line shoud contain a "DEPENDS
> GDCM" but since GDCM is ON by default and nobody is switching it OFF, we
> didn't notice.
>
> Best,
> Sascha
>
> On 06/23/2015 08:06 PM, Miklos Espak wrote:
> > Hi,
> >
> > I am trying to mock the same build structure in our project that the
> > new MITK release does.
> >
> > What is the right way of defining project dependencies? The top level
> > cmakelists file has this:
> >
> > mitkFunctionAddExternalProject(NAME ITK ON NO_CACHE)
> >
> > Other EPs have a DEPENDS clause here.
> >
> > But the CMakeExternals/ITK.cmake defines a dependency on GDCM.
> >
> > Is it a problem? Which is the right place for declaring a dependency?
> >
> > Cheers,
> > Miklos
> >
>
>
------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
