Recent changes to support-requests

Data file untar problem...

Anonymous — Tue, 20 Nov 2001 23:28:03 -0000

Is it possible to download and use
basilisk.1.04_data.tar.gz in a Microsoft (Windows ME)
environment? When I download it, and attempt to untar
it using WinZip, I get "Error after processing 60
entries". I've tried version 1.03 (data) and 1.04
(all); the only difference is how many entries it
processes before the error occurs.

The source code archives untarred successfully.

What I am doing wrong?

Thanks in advance.

Dynamic linking on Suse 7.1

Chris Williamson — Wed, 25 Jul 2001 22:37:37 -0000

Hi,

I'm a Linux newbie, so apologies in advance if I've done something obviously wrong.

I used "make dynamic" the as suggested described in the README, but this gave an error linking to the library libbasilisk.so.

After lots of manual reading etc, I managed to get the make to work by typing the line:

export LD_LIBRARY_PATH=.

and then running the makefile

Is there a better way of doing this?

Should something be put in the readme?

Cheers,

Chris Williamson

Compiling Basilisk on Mac

Roger Bonzer — Thu, 08 Mar 2001 16:54:40 -0000

Spent more time trying to compile & run basilisk on
the Mac. I can actually read in .bsk files and compile
a database. Haven't tried using it, or loading or
saving the bdb file. Anyway, here's the latest results
with basilisk.1.01:

bsklexer.c, lines 251-256, change
from:
if( c != '\n' ) {
s_pushChar( lexer, c );
} else {
c = '\r';
}
to:
if( c != '\n' ) {
s_pushChar( lexer, c );
}
c = '\r';
why:
mac uses '\r' as its eol character. s_nextChar() is
looking ahead to try to convert '\r\n' sequences to '\
r', but doesn't want to blow away the look-ahead
character if it isn't a '\n'. unfortunately, what it
does is not only save the look-ahead character in the
lexer's buffer, but also return *it* as the character
found, rather than the '\r'.

bskparse.c, lines 103-107
from:
#if defined( __unix__ )
#define FILE_SEPARATOR "/"
#else
#define FILE_SEPARATOR "\\&quot;
#endif
to: ????
why:
mac uses ":" as file separator characters. i'm not
sure what conventions you are using for cross-platform
support issues, so i don't know what to suggest as the
final answer

bskparse.c, line 3896
from:
subStream = BSKStreamOpenFile( streamName,
"rt" );
to:
subStream = BSKStreamOpenFile( streamName,
"rb" );
why:
opening files in "rt" mode is, as far as i'm aware, a
non-portable method of opening a
file in text mode. according to my docs, opening
in "r" mode should have the same effect. on the other
hand,
s_nextChar() in bklexer.c already translates line
endings, so opening the file in binary mode should
work
regardless. also, note that the treasure generator
source code opens up the main file "index.bsk" in
binary
mode, but all the other #include files will be opened
in
text mode. i'd just blow off opening the file in text
mode since it doesn't buy you much anyway.

Make the code C++ compliant

Anonymous — Tue, 06 Mar 2001 18:56:35 -0000

It isn't that difficult to write C code that can be
compiled under C++. The attached file lists 5 easy edits
to the basilisk 1.01 source files that will let the code
compile under C++.