Skip to content
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

MAKE CLEAN needs cleaning up #793

Closed
IBNobody opened this issue Sep 29, 2016 · 3 comments
Closed

MAKE CLEAN needs cleaning up #793

IBNobody opened this issue Sep 29, 2016 · 3 comments

Comments

@IBNobody
Copy link
Contributor

I have a few issues with MAKE CLEAN.

First, there is no simple make clean recipe anymore for the general QMK.

C:\GitHub\qmk_firmware>make clean
make: *** No rule to make target 'clean'. Stop.
Makefile:474: *** commands commence before first target.  Stop.

Second, I know that make allkb-clean works, but there's an issue in that it is sloooow because it iterates on every keyboard/keymap.

Third, there isn't a make clean command variant that gets rid of the hex files. I understand why we would want to keep hex files, but we don't always want them hanging around.

@fredizzimo
Copy link
Contributor

Yes, it has been on my long todo list, but I would be happy if someone else could do it,

You should never actually need to run clean though. If you have to, then there are some bugs in the dependency checks that needs to be fixed. And that should be reported as separate issues.

@IBNobody
Copy link
Contributor Author

I can look into tackling 1 and 3 this weekend.

You are right. You never truly need to run make clean for individual projects. However, it is the only way I know of to regenerate any compiler warnings.

For all projects, though, I usually want to clean up the .build folder because I don't need them taking up space.

@drashna
Copy link
Member

drashna commented Mar 25, 2018

#2485 adds a "make clean" command. And simply deletes the entire .build folder, so its fast.

This handles #1 and #2. As for #3, `rm *.hex should fork for #3.

I'm closing this. If needed, reopen or open a new issue.

@drashna drashna closed this as completed Mar 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants