On Mon, 6 Jan 2003 22:55:56 -0600 "Jon Berndt" <[EMAIL PROTECTED]> wrote:
> > I found it very helpful to capture a compile date and cvs tag into a > > chip design that verification people could use to direct me to a > > particular verilog code base to reproduce and debug problems. > > Good idea. We sort of do this for JSBSim. Isn't there a command that you > can type to get information on an executable? I can do something like > this: > > strings jsbsim.exe | grep Id > > and get a list of all the modules and version/date information that went > into the executable. That doesn't get the compile info, but it is a start. > Aren't there compiler-defined variables that could go into a version > string which could be displayed when someone typed: > > fgfs --version > > ?? > The very first thing FG displays is its version number and compiler info: [bbright@proton Main]$ ./fgfs FlightGear: Version 0.9.1 Built with GNU C++ version 3.2 Scanning command line for: --fg-root= ... It would be trivial to add a timestamp. Cheers, Bernie _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
