Re: some SDL configure options, and a question

[Stan Shebs <shebs at shebs dot cnchost dot com>]

Alan Schmitt wrote:
> 
> Hi,
> 
> Here are some files to make sdl configuration easier (for instance to
> check were the include files are). I did not do much here, just went
> through some other sdl projects to see how they did it.

Thanks, these will be very convenient!  I probably won't be able
to try them out before going on vacation, but Hans or Jim could
take up the slack if they're so inclined.

> Now to the questions:
> 
> sdl-conq does not work, it fails with the error
> Error: could not open SDL small_font.
> 
> Which font is that suppose to be.
> 
> Well, looking at the code, I got it. Maybe a readme that says to
> launch sdlconq as ./sdlconq -L ../images in x11 ?

Item 5. in INSTALL touches on this, but it doesn't address the SDL
interface's absolute requirement for a font.  What I do personally
to avoid fiddling with -L is to setenv XCONQLIB to point to my CVS
sandbox's lib dir, and Xconq knows how to find images/ as a sibling.

(To tell the truth, based on past experience, I didn't expect quite
so many people trying out the SDL interface in its half-written
state.  I guess that's good... :-)  )

> Another question, about cvs this time: I never download the tcl and tk
> directory. Is there a simple way to exclude them (on my side) from the
> cvs update, or maybe to put them in another module on the server side,
> so that they are not downloaded automatically.

You should only get those if you check out "xconq-all" or else check out
the repository en masse.  They are not in the standard "xconq" module.
In any case, you should be able to delete those dirs in the sandbox and
not be troubled by them again, unless your cvs preferences say -d for
updates or some such.

> Thanks for this great game,

You're welcome!

Stan