That did it, compiled without any problems. One last question is there any way to have scons 'install'? Copying globulation manually works but just seems so inefficient.
On Tue, 2007-07-24 at 13:00 +1200, Kieran P wrote: > I get the same problem with my copy of scons_conversion. It has > something to do with windows needing the sh reference in ParseConfig > and linux hating it. An environment if statement should fix these > easily (in the meantime, open up glob2/SConstruct and find the two > instances of ParseConfig and remove the "sh " bit before the > sdl-config call (sdl-config is a standard file installed with SDL I > beleive which locates SDL library directory based on the OS its run > on?). (note, scons still wont work on Windows so you just might have > to revert to autotools for Windows builds :( > > Regards > Kieran > > > On 7/24/07, donkyhotay <[EMAIL PROTECTED]> wrote: > This is probably something basic but I've never used scons > before and am > having a little trouble. I assume to use scons it's simply a > matter of > going into the correct directory and typing: > scons > > and it should configure and compile automatically. Now when I > do this I > get: > [snip] > > which makes it look like a SDL library is missing. There is no > libsdlconfig that I am aware of and according to the website > no new > libraries are required for compiling that weren't required > under cmake > (except fribidi which I have already installed). Any ideas on > what I'm > doing wrong? It'd be nice to be able to test the latest > version. > _______________________________________________ > glob2-devel mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/glob2-devel -- Do not be afraid to joust a giant just because some people insist on believing in windmills. _______________________________________________ glob2-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/glob2-devel
