OMK: Difference between revisions
No edit summary |
|||
| Line 11: | Line 11: | ||
==== Export of configuration to header files ==== | ==== Export of configuration to header files ==== | ||
; config_include_HEADERS : defines | ; config_include_HEADERS : defines the name of global header file, which will contains definitions of some symbols from config file (<tt>config.omk</tt>), whose value is '''y''' or '''m'''. | ||
; ''xxx''_DEFINES : controls which configuration variables should appear in header file ''xxx''.h | ; ''xxx''_DEFINES : controls which configuration variables should appear in header file ''xxx''.h | ||
| Line 18: | Line 18: | ||
config_DEFINES = CONFIG_HIGH_RES_TIMERS | config_DEFINES = CONFIG_HIGH_RES_TIMERS | ||
; LOCAL_CONFIG_H : specifies | ; LOCAL_CONFIG_H : specifies the name of header file, which is available to sources in current directory and which will contain all definitions of default_CONFIG in the current directory. | ||
Example: | Example: | ||
LOCAL_CONFIG_H = lincan_config.h | LOCAL_CONFIG_H = lincan_config.h | ||
Revision as of 12:45, 26 March 2006
OMK is an acronym for Ocera Make System.
Directives used in Makefile.omk files
Configuration Files
- default_CONFIG
- declares configuration variables and specifies their default values. Values can be y, n and m.
default_CONFIG = CONFIG_HIGH_RES_TIMERS=y DEBUG=n
Export of configuration to header files
- config_include_HEADERS
- defines the name of global header file, which will contains definitions of some symbols from config file (config.omk), whose value is y or m.
- xxx_DEFINES
- controls which configuration variables should appear in header file xxx.h
Example:
config_include_HEADERS = config.h config_DEFINES = CONFIG_HIGH_RES_TIMERS
- LOCAL_CONFIG_H
- specifies the name of header file, which is available to sources in current directory and which will contain all definitions of default_CONFIG in the current directory.
Example:
LOCAL_CONFIG_H = lincan_config.h