Jump to content

OMK: Difference between revisions

From HW wiki
m Reverted edits by IdsNos (Talk); changed back to last version by Sojka
 
Line 32: Line 32:
* [http://rtime.felk.cvut.cz/darcs/darcsweb.cgi?r=omk Darcs repository for OMK development]
* [http://rtime.felk.cvut.cz/darcs/darcsweb.cgi?r=omk Darcs repository for OMK development]
* [http://ocera.cvs.sourceforge.net/*checkout*/ocera/ocera/components/comm/can/README.makerules Makefile Rules README File]
* [http://ocera.cvs.sourceforge.net/*checkout*/ocera/ocera/components/comm/can/README.makerules Makefile Rules README File]
* [http://rtime.felk.cvut.cz/hw/index.php/H8300-boot#Using_KDevelop_for_development Using KDevelop with OMK for embedded targets]

Revision as of 07:11, 16 October 2007

OMK is an acronym for Ocera Make System.

Introduction

TODO

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
INCLUDES = -I .

OMK System Development and External Resources