On 6/26/10 7:36 PM, Alan Teeder wrote: > Is there any need for this to be done by all new cloners before compilation? > It seems to be an unnecessary complication.
The reason for having autoconf to replace the version string is that there should only be one place where the version string is set (configure.ac or some associated file depending on the build system setup). (Some) Mac and all(?) linux users use autoconf and there is no issue. I suppose the problem of copying the file and changing the string manually affects windows and mac xcode (I think) users. The source file is the .in file and that should be in the repository and nothing else. > All GIT users should be currently working with the same version (2.0.0) in > both simgear and flightgear. As and when a new version comes about both > these files can be updated and committed by whoever is responsible for > raising the issue number. Well, technically git users are working on 2.x (or 2.0.x or what ever the next version will be called). Again, the idea is that the version number should only be changed in one place and propagated by the build system. In your case it is a header for MSVC and for other developers the version will be propagated to other files. This type of scenario is error prone. Cheers, Jari ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
