-
Notifications
You must be signed in to change notification settings - Fork 3k
Export: Support Make + ArmC6 + v8m #7559
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
@deepikabhavnani @cmonr Could one of you verify that this works on windows? |
@theotherjimmy - I tried the commit for v8 devices and it fails with error
|
Thanks. We'll talk offline about how to resolve this. |
e7bc5d7
to
c3da22d
Compare
@deepikabhavnani and I found out that a call to @deepikabhavnani Could you test this PR again when you get the chance? |
c2d00d5
to
881803c
Compare
Failing at linking step now:
|
@deepikabhavnani Can you run |
@theotherjimmy - yes i can run |
@deepikabhavnani Then it's probably fixed by #7583 |
This reverts commit a242799.
OSs don't agree on what the quote chars mean
780352b
to
58180db
Compare
Still same error on windows system
Error on linux
Config setting in linux echo $PATH which armclang which armasm |
@theotherjimmy Also, |
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.
Verified works for linux. Know issue for windows (command length exceeds 32K during linking)
/morph build |
Build : SUCCESSBuild number : 2770 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 2400 |
Test : FAILUREBuild number : 2498 |
/morph test |
@deepikabhavnani To my knowledge, we don't capture that in the docs. |
Test : SUCCESSBuild number : 2504 |
Export: Support Make + ArmC6 + v8m
Description
There were a few issues preventing v8m support for
make_armc6
:* a -D flag with
(...)
in it* the wrong scatterfile was used, making use of
armcc
inthe preprocessing step
This PR fixes both of these issues.
Pull request type