Erik Hofman wrote:
> Martin Spott wrote:

> > .... but apparently this is not the correct place, at least it doesn't
> > get transferred over to 'configure' during automake/autoconf. Where do
> > I add the desired flag ?
> 
> Take a look at FlightGear's configure.ac. It should have a special 
> section for FreeBSD plib support.

The OpenAL check already happens in SimGear - this is the place where
it doesn't work. I tried several things, including removal of the
whole "FreeBSD -lpthread cheat clause", but I still didn't succeed.
So I'll stick to the manual 'correction' until I understand - at least
partially - how automake/autoconf works. This might take some time  :-)

Besides this, I had to make some very small changes. One of them is in
Simgear - please don't ask me _why_, I just can tell you that it makes
the whole thing work  ;-)

--- simgear/screen/extensions.cxx~      Thu Nov  4 16:14:59 2004
+++ simgear/screen/extensions.cxx       Thu Nov 18 17:52:25 2004
@@ -113,7 +113,7 @@
     if (libHandle != NULL) {
         fptr = dlsym(libHandle, func);
 
-        char *error = dlerror();
+        const char *error = dlerror();
         if (error)
             SG_LOG(SG_GENERAL, SG_INFO, error);
     }


Adding to that, FreeBSD-5.x, at least 5.3 appears to have a modified
joystick interface. For every occurrence of '-lplibjs' I had to add
'-lusbhid'. This is the case for src/Input/js_demo, src/Input/fgjs,
src/Main/fgfs and utils/js_server/js_server


Curt, you can add FreeBSD-5.3 to the list of supported platforms  :-)
It is not _that_ fast as recent tests with XOrg CVS on SuSE-9.0 but
this might simply be related to the not that upt-to-date XOrg release
that comes with FreeBSD-5.3,

Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------

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

Reply via email to