I'm using the wattcp development package. When building the source code into library modules, which compilation mode is used?
TRACE - turn on tracing/debugging code
SKIPINI - bootp/dhcp only, no WATTCP.CFG (size critical apps)
ETH_MSS - you might set =576 for serial use (EPPPD), mostly
useful if lacking CFG file (SKIPINI, etc)
TW_TO - set between 30 and 240 for an RFC-compliant
TIME_WAIT period (defaults to 2, higher can delay
sock_wait_closed() much longer)
#CFLAGS= $(DEBUGS) -DMSDOS -IC:\borlandc\include -I..\include
#CFLAGS= $(DEBUGS) -DMSDOS -IC:\bc4\include -I..\include
#CFLAGS= $(DEBUGS) -DMSDOS -DSKIPINI -DETH_MSS=576 -IC:\borlandc\include -I..\include
CFLAGS= $(DEBUGS) -DMSDOS -DETH_MSS=576 -IC:\borlandc\include -I..\include
I configured the wattcp.cfg file, but I don't know which compilation mode should be used together with my configuration file?
TRACE - turn on tracing/debugging code
SKIPINI - bootp/dhcp only, no WATTCP.CFG (size critical apps)
ETH_MSS - you might set =576 for serial use (EPPPD), mostly
useful if lacking CFG file (SKIPINI, etc)
TW_TO - set between 30 and 240 for an RFC-compliant
TIME_WAIT period (defaults to 2, higher can delay
sock_wait_closed() much longer)
#CFLAGS= $(DEBUGS) -DMSDOS -IC:\borlandc\include -I..\include
#CFLAGS= $(DEBUGS) -DMSDOS -IC:\bc4\include -I..\include
#CFLAGS= $(DEBUGS) -DMSDOS -DSKIPINI -DETH_MSS=576 -IC:\borlandc\include -I..\include
CFLAGS= $(DEBUGS) -DMSDOS -DETH_MSS=576 -IC:\borlandc\include -I..\include
I configured the wattcp.cfg file, but I don't know which compilation mode should be used together with my configuration file?