eCosTM Reference Manual
Prev | Chapter 16. Package: Infrastructure | Next

# Component: Startup options

#### Macro name

CYGPKG_INFRA_STARTUP

#### Type

Dummy

#### Description

Some packages require a startup routine to be called. This can be carried out by application code, by supplying a routine called cyg_package_start() which calls the appropriate package startup routine(s). Alternatively, this routine can be constructed automatically and configured to call the startup routines of your choice.

## Option: Start ISO C library

#### Macro name

CYGSEM_START_ISO_C_COMPATIBILITY

#### Type

Boolean

#### Description

Generate a call to initialize the ISO C library (libc) within the system version of cyg_package_start(). This enables compatibility with ISO C, in particular in eCos it creates a thread that invokes the function main() which the user must supply. It does this by invoking the function cyg_iso_c_start(). If this is disabled, and you want to use the C library, you call cyg_iso_c_start() from your own cyg_package_start() or cyg_userstart().

## Option: Start uITRON subsystem

#### Macro name

CYGSEM_START_UITRON_COMPATIBILITY

#### Type

Boolean

#### Description

Generate a call to initialize the uITRON compatibility subsystem within the system version of cyg_package_start(). This enables compatibility with uITRON. You must configure uITRON with the correct tasks before starting the uItron subsystem. If this is disabled, and you want to use uITRON, you must call cyg_uitron_start() from your own cyg_package_start() or cyg_userstart().

Prev | Home | Next
Component: Asserts & Tracing | Up | Option: Smaller slower memcpy()