My recent decision to reuse the character specification table from the base target was based on the fact that CBM GEOS used a copy of the CBM character specification table for the last ten years.

However now I understand that CBM GEOS does _not_ use PETSCII so the CBM character specification table doesn't make sense at all. After all this is very plausible because GEOS wants to enable the user to share his files across GEOS variants - so we can share the character specification table too.

git-svn-id: svn://svn.cc65.org/cc65/trunk@5527 b7a2c559-68d2-44c3-8de9-860c34a00d81
This commit is contained in:
ol.sc
2012-02-17 20:23:35 +00:00
parent 7d2972fdb2
commit fb7d8a7c37
4 changed files with 286 additions and 14 deletions

View File

@@ -41,11 +41,6 @@ CFLAGS = -Osir -g -T -t $(SYS) --forget-inc-paths -I . -I ../../include
%.tgi: %.o ../runtime/zeropage.o
@$(LD) -o $@ -t module $^
#--------------------------------------------------------------------------
# Object files
S_OBJS= ctype.o
#--------------------------------------------------------------------------
# Directories
@@ -72,8 +67,8 @@ TGIS = geos-tgi.tgi
# Directives
include $(addsuffix /Makefile, $(DIRS))
vpath %.c $(DIRS) ../cbm
vpath %.s $(DIRS) ../cbm
vpath %.c $(DIRS)
vpath %.s $(DIRS)
#--------------------------------------------------------------------------
# Targets