[Openib-windows] Branding

[Fab Tillier]

> From: Tillier, Fabian
> Sent: Wednesday, October 19, 2005 11:16 AM
> 
> > From: Yossi Leybovich [mailto:sleybo at mellanox.co.il]
> > Sent: Wednesday, October 19, 2005 11:02 AM
> >
> > > From: Fab Tillier [mailto:ftillier at silverstorm.com]
> > > Sent: Wednesday, October 19, 2005 7:47 PM
> > >
> > > Right now since the SVN trunk is under "gen1", the major
> > > version number is 1. The minor number is zero just because we
> > > have to start somewhere.  We can define a process by which
> > > major and minor version numbers are changed, but this can
> > > wait until we need it.
> >
> > One more little thing don't you think it better to put the SVN
> > version var in last number (VER_FILEREV(
> 
> If you look at Windows binaries, they use the 3rd field in the
> version number to indicate the build number.  I was just going
> to use the SVN revision as the build number, but we could use
> monotonically increasing build numbers instead and put the SVN
> number in the VER_FILEREV field.  I'm open to suggestions here.
> In fact, the VER_FILEREV field could be used to indicate the OpenIB
> version, and the VER_FILEBUILD the company specific build number.
> This might be a good way to give information about what SVN version
> a vendor specific build is based on.

Ok, I just committed a patch that allows overriding the branding information -
company name, product name, major, minor, build, and revision numbers by setting
IB_COMPANYNAME, IB_PRODUCTNAME, IB_MAJORVERSION, IB_MINORVERSION, IB_FILEBUILD,
and IB_FILEREV environment variables.  The file revision expects the OPENIB_REV
environment variable to be set if IB_FILEREV isn't, and it should be set to the
SVN revision number.

- Fab