Julian Foad writes: > configure.in includes a fix to make it work with both versions of > the auto-tools: > > if OLD_AUTOMAKE > INCLUDES += -I$(top_srcdir) > else > INCLUDES = -I$(top_srcdir) > endif > > But > (1) If "=" is good enough in the new version, isn't it good enough > in both versions?
Technically it's not quite good enough for both versions. > (Not necessarily: maybe the meaning has changed.) <ding> <ding> <ding> The new automake changed around the names of the user setable variables vs. the built in variables. The new automake way actually makes more sense than the old, but it's not forward or backwards compatible which is a pain for us. We might be able to get lucky and still build with the old version and just use INCLUDES = , but that could break the make for some people with the old automake under some circumstances. I'm tempted to try this and tell people to upgrade if they run into problems, but that's not a perfect solution either. For some people, on some platforms, in some environments, upgrading is not an easy option. <OT> You know what would be cool to mess around with someday is a bootable linux cd that comes up with flightgear running, right off the cd. Yeah, video driver issues, I know, sound driver issues, net card issues, but still, would be cool if we could find a reasonable way to detect the hardware and load the appropriate drivers. </OT> 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
