Sw4STM32 Class Reference

Add the containgin directory of mbed_config.h to include dirs

Headless build an Eclipse project.

The following steps are performed:
- a temporary workspace is created, 
- the project is imported,
- a clean build of all configurations is performed and 
- the temporary workspace is removed.

The build results are in the Debug & Release folders.

All executables (eclipse & toolchain) must be in the PATH.

The general method to start a headless Eclipse build is:

$ eclipse \
--launcher.suppressErrors \
-nosplash \
-application org.eclipse.cdt.managedbuilder.core.headlessbuild \
-data /path/to/workspace \
-import /path/to/project \
-cleanBuild "project[/configuration] | all"

Clean a previously exported project
This method is assumed to be executed at the same level as exporter
project files and project source code.
See uvision/__init__.py, iar/__init__.py, and makefile/__init__.py for
example implemenation.

Positional Arguments:
project_name - the name of the project to build; often required by
exporter's build command.

Returns nothing. May raise exceptions

With the project root as the only source folder known to CDT,
based on the list of source files, compute the folders to not
be included in the build.

The steps are:
- get the list of source folders, as dirname(source_file)
- compute the top folders (subfolders of the project folder)
- iterate all subfolders and add them to a tree, with all 
nodes markes as 'not used'
- iterate the source folders and mark them as 'used' in the
tree, including all intermediate nodes
- recurse the tree and collect all unused folders; descend
the hierarchy only for used nodes

Remove the './' or '.\\' prefix, if present.

Returns a dictionary of toolchain flags.
Keys of the dictionary are:
cxx_flags    - c++ flags
c_flags      - c flags
ld_flags     - linker flags
asm_flags    - assembler flags
common_flags - common options

The difference from the parent function is that it does not
add macro definitions, since they are passed separately.

Generates a project file from a template using jinja

Generate the project file location in an exported project

Generates a project file from a template using jinja

Generate the .project and .cproject files.

Convert fpu unit name into hardware name.

Returns a list of the directories where source files are contained

A helper getter function that we should probably eliminate

Group the source files by their encompassing directory
Positional Arguments:
sources - array of source locations

Returns a dictionary of {group name: list of source locations}

Query support for a particular target

NOTE: override this method if your exporter does not provide a static list of targets

Positional Arguments:
target_name - the name of the target.

From a source file, extract group name
Positional Arguments:
src - the src's location

CDT managed projects store lots of build options in separate
variables, with separate IDs in the .cproject file.
When the CDT build is started, all these options are brought
together to compose the compiler and linker command lines.

Here the process is reversed, from the compiler and linker
command lines, the options are identified and various flags are
set to control the template generation process.

Once identified, the options are removed from the command lines.

The options that were not identified are options that do not 
have CDT equivalents and will be passed in the 'Other options' 
categories.

Although this process does not have a very complicated logic,
given the large number of explicit configuration options
used by the GNU ARM Eclipse managed build plug-in, it is tedious...

Process System Workbench specific options.

System Workbench for STM32 has some compile options, which are not recognized by the GNUARMEclipse exporter.
Those are handled in this method.

Returns a dictionary of toolchain flags.
Keys of the dictionary are:
cxx_flags    - c++ flags
c_flags      - c flags
ld_flags     - linker flags
asm_flags    - assembler flags
common_flags - common options

The difference from the above is that it takes a parameter.