Richard Bytheway writes:
> SimGear - configure does not find the metakit libs unless I 
> set LDFLAGS="-L/usr/local/lib/". Is this a SimGear, Metakit, 
> Autoconf or Cygwin problem?

SimGear/FlightGear configure used to automatically add /usr/local/lib
to the library search path.  That was removed because apparently it
causes gcc-3.2 to gripe?  Someone needs to explain the gcc-3.2 problem
so that we can get this resolved in a way that works for everyone.

> SimGear - simgear/sky/clouds3d/SkyTextureState.cpp -
> glActiveTextureARB is undefined. For now I have removed the clouds3d
> directory from the Makefile in .../simgear/sky, but this is
> obviously a workaround, but I got stuck trying to find the real fix.

There are numerous issues with the 3d clouds.  We don't have anyone
addressing them at the moment, so they are not activated by default
(but the code is still built.)  For now, what you did isn't a bad
solution.  The solution for this particular problem is to impliment
opengl extensions correctly, but no one here seems to know how to do
that. :-(  It's a harder problem than it might first appear though
because MS ships with opengl 1.1 headers I believe so you can't
depend on a particular opengl version, and extensions being what they
are, you can't depend on them being on a particular platform.  And to
make matters worse, the extension mechanism is different between
windows and unix ...

> FlightGear - configure cannot find Metakit without setting 
> LDFLAGS as above.

Same /usr/local/lib issue ... apparently we don't include
/usr/local/lib in order to appease the gcc-3.2 gods, but then it never
get's included at all ... why does gcc-3.2 detest having to look in
/usr/local ???

Regards,

Curt.
-- 
Curtis Olson   IVLab / HumanFIRST Program       FlightGear Project
Twin Cities    [EMAIL PROTECTED]                  [EMAIL PROTECTED]
Minnesota      http://www.menet.umn.edu/~curt   http://www.flightgear.org

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to