Re: Bug in Build system.

Darren Vincent Hart wrote:
> On Mon, 2003-09-08 at 09:00, Marc Strämke wrote:
> 
>>(Sorry to report here, our bugzilla seems to be broken *G*)
>>The Build system doesnt work if the user hasnt got SDL installed, this 
>>is so because it cant find the AM_PATH_SDL macro, so basically atm you 
>>cant build on a system which doesnt have SDL installed.
>>
> 
Ok right :)
Now i that i think about it i fully agree, i'am just too much used to 
running autogen ;)
Taking Aclocal out of autogen and giving a "good" aclocal.m4 file over 
the CVS would solve the issue too, and still give developers without SDL 
installed the opportunity to regenerate the Makefiles, doesnt it? Dunno 
if there are versioning probs with the aclocal file though

> IMO this isn't a bug.  Those who are going to *develop libstk* should be
> able to run autogen.sh (and therefor will need all the macros it
> needs).  End users (programmers who will *use libstk*) will just use the
> configure script we generate and distribute (and therefor won't need the
> AM_PATH_SDL macro).
> 
> In order to "fix" this, we would need a preprocessor for configure.in
> (and I have my fill of indirection in the build process thank you very
> much).  I looked into this for an hour or so tonight and the only way to
> do this would be to use pkgconfig, which SDL doesn't at the moment.  So
> until then, install SDL (or at least the SDL .m4 file, I can make that
> available if people want that).
> 
> If anyone knows of a better solution, please let me know, otherwise just
> install the libsdl devel packages and be done with it.
> 
> Darren
> 
> 
>>
>>_______________________________________________
>>Libstk mailing list
>>Libstk@Óq«LD—"
>>http://www.dvhart.com/cgi-bin/mailman/listinfo/libst
> 
> k