Skip to end of metadata
Go to start of metadata

LieberLieber Embedded Engineer comes with a set of options which influence the UI and code generation.
These options can be set for each View of a model, and are stored in the model.

Version 2.6 Update

Model Settings update:

  • Settings can now be stored on each package level
  • Only changed settings will be stored as Tagged Values
  • Settings will be inherited from the parent packages
  • Settings from parent packages can be overwritten in subsequent packages
  • JSON-Formated settings can be read


To open the settings for your model, go to Extensions → LieberLieber Embedded Engineer 2.x → Model Settings...

The Treeview will now represent the structure of your current Package list and its inheritance structure.

Available Settings

SettingDescriptionDefault ValueVersion
Code Editor
Code Editor Save Strategy

Allows the user to choose what should happen if unsaved changes are present in the new code editor dialog.

DiscardChanges: Will discard any changes made without prompting the user.

AutoSaveChanges: Will save any changes made without prompting the user.

PromptUser: Will prompt the user to eather save or discard unsaved changes.

DiscardChanges3.0
Code Generation
Always Generate SignalsAlways update the signals enumeration before generating code?No2.0
Clang-Format Style OptionsOptions used by Embedded Engineer and Clang Format to format the output code

{
ColumnLimit: 0,
BasedOnStyle: LLVM,
BreakBeforeBraces: Allman,
IndentWidth: 4,
UseTab: Never,
AccessModifierOffset: -4,
PointerAlignment: Left,
AllowShortFunctionsOnASingleLine: None,
AlignConsecutiveAssignments: false,
AlignTrailingComments: false,
BinPackParameters: false,
PenaltyReturnTypeOnItsOwnLine: 1000,
SortIncludes: false
}

2.1
Generate includes in .c fileGenerates includes in .c instead of .h fileNo2.0
Sync User CodePerform the User Code Synchronization and the comments required for this feature?Yes2.0
Code Generation - Advanced
Activity Code GenerationGenerate code for activities?True2.0
AnsiC class instantiation strategy

CreateInstanceAndFunction: The statically allocated instance and accessing function for the current class will be generated

CreateStaticInstance: The statically allocated instance for the current class will be generated

CreateNothing: Will skip the generation for the statically allocated instance and accessing function for the current class

CreateInstanceAndFunction2.6
Consider define scope

If set will take "private/public" scope of <define> Attributes into consideration during generation.

(private defines will be generated into the .c file)

No2.3
Generate Directories for PackagesWill generate a sub folder for each sub package of the current package.No2.1
Generate 'origin of code' comment

If set will generate a //User-supplied code: [UmlType] '[ElementName]', [ElementGuid] for every user-supplied code

(e.g.: OpaqueActions, Behaviors,...)

No2.3
Include Path DelimiterDelimiter to use for include path generation/2.1
MISRA Compliance EnabledGenerate redundant statements to maintain MISRA compliance?True2.0
Position of field commentsCustomize where to put the comments of a field (BeforeField, AfterField, AfterFieldIfSingleLine)AfterFieldIfSingleLine2.1
State Machine Code GenerationGenerate code for state machines?True2.0
Single Class instance modeIf Yes: Will omit generation of the "me/this" pointer in Class Operations and will access the statically allocated field instead.No2.6

Single State Machine instatnce mode

If Yes: Will omit generation of the "stm" pointer in State Machine Operations and will access the statically allocated struct field instead.No2.6
State Machine Code GenerationGenerate code for State Machines?True2.0
User Code storage fieldDefine if usercode will be stored in Initial Code or Behavior field of Enterprise ArchitectInitalCode2.1
Write comment before includeCustomize where to put the include commentFalse2.1
Traceability
Add Requirement CommentsAdd comments for linked requirements?Yes2.0
UML Debugger
Generate UML Debugger InformationGenerate debugging information to be used by the UML Debugger?Yes2.0
User Interface
Auto Close Progress WindowAutomatically close the progress window if no errors/warnings have been detected?No2.0
C++-Code Generation EnabledShow the entries for C++ Code Generation in the Embedded Engineer menus?Yes2.0
C-Code Generation EnabledShow the entries for C Code Generation in the Embedded Engineer menus?Yes2.0
Show "Generate Signals and Code"Show the entry "Generate Signals and Code"? Useful when activating the option Always Generate Signals.Yes2.0
  • No labels