-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement different levels of "make clean" #38
Comments
@jmalloc FYI |
I've going to go ahead and at least remove |
Spoke to soon, easier said than done, etc - https://github.com/make-files/lib-core/blame/v1/include/common.mk#L99 |
I guess we just add |
Could work well in combo with a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In previous implementations of the makefiles, we used to have
make clean
andmake clean-all
. A similar concept might be useful here.Two things stand out as being potential candidates to not remove under the standard
make clean
target:node_modules
/vendor
directories).makefiles
directory itselfImplementing this might solve #36, which we currently think is caused by the
.makefiles
directory being removed before some of the double-colonclean::
targets run.The question is: what to call these different targets, and what should be cleaned by each?
The text was updated successfully, but these errors were encountered: