James Turner wrote: > I'm always curious to know how other Mac users build FlightGear - does > your build setup produce an fgfs binary (or application bundle) you > could make available somewhere? It would provide another case I could > test locally.
Since recently I actually do both (sort of). Since the past few months I have created fgfs, terrasync, atlas, and map. All from their respective repositories. I have an update and build script that updates my working copies and rebuilds the packages if needed. This of course has to be done in the proper order because of dependencies. Also, I avoid installing to much of the moving targets so my set up is not straightforward to copy ... actually come to think of it, if I redo some things it will be fairly easy to copy my setup. Also I use a start-up script that points to different locations to run fgfs (I share data with development and released versions of fg). The reason for doing the above is that I do not like the macflightgear strategy of having snapshot copies of different fg components in the macflightgear repository. Also, getting access to all new stuff takes a while since the macflightgear maintainer must update the repo. Last week I realized that I miss the OSX lancher. I checked out the OSX launcher from the repository (trunk branch ... I don't get latest fixes to the launcher :-0), hacked around with the Xcode stuff and now I have an application bundle. Unfortunately I only bundle minimum amount of information and use links to fg/data and some other things which makes the current bundle non-distributable. The fg app works well and I think that terrasync also works but Atlas is currently broken on my machine because Atlas is currently in heavy development (I use Atlas CVS trunk). In conclusion when my Mac bundle is usable I'll make it available. Jari ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
