Commit graph

5 commits

Author SHA1 Message Date
Oliver Schmidt fb5d0b7ef0 Made 80 column display a cc65 application attribute.
So far 80 column display was an attribute of a cc65 platform. Now each cc65 application can ask for 80 column display by defining WITH_80COL. Of course this is ignored by platforms incapable of 80 column display.

I see three types of application:

* Applications not benefitting from 80 column at all and in fact looking better with 40 column display. These are now using 40 column display. Examples: ethconfig, ipconfig

* Applications taking advantage of 80 column display if it is available without drawbacks. These stay as they were. Examples: Telnet server, web server, wget

* Applications needing 80 column display so urgently that it is likely desirable even if the display becomes harder to read. These come now in both flavors allowing the user to choose. Examples: IRC, web browser

Note: This change doesn't actually introduce any 80 column display with drawbacks. This if left to a subsequent change.
2015-10-30 12:42:58 +01:00
Oliver Schmidt fc9d38caba Reduced default for number of connections.
Save some memory by reducing the the default for number of connections from 10 to 2.
2015-06-21 20:58:51 +02:00
oliverschmidt 8b6d34dbfc Configure maximum number of C128 web server connections indirectly via maximum number of TCP connections. 2010-04-11 21:34:18 +00:00
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 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