Skip to content

Expand on use of debug profile in the exporters #151

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
Apr 27, 2017

Conversation

theotherjimmy
Copy link
Contributor

@@ -36,6 +36,14 @@ For example, to export to uVision5 with the K64F target run:
A `*.uvproj` file is created in the root folder of the project.
You can open this project file with uVision5.

When exporting from mbed CLI, you will get a project that compiles with the debug profile. More information on the debug profile may be found in the [build profiles documentation](build_profiles.md#debug-profile). For example, this means that compiling within UVision 5 after this export:

Copy link
Contributor

Choose a reason for hiding this comment

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

I recommend changing the first two sentences to the following for active voice:

"When you export from mbed CLI, you create a project that compiles with the debug profile. You can find more information on the debug profile in the build profiles documentation."

@theotherjimmy theotherjimmy force-pushed the expand-general-export branch from 22f269d to e22ea9d Compare April 26, 2017 19:33
@theotherjimmy
Copy link
Contributor Author

Thanks for the review. Updated.

Fixed my typo
@AnotherButler AnotherButler merged commit 2520a7e into ARMmbed:5.4 Apr 27, 2017
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.

2 participants