-
Notifications
You must be signed in to change notification settings - Fork 3k
Add include search path when preprocessing assembly files for uvision and make_armc5 exports #6356
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
Conversation
When exporting a mbed project to make_armc5, the include options (-I) of the ASM flags are not pointing to the good folder. It should be pointing to the root mbed-os folder and not the one in BUILD. This issue was found in the pull request ARMmbed#6168. Signed-off-by: Hugues de Valon <[email protected]>
When exporting to a uvision project, the include flags are not put in the assembly compilation line. When assembling the files containing includes, the search path will then fail. This patch adds the include paths to the Assembly sequence, as it is done for compilation. This issue was found in the pull request ARMmbed#6168. Signed-off-by: Hugues de Valon <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. Thanks!
/morph build |
Build : FAILUREBuild number : 1448 |
There was a license server failure, we are investigating and restart CI |
/morph build |
Build : SUCCESSBuild number : 1460 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 1101 |
Test : FAILUREBuild number : 1228 |
CI issue: Machine timeout? @0xc0170 Might need to restart this test. |
/morph test |
Test : FAILUREBuild number : 1244 |
The
Is that related with the CI issue? |
oops just seens #6340 nevermind 😨 |
/morph test |
Test : SUCCESSBuild number : 1260 |
Without that fix, the generated
uvision
andmake_armc5
exports would not include the different project folders in the search path of the assembly command line. It forces the user of using#include
with relative path.These issues were discovered while doing the export test if the pull request #6168