Hi... > Looking at the format of the CMakeLists.txt > file, it should be fairly straightforward for developers to add new > widgets/whatever, even if they do not have CMake installed to test their > changes (hence they should tell the list, and leave it to someone who > can test before committing).
That's the idea. Hopefully it will also be possible for non auto* users to modfiy those files as well. In practice, your suggestion of emailing back and forth is probably the most practical (given that the number of developers and overall number of classes being changed at any one time will probably be relatively low). So, to summarize, we'll have two "official" build systems: auto* for the Unix crowd - Maintained by Ross et. al. CMake for Windows or non-auto* Unix people - Maintained by Damion I have fewer qualms about forcing CMake on Windows people, since there's a small binary download and Visual C++ projects are notoriously difficult (impossible) to manage using CVS alone. > Hopefully, I'll be in a position to look a bit closer at the OpenGC > auto* support soon. I've been stalled a bit by having a fried CPU on my > main FlightGear workstation, which I've still not fixed. I've been > working from my laptop for last two weeks, which doesn't do 3D so well. No rush... I'm still getting caught up on Matlab (aarrrgh) coding after being at conferences for two weeks early this month and Thanksgiving last week, so I'm probably not going to get anything major accomplished until early December. John's made good progress on the Unix/Flightgear end, and we have a few people lurking in the sidelines waiting for the system to stabilize who'll be developing gauges. I'm going to take a look at the map/ND stuff posted last week (Atlas) so hopefully we'll have a beta 777 cockpit early next year (keep your fingers crossed). Cheers, -Damion- _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
