Commit graph

15 commits

Author SHA1 Message Date
Oliver Schmidt
d79ac1558a Added missing 'atarixl' Makefile defines. 2013-10-04 00:03:40 +02:00
Oliver Schmidt
57d9c43a33 Removed support for 'atari' now that 'atarixl' is part of the cc65 master. 2013-10-03 22:55:32 +02:00
Adam Dunkels
944537fccf Removed all old RCS tags in the Contiki source tree. Those RCS tags are not used any more, as we are now using git to manage the Contiki source tree 2012-10-26 15:54:49 +02:00
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
fros4943
9fb4c73d8d WITH_UIP in Makefile 2010-03-10 12:21:12 +00:00
oliverschmidt
b4d6dd6893 Added webserver and irc. 2009-03-01 23:37:49 +00:00
oliverschmidt
c109e102c4 Include wget shell command in "standard" shell environments. 2008-11-10 22:10:32 +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
0fc8481f15 As adding some commands to the telnet server shell doesn't seem to be desirable in the application it's now done in the example. 2008-02-28 23:12:47 +00:00
oliverschmidt
7f7f11d30f Set default target to minimal-net. 2007-05-26 22:42:02 +00:00
oliverschmidt
7168278a89 Adding 'APPS+=program-handler' in apps/Makefile.telnetd might be considered more consistent but I opted for this more obvious approach. BTW yet another example that from my perspective simply can't have worked... 2007-03-03 13:32:10 +00:00
adamdunkels
c9e808d638 Import of the contiki-2.x development code from the SICS internal CVS server 2006-06-17 22:41:10 +00:00