-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
min
and max
definitions in Arduino.h
cause compilation errors
#12
Comments
Interesting, thanks for the report. I'll look into this asap. |
@h2zero Please let me know if there are any tests or other things I should try. I'm convinced this is just a mistake on my end, since it seems to happen when using anything from For reference, here is the complete compilation log ( |
Looks like there is a redefinition of min and max in the "drivers" library. Is this a private lib? |
Yes it is, but I just did a quick |
Oh boy, I think I've found it: https://arduinojson.org/v6/error/macro-min-passed-3-arguments-but-takes-just-2/ Looks like |
Reordering does partially fix things, but still produces compilation errors from
It looks like this is related to an issue in an older version of Arduino-samd, which I know this repo is loosely based off of. Is the core up to date with the latest SAMD core? |
I have confirmed that the issue is indeed in the |
unordered_map
causes compilation errors.min
and max
definitions in Arduino.h
cause compilation errors
Awesome, any thoughts about a permanent solution? Not sure if they did anything in the samd core to deal with this. |
@h2zero It's unclear to me how exactly they fixed it in the samd core. Something to do with the underlying arduino-api. But here a permanent (albeit a bit sloppy) fix would just be to use the same
that the samd core uses for |
Any project which uses
std::unordered_map
fails to compile. The error message is extraordinarily long, but starts as:I hope this is just something I'm doing wrong. An identical project using the non-n-able core compiles without issue.
The text was updated successfully, but these errors were encountered: