`Make clean` does not remove compiled custom ops
See original GitHub issueIs it better to move all of them to the build
directory instead of inline with the source code?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
'make clean' removes object files but not the entire build dir #52
I've just noticed that 'make clean' doesn't remove the compiled objects but instead removes the executable dir. It is 'make distclean' that ...
Read more >Makefile doesn't clean object files - Stack Overflow
You should not normally need or want to "clean object files". The whole point of using Make, is that you don't clean up...
Read more >Way to "really clean" a project - Google Groups
Sometimes I want to reset a project by removing *all* generated files. The sbt "clean" command goes part of the way but only...
Read more >How to git clean untracked files example - TheServerSide.com
Developers can use the git clean command to delete untracked files in a working tree and remove what they don't need from a...
Read more >GNU make
In this chapter, we will discuss a simple makefile that describes how to compile and link a text editor which consists of eight...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It was to be less specific yes!
But if you’re thinking for future operations
find
makes sense too!