native/make: Don't use INCLUDES for building any native at all.#804
Merged
miri64 merged 1 commit intoRIOT-OS:masterfrom Mar 3, 2014
Merged
Conversation
native modules will never need the dynamic INCLUDES, so we define our own NATIVEINCLUDES. Due to the current make structure, the only way to not use INCLUDES is to redefine the build rules.
This was referenced Feb 28, 2014
Member
|
Works for me. ACK. |
miri64
added a commit
that referenced
this pull request
Mar 3, 2014
native/make: Don't use INCLUDES for building any native at all.
12 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Native modules will never need the dynamic INCLUDES, so we define our
own NATIVEINCLUDES. Due to the current make structure, the only way to
not use INCLUDES is to redefine the build rules.
This fixes #793 and all future conflicts for the current INCLUDEs scheme.