On Fri, Jul 8, 2011 at 3:39 AM, Sascha Zelzer
<[email protected]> wrote:
> Did you modify the MITK sources in some way?
>
> Are you trying to re-use an older build-tree by updating the MITK sources
> and building again? If so, you might want to try with a clean (empty) build
> tree again.
I though I was doing a completely fresh build, but apparently not.
After `git clean -fd && git reset --hard && rm -rf ../MITK-superbuild`
and a few hours of compiling things are working.
I'd like to be able to do fresh re-builds more often but since the
(super)build time is so long I'm often reluctant to do so. What's the
recommended best way to do a fresh rebuild in minimal time? Since CTK
development activity seems coupled with MITK development (i.e. the
MITK superbuild pulls the latest from CTK Git HEAD) I probably want to
always let that run. But for all the other components that simply
download and build a release tarball, would something like this work:
~/MITK-src
--> MITK source from Git HEAD
~/MITK-superbuild
--> Built using `ccmake ../MITK-src`
~/MITK-quickbuild
--> Built using `ccmake -DITK_DIR:PATH=../MITK-superbuild/ITK-build \
-DVTK_DIR:PATH=../MITK-superbuild/VTK-build \
-DGDCM_DIR:PATH=../MITK-superbuild/GDCM-build \
../MITK-src`
Or how do most MITK developers setup their builds?
Taylor
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
