Commit Graph

6 Commits

Author SHA1 Message Date
oliverschmidt
1cab294517 The Contiki 2.x build system allows to define arbitrary macros for the C compiler preprocessor (in other word add -d<macro[=value]>'s to the C compiler command line) directly from the gnumake command line by setting the gnumake variable DEFINES to a comma-seperated list of macros (and optionally values) like this:
make TARGET=mytarget DEFINES=MYLOG, MYSIZE=100, MYTRACE

The build system does however _NOT_ take care to rebuild things if the DEFINES change so most likely a 'make clean' is advisable. To ease usage the DEFINES may be saved individually per target with the goal 'savedefines' similiar to savinf the target.

The 6502-based target leverage the DEFINES mechanism by introducing so-called 'high level config macros' which allow to configure Contiki per target AND per project.

Most of the time there's exactly one reasonable set of high level config macros for every combination of target and project. Therefore it makes sense to place them into CVS.
2008-05-26 09:28:28 +00:00
oliverschmidt
8248685dcf Not all targets support stdio. There I replaced stdio output with log output (and streamlined the source). 2008-05-26 09:12:22 +00:00
oliverschmidt
b2810f02e1 Many project Makefiles build just one Contiki binary. Up to now the name of this binary was only available to the 'all' goal as prerequisite. So it was possible to create a non-project-specific rule to i.e. load that binary into the target device.
Therefore I introduced the make variable CONTIKI_PROJECT. Now a typical project Makefile starts with:

CONTIKI_PROJECT = hello-world
all: $(CONTIKI_PROJECT)
2008-05-26 07:37:24 +00:00
oliverschmidt
f8bf3e1428 Fixed buffer overflow. 2007-08-10 10:33:28 +00:00
oliverschmidt
91710dd48f Minor adjustment to coding style. 2007-04-04 17:41:28 +00:00
oliverschmidt
f1d9702b68 Added an example application to show the usage of the Contiki Multi-threading library. 2007-04-03 20:13:27 +00:00