From: Tor L. <tm...@ik...> - 2001-10-17 17:10:51
|
(Sorry for the late follow-up, but I just now remembered that I was supposed to look into how SDL allegedly handles the problem.) David Weisgerber writes: > the right place in my mingw installation ? [Why are the Gtk people not able > to make it installable like SDL, for example?] and later: > The only thing I can say about that is, that it worked for SDL > under linux / mingw AND linux / gcc I downloaded the SDL-1.2.2 developer packages from libsdl.org, and lo and behold, the "mingw" version does contain a sdl-config shell script. *but*, this script contains a harcoded reference to /usr/local/cross-tools/i386-mingw32msvc. Surely not a path that the average mingw user would use? Also, remember that if one interprets the term "mingw" strictly, there is not necessarily any (Bourne-compatible) shell available for a mingw user to interpret such a shell script on Win32. SDL had separate developer packages for VC5, VC6 and mingw. There certainly wasn't, for instance, any installer that would automagically had set up the headers and import libraries somewhere for MSVC to find. (Instead, the VisualC.html file tells you to copy the .lib files into your Project directory, etc.) I don't see what you mean by the SDL people being able to "make it installable". A certain amount of hand work is needed. For instance copying files around (in general, a bad idea) or adding -I and -L switches to makefiles. --tml |