Hi,

that's unusual. I may happen that the build sometimes still crawls through 
already built libraries but in that case it should just take milliseconds per 
library to check timestamps. 

A few ideas:

- It seems like you still called make from superbuild level. After your 
superbuild was successful, you should cd into the MITK-build subdirectory 
instead and call make from there. No need to stay at superbuild level which 
will look up each Git repository for all dependencies again for differences. 
This may take a long time in some network-related circumstances... I guess this 
is already your main issue.
- I suggest to do a multi-core build by specifying the -j parameter to make 
with the number of parallel build processes. This will speed up your build 
dramatically. As a rule of thumb, use <number of cores + 2> but never more than 
<number of GBs memory>, i.e.: "make -j 10" called from within the 
MITK-superbuild/MITK-build directory for an 8-core processor with at least 10GB 
RAM.
- Instead of make you can also use the Ninja Generator (apt-get install 
ninja-build). No need to specify any multi-core parameters with "ninja". It 
will be noticeably faster than "make" as it is not as verbose as make. However, 
you would need to do a fresh build, since you cannot pick up a "make" build.
- Advanced: You could even reduce build times of complete subsequent 
superbuilds to a few minutes by using tools like ccache, but for the beginning 
stick with pure make or ninja.

Best,

Stefan

_______________________________________
Von: Michael Joseph Barrow <mjbar...@stanford.edu>
Gesendet: Mittwoch, 6. Dezember 2023 06:23
An: mitk-users@lists.sourceforge.net
Betreff: [Extern] - [mitk-users] How to quickly compile a custom MITK extension 
module?

Hi, I have searched the mailing list but could not seem to find the best way to 
incrementally/quickly build an MITK module under development. I am using the 
example template here: https://github.com/MITK/MITK-ProjectTemplate and have 
verified it appears in the MITK GUI and works after setting MITK_EXTENSION_DIRS.


I have tried "make MITK-build", but this takes 35 minutes even after an initial 
superbuild and seems to run make for many (all?) un-touched MITK dependencies.

I am sure no one could easily develop code in this way, so what is the right 
way to only re-compile the plugin module on its own?


_______________________________________________
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to