-
Notifications
You must be signed in to change notification settings - Fork 2k
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
oonf_api requires undocumented define #2772
Comments
Thanks to @mfrey for detecting this. |
Seems reasonable to me. @benpicco, since you're the author of this patch, can you tell us if you had any other intentions we're overlooking here? |
I think the intention was to have this always defined by a core RIOT Makefile, but that never got merged. I wanted to compile the same source code for RIOT and for Linux, so I needed a way to identify the platform - maybe something like this has been added by now? Otherwise it can't hurt to add such define to |
I'm not sure if we need this. Is it really a use case to build a thirdparty library inside RIOT (i.e. in |
Well it's possible that one day such patches could be merged upstream, then they mustn't break the build for non-RIOT targets. |
Ok, makes sense. Let's close this as soon as #2805 is merged. |
Will keep an eye on it. |
Building an application (e.g. https://github.com/Lotterleben/RIOT-AODVv2/tree/master/aodvv2_demo) with
oonf_api
fails with an error likeif one does not define the macro
RIOT
(which is done by the given example in the application Makefile byexport CFLAGS += -DRIOT
I think this define is useless, because it's only used in a RIOT specific patch (https://github.com/RIOT-OS/RIOT/blob/master/pkg/oonf_api/0001-add-RIOT-support.patch#L87) that can live without this ifdeff since the package inside RIOT will always be built for RIOT.
If there's still a reason for this define, it should be either documented somewhere and get a better name.
The text was updated successfully, but these errors were encountered: