3 Commits

Author	SHA1	Message	Date
ol.sc	fb7d8a7c37	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	2012-02-17 20:23:35 +00:00
ol.sc	764f07e56b	Reuse the character specification table from the base target. ... git-svn-id: svn://svn.cc65.org/cc65/trunk@5517 b7a2c559-68d2-44c3-8de9-860c34a00d81	2012-02-09 16:40:18 +00:00
ol.sc	bf6b0f1e4b	Initial Apple GEOS build. ... git-svn-id: svn://svn.cc65.org/cc65/trunk@5512 b7a2c559-68d2-44c3-8de9-860c34a00d81	2012-02-09 10:03:54 +00:00