Skip to content

Commit 9a391dd

Browse files
author
Amanda Butler
authored
Rearrange content in export_to_third_party.md
Flip order to match that of the compiling section.
1 parent a67e187 commit 9a391dd

File tree

1 file changed

+10
-8
lines changed

1 file changed

+10
-8
lines changed

docs/tools/toolchains/export_to_third_party.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,14 @@ If you'd like to develop on Arm Mbed OS with a third party tool, or migrate to o
2525

2626
This may be useful to launch a debug session with your favorite tool while using Arm Mbed CLI for development, or creating examples or projects you work on within your tool of choice.
2727

28+
### Exporting from the Arm Mbed Online Compiler
29+
30+
The Arm Mbed Online Compiler has a built-in export mechanism that supports the same development environments as Mbed CLI. When you right click on a project you want to export and click **Export Program...**, the **Export Program** window opens. You can select your board and development environment.
31+
32+
<span class="images">![](https://s3-us-west-2.amazonaws.com/mbed-os-docs-images/export_menu.png)<span>Triggering an export</span></span>
33+
34+
The export process generates a ZIP archive with a project file matching your selected development environment. Follow your toolchain's import or project creation process to begin working there.
35+
2836
### Exporting from Arm Mbed CLI
2937

3038
[Mbed CLI](developing-arm-mbed-cli.html) currently supports [exporting](exporting.html#exporting-from-arm-mbed-cli) to all of the development environments mentioned above by using the `export` command.
@@ -38,6 +46,7 @@ You can open this project file with uVision5.
3846

3947
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](build-profiles.html). For example, this means that compiling within UVision 5 after this export:
4048

49+
```
4150
$ mbed export -i uvision5 -m K64F
4251
4352
will have the same flags as if you had compiled with:
@@ -47,14 +56,7 @@ will have the same flags as if you had compiled with:
4756
For a complete list of supported export toolchains, you can run:
4857
4958
$ mbed export -h
50-
51-
### Exporting from the Arm Mbed Online Compiler
52-
53-
The Arm Mbed Online Compiler has a built-in export mechanism that supports the same development environments as Mbed CLI. When you right click on a project you want to export and click **Export Program...**, the **Export Program** window opens. You can select your board and development environment.
54-
55-
<span class="images">![](https://s3-us-west-2.amazonaws.com/mbed-os-docs-images/export_menu.png)<span>Triggering an export</span></span>
56-
57-
The export process generates a ZIP archive with a project file matching your selected development environment. Follow your toolchain's import or project creation process to begin working there.
59+
```
5860

5961
### Before you export
6062

0 commit comments

Comments
 (0)