Just answered this somewhere else, but hope this helps. Don't even know what platform you're on, but if you're not on windows, this may be transferrable if you're lucky.
On Win32 you can just delete the four files generated by btool (build.dep, config.h, inkscape_version.h and compile.lst) and the either delete or rename the inkscape directory, and then run btool again, and it will only recompile the changed modules and their deps. I don't think I would do that if I changed the devlibs in between, and I still do a clean build fairly often, but many fewer 1hr waits to test.
For more info, see http://wiki.inkscape.org/wiki/index.php/Win32Port - I've put in some more detail there.
Cheers,
Rygle
Maximilian Albert wrote:
Hi all,
I'm not sure if I already asked this some time ago (if so, please bear with me). Compiling and linking always takes a considerable amount of time and I regularly run into the need to test the effect of several small changes in quick succession. Is there a way to speed up compiling in any way, for example by deactivating certain things which have nothing to do with the code I'm interested in? Any options for ./configure (I already use --without-inkjar), any compile switches, #ifdefs I'm not aware of, anything?
Thanks, Max
P.S.: I do use ccache but I still hope that the building (in particular, the linking) time can be reduced by other means, too.
Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel