osd-contiki

deac/osd-contiki

Fork 0

Commit graph

Author	SHA1	Message	Date
Oliver Schmidt	4af9f534cc	Added the Telnet server to the examples supported by cc65.	2011-05-21 23:24:55 +02:00
oliverschmidt	6cbf46eeda	Removed 6502-specific files as this example doesn't build on any platform cleanly anyway.	2010-04-06 10:21:34 +00:00
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

Author

SHA1

Message

Date

Oliver Schmidt

4af9f534cc

Added the Telnet server to the examples supported by cc65.

2011-05-21 23:24:55 +02:00

oliverschmidt

6cbf46eeda

Removed 6502-specific files as this example doesn't build on any platform cleanly anyway.

2010-04-06 10:21:34 +00:00

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

3 commits