keep compiled files between compiles, make distclean #788
Conversation
should speed up re-build process as only changed .o files are compiled again. Use make clean to start fresh --eg when strange errors occur.
Actually not sure about Travis - it does delete all files at init, right? But definitely fast for user builds. |
@breznak Travis has a fresh environment and fresh checkout of the repo for every job. Is that what you are asking? |
Ok, so travis would not gain any speed-advantage from this (unless we can copy object files from last build to build/temp ) . But developers (who rebuild often) definitely would. |
LGTM... @david-ragazzi ? |
What is LGTM?? hehe |
@breznak Wouldn't be better "make clean" instead of "make distclean"? |
Looks good to me. 👀 |
hummm Waiting for @breznak answer.. |
I thought the same, but no. clean is reserved target for make. see that it already does something. |
Btw, updated SHA, for the change to make sense. |
👍 |
LGTM, @rhyolight ! |
keep compiled files between compiles, make distclean
keep compiled files between compiles, make distclean
1/ new target make distclean
2/ keeping precompiled objects during compilations - makes consequent builds much faster, only changed objects are recompiled.
when numenta/nupic.core-legacy#65 is merged and SHA here updated to it, the difference should be visible!