Commit Graph

12 Commits

Author SHA1 Message Date
oliverschmidt
4e30e73bdb Activated Platform-specific File System (PFS) for the C128 by default for all programs with R/O CFS access. 2010-04-06 10:39:50 +00:00
oliverschmidt
6c4c98644e Activated Platform-specific File System (PFS) for the C64 by default for all programs with R/O CFS access. 2010-04-06 10:24:43 +00:00
oliverschmidt
1817acae15 Now that the C64 mouse driver works we can activate the mouse support for this target :-) 2010-02-18 21:30:31 +00:00
oliverschmidt
7ef7efecd8 Without forms, centering and history we can just squeeze in DNS. 2010-02-13 10:44:23 +00:00
oliverschmidt
ce48ac2d94 Added high-level config macros for the C128 (due to lack of memory no DNS support for the webbrowser). 2010-02-01 21:15:36 +00:00
oliverschmidt
75b773c45c Deactivated mouse support on the C64 because of "phantom keystroke" and "phantom mouseclick" issues :-( 2010-01-31 13:40:50 +00:00
oliverschmidt
1fe9bf24c9 Re-added temporarily removed file. 2010-01-31 13:36:06 +00:00
oliverschmidt
40101db78f Temporarily removed file due to CVS issue. 2010-01-31 13:34:19 +00:00
oliverschmidt
4dcbc3273e Now that we started adding files to the CVS which are normally generated with a 'save...' make goal we can remove the DEFAULT_TARGET mechanism altogether and just add Makefile.target files. 2008-05-26 10:09:12 +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
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