Skip to content

Using Mbed Studio's ARMC6 with Mbed CLI #1028

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 5 commits into from
Mar 22, 2019

Conversation

bridadan
Copy link
Contributor

This is the accompanying docs changes informing users on how to take advantage of the free Arm Compiler 6 bundled with Mbed Studio when building with Mbed CLI.

This is the corresponding OS tools change that will print a link to this encouraging users to upgrade to Arm Compiler 6: ARMmbed/mbed-os#10193

Reviewer notes/requests

For Mbed Studio folks: want y'all to be aware of what we're telling our users. I realize the compiler may move around in future releases. Please keep me posted and I can update this doc to match what you release, thanks!

For docs team: do the fine work y'all always do 👍

For everyone else: general review and to keep you in the loop

FYI @iriark01 @AnotherButler @bulislaw @SenRamakri @thegecko @arekzaluski

^ Lots of people but this is pretty wide reaching, thanks for taking the time to review this!

##### Using Arm Compiler 6 from Mbed Studio
Mbed Studio comes with a free version of Arm Compiler 6 when it's used with Mbed OS. It requires configuring the `ARMC6_PATH` as well as setting an environment variable to manage the license.

For Mbed Studio version 0.4.0, the Arm Compiler 6 executable is located in `./tools/ac6/bin`. This path is relative to the installation directory of Mbed Studio. On Windows for example, the default path is `C:\MbedStudio\tools\ac6\bin`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They have a new release next week - 0.5

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good to know, hopefully they can comment if I need to update this.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove this if you accept the suggestion above

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bridadan Irit is correct. Version 0.5 of Mbed Studio is planned soon. Ideally, you should not add path in docs. We are also moving the location of tools. It is no longer going to be inside of installation path.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Arek also said it's going to be different locations for different platforms.

This is starting to look like the docs maintenance effort is going to be very high.


For Mbed Studio version 0.4.0, the Arm Compiler 6 executable is located in `./tools/ac6/bin`. This path is relative to the installation directory of Mbed Studio. On Windows for example, the default path is `C:\MbedStudio\tools\ac6\bin`.

You must also set the environment variable `ARMLMD_LICENSE_FILE` to the path of Mbed Studio's Arm Compiler 6 license. For Mbed Studio version 0.4.0, the license is located at `./tools/ac6-license.dat`. This path is relative to the installation directory of Mbed Studio. On Windows for example, the default path is `C:\MbedStudio\tools\ac6-license.dat`. Note that this environment variable is not managed by Mbed CLI, so you must set it appropriately in your environment.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again - they're releasing 0.5 to match 5.12; need to make sure which versions this is correct for

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above. That is part of the reason why I put the version number in this change.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove this if you accept the suggestion above.

@iriark01
Copy link
Contributor

@arekzaluski can you answer some questions about 0.4/0.5?

@iriark01
Copy link
Contributor

Merging; will then update links that came from PR 1024

@iriark01 iriark01 merged commit 1a744b7 into ARMmbed:development Mar 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants