The api hides all the gory details of message buffer setup and usage
(particularly the differences between writing and reading). Most
importantly, the api provides a safe way to read and write binary data
(always little endian).
Despair has things locked down such that running qfcc during a build fails
due to lack of read access to /usr/local/lib. This is actually a good
thing as accidentally hitting old includes/libs (when a file gets deleted
in the tree) hides bugs. Thus, --no-default-paths to turn off default
search paths.
I'm not sure why this is happening now when it didn't in the old qfcc,
but this will take care of the warning for now until I can get around to
fixing it.
This version is a bit more useful, and we should be able to get rid of the
Stack class. Also, the Ruamoko parts of the autorelease system should be
almost ready now.
class with the same name. This will break things. To support it, there are
three new classes, one of which is incomplete (AutoreleasePool). It'll get
finished soonish, but the rest of the class lib will need some updating to
work.
define default include and lib paths for qfcc
ruamoko:
{cl_menu,game}/Makefile.am:
conform to the new qfcc library linking rules
lib/Makefile.am:
install the libs to ${prefix}/lib/ruamoko
qfcc:
linker.[ch]:
support path searching for -llib and make linker_add_lib search for
libfoo.a for -lfoo in the paths, or just a single dir search for the
libname otherwise.
options.c:
support -L libpath and setup the default include and lib paths
also change most strdup calls to save_string
qfcc.c:
check for foo.a as well as -lfoo when deciding whether the file is
an object file or lib file.
