Revert "Using Mbed Studio's ARMC6 with Mbed CLI" #1029
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bulislaw
requested changes
Mar 22, 2019
|
Closing as agreed with Bartek |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reverts #1028
@bridadan I do not think that documenting the location of the tools that we are shipping with Mbed Studio is a good idea. They are designed to be isolated and to work only with Mbed Studio.
Mbed CLI should not reuse tools that we are shipping inside of Mbed Studio. The way that it should be done is for mebd CLI installers to ship its own ARMC6.
We also can't commit to the location of tools. In fact release 0.5 (next release) is going to change tools location. It is going to be specific on each of the platform supported by Mbed Studio.