-
Notifications
You must be signed in to change notification settings - Fork 3k
Remove unnecessary absolute paths from IAR and ARM compilers #3414
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
Remove unnecessary absolute paths from IAR and ARM compilers #3414
Conversation
This fixes an issue where the absolute path causes a file error if the compiler paths are configured incorrectly. It uses a relative path instead now (the files appears to be in the default search path).
/morph export-build |
/morph test |
@mbed-bot: TEST HOST_OSES=ALL |
|
||
c_flags_cmd.extend([ | ||
"--thumb", "--dlib_config", "DLib_Config_Full.h" | ||
]) |
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.
👍
Result: FAILUREYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 50 Exporter Build failed! |
Failure should be fixed by #3416 |
[Build 1159] |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
LGTM |
#3416 is now merged, rerunning exporter tests now. /morph export-build |
retest uvisor |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 61 All exports and builds passed! |
Description
Both the ARM and IAR compilers use absolute paths to explicitly include their standard libraries. It seems that for both of these compilers, these paths are already in their default search paths, so using an absolute path is not necessary. This fixes an issue when exporting to make and the paths are incorrectly configured. This should now work out-of-the box.
Status
READY
Migrations
If this PR changes any APIs or behaviors, give a short description of what API users should do when this PR is merged.
NO
Todos
Notes
Requesting @theotherjimmy and @screamerbg to review this since it modifies the toolchains