Christian Mayer wrote: > Andy Ross wrote: > > Is that correct? In my SimGear installation tree, easyxml.h is under > > /simgear, there is no /simgear/xml directory. In the SimGear *source* > > tree, that's where the file is. But you're not supposed to be > > building against the source tree. I suspect you have a bug in your > > project configuration. > > No. I'm using the latest CVS. And the file lives (on my System) in > > K:\Projekte\SimGear\simgear\xml
That's the source tree -- the stuff you've checked out of CVS. Under the autoconf build procedures, there's a "make install" step that puts the SimGear header files into a specified target directory (the default is /usr/local/include/simgear). When installed, easyxml.h goes into /usr/local/include/simgear/easyxml.h. The FlightGear files, which are a separate package, are written to be compiled against the *installed* SimGear tree, *not* the files that are checked out of CVS. Now, one might argue that an installed header file shouldn't live in a different relative path from the one in the source tree, and I would agree. But nonetheless, FlightGear's current build procedure requires that I include <simgear/easyxml.h>, because <simgear/xml/easyxml.h> isn't available at build time. Maybe the fix is to move the installation location for this file? The reason this bites only YASim, I suspect, is that I'm the only non-SimGear code that actually uses this file. Everything else uses the PropertyTree "wrapper" parser instead. I didn't know about this at the time, so I just used the raw SAX-like parser instead. Andy -- Andrew J. Ross NextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
