Home  Contents

Project Properties

Development Core4 Manager

PROPERTIES

Project properties

Project Tab

The Targets field chooses which controller models you want the software to be built. This is a comma separated list of names. Available controller models are V4r3 and V4.5p1.

The SDK box selects a version of the Core4 SDK. The SDK contains the operating system and all other base files needed to build a working firmware. Core4Manager presets this to the latest SDK that is installed.

Note that whenever you install a new SDK version, projects will not automatically switch to it. To make use of a newly installed SDK, you need to pick the SDK explicitly in the project properties.

Lua properties

Lua Tab

Use preprocessor: All source files will be passed through the Core4 Lua preprocessor. This tool uses the same syntax as the well known C preprocessor. For example, it allows #define statements and conditional compilation using #if/#endif.

Remove comments: The preprocessor is asked to remove all comments.

Simplify whitespace: The preprocessor will remove all unnecessary whitespace and indentation. It will not remove empty lines.

Compile to bytecode: The source files will be compiled to Lua bytecode. Bytecode files load faster on the target and hide the source code.

Strip debugging symbols: The bytecode will not contain any information about source file names and source code line numbers. Whenever Lua needs to print an error message at runtime, it cannot tell you where the error happened.

Startup file: The name of the file that is run when the system starts. It is not recommended to change this.

Enter interactive mode after startup file terminates: When the main startup file terminates, the Lua interpreter will drop to a commandline on the debug serial port. While this may be helpful during development, make sure to not enable this on production systems. If this box is left unchecked, the startup file is restarted whenever it terminates.

Extra includes: Enter directories where the preprocessor should look for include files. One path per line. All paths are relative to the project directory. Since include files are not needed on the target, they should not be placed inside the root tree.