-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Question: Split Makefile #878
Comments
true, it's pretty complex. Crossplane folks have a standalone repo that they include as a git submodule - https://github.com/upbound/build But we are more a mono-repo project so not sure if it's not an overkill for us. So sub directories could work. I'd rather put all the makefile stuff into 1 directory rather than splitting them to There is also that |
Basically, the reason for moving Makefiles under individual folders was so that we could see only things related to tests in Although the idea of leaving everything in one folder is even better, especially more convenient for maintenance. So I'm in favor of leaving everything in Perhaps we can keep the master Makefile in root - containing |
let's NOT do it until it's really necessary. |
I can split makefile into multiple files using
include
keyword.This way the split Makefile will still behave as one monolithic Makefile (the declared variable is visible from each Makefile, If I press
tab
in the commandline the autocomplete will work as expected).Makefile is quite robust, do you think it makes sense to split it?
Example:
The text was updated successfully, but these errors were encountered: