3 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	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	4ffca4c3b8	Introduced web browser as new example using ctk fullscreen mode.	2007-12-15 22:05:34 +00:00