-
Notifications
You must be signed in to change notification settings - Fork 3k
Tools: Restrict toolchains reported by mbed compile -S to official ones #8249
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
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.
Isn't this available anywhere as a list (similar to other like allowed_features, etc): SUPPORTED_TOOLCHAINS
?I assume we check the validity for supported toolchains somwhere
tools/build_api.py
Outdated
unique_supported_toolchains.append(toolchain) | ||
|
||
return unique_supported_toolchains | ||
return ["ARM", "uARM", "GCC_ARM", "IAR"] |
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.
To avoid creating a disconnect between the toolchain implementation, can we reference the keys present here instead:
mbed-os/tools/toolchains/__init__.py
Line 1112 in 1eab072
TOOLCHAIN_CLASSES = { |
I realize ARM6 is in that list though. So that would mean just removing it from the list here by name, or adding a "supported" variable (or something similar) to the toolchain class and then filter on that here.
Side note, there are quite a few targets in |
I would think it should be fine. Not even sure what GCC_CR is. @ARMmbed/mbed-os-test Thoughts? |
|
Not valid anymore, can be removed. |
@bridadan review please. |
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.
OFFICILLY_SUPPORTED is misspelled :)
Also, can we just say supported
or released
? We don't currently have a distinction between official/unofficial right?
tools/toolchains/__init__.py
Outdated
@@ -48,6 +48,8 @@ | |||
CPU_COEF = 1 | |||
|
|||
class mbedToolchain: | |||
OFFICILLY_SUPPORTED = False |
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.
This is the mispelling
### Description The `mbed compile -S` command is suposed to indicate what targets support what toolchains. The command was printing out things that don't make sense, like `GCC_CR` and things that make sense, but are not offiially supported yet, like `ARMC6`. This PR fixes all of that. ### Pull request type [x] Fix [ ] Refactor [ ] Target update [ ] Functionality change [ ] Breaking change
5d2df3d
to
ec72ce7
Compare
@bridadan Typo corrected. @theotherjimmy Thoughts on doing |
@bridadan I think the idea is that in the past, there's been confusion about compilers being enabled vs supported in the tools. The thought goes, being a bit more verbose about this helps makes this a bit clearer, and can help contextualize questions if/when they come up. |
Yeah fair point, though I would think "enabled" would mean it's in the tools (an implementation exists) and "supported" would mean the flag is set. But if this helps clarify it more then I don't feel that strongly about it 😄 |
/morph build |
Build : SUCCESSBuild number : 3409 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 3037 |
Test : SUCCESSBuild number : 3207 |
Description
The
mbed compile -S
command is suposed to indicate what targetssupport what toolchains. The command was printing out things that
don't make sense, like
GCC_CR
and things that make sense, but arenot offiially supported yet, like
ARMC6
. This PR fixes all of that.Pull request type