Actually, I'm not sure that the FreeSCI code should be split into many
libraries. The only thing that makes sense to me is creating a separate
library for code that will be used by external console-mode tools (like
scidisasm or possibly some SCI development tools).
Other than that, a single dynamic-link library containing all the code
except for the uppermost level (main.c and config.c) should work just fine.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 18, 2000 11:36 PM
To: [EMAIL PROTECTED]
Subject: cvs: cvsuser
* all tools are now statically linked against libscigraphics.a. This is sub-
optimal.
Taking care of this cleanly will probably require libscicore.a to be split
up
into two separate libs: libscicore.a (resource management, decompression),
and
libsciengine.a (vm, kernel, etc).
I think I'll replace the 'core' directory with 'scicore' (core should be
reserved for core files, even if those don't belong into src/) and an
'engine'
one. I'm open to alternate suggestions, of course; I probably won't be able
to
do this until saturday or sunday anyway.
-- Christoph
