You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/tools/toolchains/export_to_third_party.md
+10-8Lines changed: 10 additions & 8 deletions
Original file line number
Diff line number
Diff 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
25
25
26
26
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.
27
27
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
+
<spanclass="images"><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
+
28
36
### Exporting from Arm Mbed CLI
29
37
30
38
[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.
38
46
39
47
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:
40
48
49
+
```
41
50
$ mbed export -i uvision5 -m K64F
42
51
43
52
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:
47
56
For a complete list of supported export toolchains, you can run:
48
57
49
58
$ 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
-
<spanclass="images"><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.
0 commit comments