All of the definition files have the same format. They're divided into sections. Each section type has a set of permitted content, which could be simple, numerical or text values, named items, or other sections (subsections).
A section always starts with a section name followed by a colon (':').
Sections that can have multiple content items always have curly braces around their content.
All sections are optional; they can be empty or omitted.
Sections can be in any order, multiple occurrences are permitted, and some sections have sub-sections.
A named item always begins with the item name followed by an equals sign ('=').
If a named item can have multiple content items, then it must have curly braces around its content.
Integers are required in some sections.
Numbers can be expressed in multiples of 1024 by adding the 'K' suffix.
Some sections contain text-based values. The format of these varies depending on the type of section.
It's possible to use environment variables inside of .sdef
, .adef
, and Component.cdef
files.
This works the same way as in shell scripts, by prefixing the environment variable name with a dollar sign ($):
If necessary, the variable name can also be enclosed in curly braces.
Some useful environment variables:
LEGATO_ROOT
= path to where the Legato framework sources are locatedLEGATO_TARGET
= build target (e.g., wp85, localhost)LEGATO_BUILD
= shorthand for $LEGATO_ROOT/build/$TARGET
LEGATO_SYSROOT
= path of the directory containing the target device's system filesTabs, spaces, new-lines, carriage-returns and comments act as token separators only, and are otherwise all ignored. Consequently, choice of indentation and spacing style is relatively unrestricted.
Comments can be included using
Copyright (C) Sierra Wireless Inc. Use of this work is subject to license.