-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Ignore "makefile", which can be used to customize the build #3372
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
Conversation
e.g., I put content in ports/portname/makefile like ``` BOARD=boardname DEBUG=1 include Makefile ``` so that when I `make` it picks up these flags automatically. This change means that these files won't be picked up by `git status` or removed by `git clean`.
|
will the Makefile still be Downloaded when cloned and updated when it is modified? |
|
The "Makefile" and the "makefile" are different files. |
|
However, behavior on systems which don't distinguish between "Makefile" and "makefile", like windows, may be a reason to not accept this PR. I can't easily check those systems. |
dhalbert
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
However, behavior on systems which don't distinguish between "Makefile" and "makefile", like windows, may be a reason to not accept this PR. I can't easily check those systems.
Both Windows and MacOS also have case-insensitive filesystems by default. I think those are showstoppers.
Alternatives:
- Add
-include makefile.localto the Makefiles, and put makefile.local in .gitignore. See https://stackoverflow.com/questions/3910054/makefile-conditional-include.
-
According to the documentation, GNU make "will look for the makefiles GNUmakefile, makefile, and Makefile, in that order." If you're always planning to use GNU make, you could add
GNUmakefileto .gitignore instead. -
Alias
maketo a script that checks for, say,makefile.local, and putmakefile.localin the.gitignore.
|
I like |
|
in my experience everything except the esp32s2 will build on a case-incensitive file system on a Mac. (anything using the arm toolchain) The espressif idf (xtensa toolchain) requires a case insensitive file system. |
|
It may only be necessary to have a case sensitive file system to build the xtesna toolchainn locally -- that is the only place I see it mentioned here -- |
|
FYI -- I just did a fresh clone of the CP repo to a default (case-insesntive) MacOS file system and I am able to build the esp32s2 files.. The only issue I aide was with the version of gdbgui installed -- has to revert it to 0.13.2.0 (that hs noting to do with the file systems) |
e.g., I put content in ports/portname/makefile like
so that when I
makeit picks up these flags automatically.This change means that these files won't be picked up by
git statusor removed bygit clean(unless -x is specified).