Skip to content

Allow target attribute overrides in app config and pick toolchain with default_toolchain #4387

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

Merged
merged 2 commits into from
Jun 2, 2017

Conversation

theotherjimmy
Copy link
Contributor

@theotherjimmy theotherjimmy commented May 24, 2017

Description

The two commits in this PR do independent things:

First

We currently do not allow a user to override noncumulative attributes in the app
config. Attempting to override target.core, target.default_lib or
target.default_toolchain will error out with "Atempted to override undefined
parameter".

Instead, lets allow user to do this.

Second

This commit delays evaluation of the build profiles until after the app config has had a chance to override things.

TODO

  • /morph test
  • Write documentation for the first commit and submit the PR to the handbook

@theotherjimmy
Copy link
Contributor Author

Alternative implementation of #4371

@theotherjimmy
Copy link
Contributor Author

Wow that failed fast.

@theotherjimmy theotherjimmy force-pushed the override-target-attrs branch from 0a15635 to e0612f0 Compare May 24, 2017 18:55
@0xc0170
Copy link
Contributor

0xc0170 commented May 25, 2017

Travis still fails AttributeError: 'Target' object has no attribute 'default_toolchain'

@theotherjimmy
Copy link
Contributor Author

That travis log is not for the current commit. It's for 862fddc, the current commit is e0612f0.

@0xc0170
Copy link
Contributor

0xc0170 commented May 26, 2017

That travis log is not for the current commit. It's for 862fddc, the current commit is e0612f0.

Thats correct. I restarted it but does not pick up the latest one. Can you please rebase/amend to restart it?

@theotherjimmy
Copy link
Contributor Author

Trying to retrigger travis...

@theotherjimmy theotherjimmy force-pushed the override-target-attrs branch 2 times, most recently from 4abe922 to 8ff08d1 Compare May 30, 2017 20:05
@theotherjimmy
Copy link
Contributor Author

Ah, I forgot to push. That was the problem.

@theotherjimmy
Copy link
Contributor Author

Documentation submitted.

@theotherjimmy theotherjimmy force-pushed the override-target-attrs branch from 8ff08d1 to 18cb953 Compare May 30, 2017 21:27
@theotherjimmy
Copy link
Contributor Author

@sg- ARM should now only be ARM, and uARM only uARM.

@adbridge
Copy link
Contributor

@theotherjimmy looks like this also needs a rebase now

@theotherjimmy
Copy link
Contributor Author

Yes it does.

@theotherjimmy theotherjimmy force-pushed the override-target-attrs branch from 18cb953 to e001a3a Compare May 31, 2017 14:24
@theotherjimmy
Copy link
Contributor Author

retest uvisor

@theotherjimmy
Copy link
Contributor Author

/morph test

@mbed-bot
Copy link

mbed-bot commented Jun 1, 2017

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 387

Build Prep failed!

@sg- sg- closed this Jun 1, 2017
@sg- sg- reopened this Jun 1, 2017
@sg- sg- added needs: work and removed needs: CI labels Jun 1, 2017
@sg- sg- removed the needs: work label Jun 1, 2017
@sg-
Copy link
Contributor

sg- commented Jun 1, 2017

/morph test

@mbed-bot
Copy link

mbed-bot commented Jun 1, 2017

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 391

Example Build failed!

@0xc0170
Copy link
Contributor

0xc0170 commented Jun 1, 2017

/morph test

@mbed-bot
Copy link

mbed-bot commented Jun 1, 2017

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 394

Example Build failed!

@0xc0170
Copy link
Contributor

0xc0170 commented Jun 1, 2017

@theotherjimmy Fails for 2 targets, all toolchains, with the following message

Compiling mbed-os-example-bootloader for K64F, ARM
[ERROR] list indices must be integers, not str

It's related to bootloader example. I firstly thought it was CI failure, but no it is example build failure for those targets that support the bootloader

@theotherjimmy
Copy link
Contributor Author

I had an ordering wrong. shakes fist at sky darn you imperative paradigm!

@theotherjimmy theotherjimmy force-pushed the override-target-attrs branch from 9324eb8 to 4e3591b Compare June 1, 2017 16:16
@sg-
Copy link
Contributor

sg- commented Jun 1, 2017

/morph test

@sg- sg- added needs: CI and removed needs: work labels Jun 1, 2017
@studavekar
Copy link
Contributor

/morph test

@mbed-bot
Copy link

mbed-bot commented Jun 2, 2017

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 408

All builds and test passed!

@sg- sg- added needs: work and removed needs: CI labels Jun 2, 2017
@0xc0170 0xc0170 force-pushed the override-target-attrs branch from 4e3591b to 9277c6e Compare June 2, 2017 11:06
@0xc0170
Copy link
Contributor

0xc0170 commented Jun 2, 2017

/morph test

@mbed-bot
Copy link

mbed-bot commented Jun 2, 2017

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 419

All builds and test passed!

@theotherjimmy theotherjimmy merged commit 2886f0b into ARMmbed:master Jun 2, 2017
@theotherjimmy theotherjimmy deleted the override-target-attrs branch June 2, 2017 15:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants