Make build process compatible with yocto #42
Closed
Conversation
This file contains 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
|
Tested and works. |
|
Is there any reason for this not to be merged ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It's currently not possible to manipulate easily internal Makefile variables like TOOLCHAIN, CC, AR, etc.
By adding simple modifications, it becomes possible to more easily integrate the project into build tool systems like Yocto.
The "" around ${CC}, ${AR} and ${LD} are needed in case of the CC passed to makefile is composed of multiple arguments. For example, in Yocto the value of CC is something like:
arm-poky-linux-gnueabi-gcc -march=armv7-a -marm -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a5 --sysroot=/opt/poky/2.5.2/sysroots/cortexa5hf-neon-loros-linux-gnueabiIt doesn't modify the default behavior but allows a lot more flexibility.