John Wojnaroski writes: > Just to add a little more confusion .... > > Boy, this is turning into a real bad mess. > > The unix source on kingmont builds with the freetype 1.3 and gltt and should > work with the latest version of FG from the CVS, but the displays are > minimal, just the PFD stuff. Check the email thread starting about 3 Nov > from Flavio Villanuestre, there were a few hiccups during the build but it > did run. > > I have a version with an EICAS panel that displays engine data, but will > need updates to the source in the FG network directory and the source at > kingmont. Good news -- all you have to do is replace the old with the new > versions and rebuild if you get it built the first time. > > The source at the OpenGC repository has been converted to freetype-2.0.4 and > ftgl libraries. I'm converting over but it is taking a little time. That > source, as noted, is Windows only and DOES NOT have the interface module > ogcFGDataSource or definition of the class structure required for > Flightgear. There is the start of a gnu make/build system by Ross Golder but > more work is required. > > To add to all this, for some inane reason Damion has tried to setup my CVS > account at sourceforge but no luck. I believe he is moving the respository > to another site. so I can't commit my changes/updates until that happens > > I suspect if we were doing this for a living, we' ld all be fired by now ;-) > > Give Damion and I a few days to iron this out. I don't think any of the > interface stuff is library dependent, so we should be able to stick in the > FG inteface stuff. I can provide the latest versions of opengc.cxx, > opengc.hxx and opengc_data.hxx which belong in the ~/FlightGear/src/Network > directory to replace the versions in the CVS stuff.
Hehe, you are just discovering that this open-source project management stuff isn't as easy as it looks. :-) Seriously though, expect it to take time to get a project up to speed, or an existing project up to speed on a new platform, and work out the kinks. It just takes a bit of persistance. Also, I encourage you to avoid having multiple versions of stuff floating around if at all possible. Keeping everything centralized helps in a single repository avoids losing changes or having one set of changes stomp on another, or having one group take off in some direciton and leave other people's changes in the dust. Perhaps you could lobby Damion to commit your changes into his CVS repository until you can get the SF procedures straightened out. If you don't get your changes commited to the master repository, you are going to spend the rest of your life chasing Damions changes, and he won't know when he does something that ends up causing severe problems for you. Once your stuff is in, it's in and hopefully, at worst, you'll only have to make occasional minor tweaks to keep it working with anything new that Damion does. Also, it forces him to think about how his changes affect your stuff. Regards, Curt. -- Curtis Olson Intelligent Vehicles Lab 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
