The xCDL Configuration Mechanism - DEPRECATED

Page date Sun Nov 13 22:41:03 2011 .

Improve this page

Overview

Scope

The xCDL mechanism was designed for the µOS++ SE, but should be general enough to be used for other C/C++ embedded frameworks too.

Goals

The first goal of the configuration mechanism is to help the build mechanism compile only the desired sources. In other words, to define the dependencies between various source files, so that when a certain platform is selected, all needed files are present. Even more, unused source files should not be compiled at all.

The second goal is to automatically generate header files, with various configuration definitions, like preprocessor defines, type definitions, etc.

Credits

The xCDL mechanism is inspired from the eCos CDL mechanism. For details please see:

• The eCos Component Writer’s Guide by Bart Veer and John Dallaway, and
• Embedded software development with eCos by Anthony J. Massa.

The XML format used to store the configuration data is the .plist, the Apple property list. For details please see:

• Introduction to Property Lists
• Apple’s Property List Document Type Definition

Misc:

• Software Build Systems: Principles and Experience by Peter Smith

Package organisation

The xCDL language

The build process

Monolithic vs component based builds.

The xCDL reference

• Tweet