On 5 Sep 2011, at 17:10, Curtis Olson wrote: > So I have nothing against cmake, it sounds like it offers some nice features. > But I assume those that want to push this change forward, will take some > time to write up some basic howto's so that people who have never used it as > a developer can get up to speed without too many problems? > > Right now when I poke around on the wiki and I'm sure the getstart manual, > all the instructions are automake based. Hopefully we can do some proactive > hunting of automake references in our instructions scattered around and get > those cleaned up in advance?
> Are there any cmake based build instructions available anywhere? I'm not > seeing them. Yes, absolutely - Brisa's helper script also needs to be updated. We're at the start of that process now, but I don't want to document things if they are about to change, which brings me too: > > When building OSG, you run "./configure; make; make install" like any other > project. However, ./configure is an automake/conf generated in flightgear. > For a cmake dummy, how do you even go about building flightgear with cmake? > (I of course know everything, but I do have a friend who's a little > inexperienced with cmake.) OSG supply a 'configure' script for sue with Cmake, and we can do the same, to keep things more familiar for people. I'll look into borrowing the CMake one :) > Is there a way to do the equivalent of "make dist" in cmake to generate > .tar.gz source releases? Has this been tested to see if it includes all the > necessary files? That's what CPack does - I've tested tar.gz creation, and there is some supported for Slackware TGZ / .deb / .rpm creation too. I'm sure the rules need some improvement to catch all the docs / utils / data files that the current make dist captures. > We have some extra automake rules to help create the data archives (which is > important because this officially defines what goes into the release > installer for both Mac and Windows as well as the data archive for people > building from source code (who aren't doing 3Gb of git for the data tree.)) Indeed! > I'm just hoping the cmake jocks will put themselves in the position of > non-cmake jocks and help ease the transition from multiple fronts for many of > our different classes of users/developers. Yes absolutely, and feedback (like above) is the driver for that. james ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
