Mistake on this page?
Report an issue in GitHub or email us

About the exporters

Note: Note that exporters to export your code to various third party tools and IDEs are no longer supported. See this blog post for more details.

Use the Arm Mbed exporters to export your code to various third party tools and IDEs. Each exporter implements a generate function that produces an IDE specific project file. Exporters benefit from Mbed build tools. However, instead of using your source and config data to create an executable, we use that information to populate an IDE project file that will be configured to build, flash and debug your code.

Arm Mbed CLI command

usage: mbed export [-h] [-i IDE] [-m TARGET] [--source SOURCE] [-c] [-S] [-v]

Generate IDE project files for the current program.

optional arguments:
  -h, --help            show this help message and exit
  -i IDE, --ide IDE     IDE to create project files for. Example: UVISION4,
                        UVISION5, GCC_ARM, GNUARMECLIPSE, IAR, COIDE
  -m TARGET, --target TARGET
                        Export for target MCU. Example: K64F, NUCLEO_F401RE,
  --source SOURCE       Source directory. Default: . (current dir)
  -c, --clean           Clean the build directory before compiling
  -S, --supported       Shows supported matrix of targets and toolchains
  -v, --verbose         Verbose diagnostic output
  -vv, --very_verbose   Very verbose diagnostic output
Important Information for this Arm website

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies. If you are not happy with the use of these cookies, please review our Cookie Policy to learn how they can be disabled. By disabling cookies, some features of the site will not work.