-
Notifications
You must be signed in to change notification settings - Fork 2k
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
makefiles/cflags.inc.mk: don't include absolute path in __FILE__ macro #18913
Conversation
This requires at least GCC 8
I use on my old debian
Is that version of the compiler no longer supported by RIOT? |
Arg, Debian stable ships GCC 8 and the previous Ubuntu LTS GCC 9 so there is a temptation to say yes. But then again we should just properly detect the compiler version (so we don't penalize users who have a recent For now, just add
if you can't update your system. |
Probably adding some I think this is a good time (and reason) to system update. |
Can you try #18935 |
PR #18935 works with my old Thanks for this PR! |
This makes |
Contribution description
__FILE__
will resolve to the absolute path of the file.This adds a lot of noise (and ROM size) when debugging with tracer macros.
Luckily, starting with GCC 8 we can drop the common
$(RIOTBASE)
prefix, this makes for much nicer output.Testing procedure
Used in e.g. #18795
Issues/PRs references