Merge pull request #5666 from mharringADI/feature-cces-exporter

Add exporter for Analog Devices' CrossCore Embedded Studio

Author: cmonr

tools/export/__init__.py

@@ -30,7 +30,7 @@
 from ..targets import TARGET_NAMES
 from . import (lpcxpresso, ds5_5, iar, makefile, embitz, coide, kds, simplicity,
                atmelstudio, mcuxpresso, sw4stm32, e2studio, zip, cmsis, uvision,
-               cdt, vscode, gnuarmeclipse, qtcreator, cmake, nb)
+               cdt, vscode, gnuarmeclipse, qtcreator, cmake, nb, cces)
 
 EXPORTERS = {
     u'uvision5': uvision.Uvision,
@@ -60,7 +60,8 @@
     u'vscode_gcc_arm' : vscode.VSCodeGcc,
     u'vscode_iar' : vscode.VSCodeIAR,
     u'vscode_armc5' : vscode.VSCodeArmc5,
-    u'cmake_gcc_arm': cmake.GccArm
+    u'cmake_gcc_arm': cmake.GccArm,
+    u'cces' : cces.CCES
 }
 
 ERROR_MESSAGE_UNSUPPORTED_TOOLCHAIN = """

tools/export/cces/README.md.tmpl

@@ -0,0 +1,25 @@
+# Create and build CrossCore Embedded Studio projects
+CrossCore Embedded Studio (CCES) can generate and build IDE projects from the command line using .json input files.
+
+## Create a new project
+
+Run the following headless tools command to create your CrossCore Embedded Studio project using the .json file generated by the ARM mbed exporter:
+{% for operating_system, command in commands['create'].items() %}
+### {{ operating_system }}
+> {{ command }}
+
+{% endfor %}
+where "CCES_HOME" is an environment variable pointing to the root CCES installation directory and "WORKSPACE" is the path to the desired CCES workspace directory.
+
+Once the CrossCore Embedded Studio project is generated, you can import the project into the IDE for development and debugging.
+
+## Build a project
+Once created, you can use headless tools to build the project with the following command:
+{% for operating_system, command in commands['build'].items() %}
+### {{ operating_system }}
+> {{ command }}
+
+{% endfor %}
+where "CCES_HOME" is an environment variable pointing to the root CCES installation directory and "WORKSPACE" is the path to the desired CCES workspace directory.
+
+For more information on how to use CrossCore Embedded Studio and headless tools, please see the CrossCore Embedded Studio Help.