Hello, All.

I'm trying to refine Windows package building and I wonder if subj can be used to distinguish production status of the build. Currently it is done by parsing of whole file for words like "UNSTABLE", "Beta", "RC" etc. From observing build_no.h from different branches I assumed that "T" stay for unstable versions and "V" for releases.
  Am I right?
  May be it would be better to use other macro for this?
--
  WBR, SD.


Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to