Marcus Barnes (marcus++at++multigen.com)
Fri, 11 Apr 1997 11:57:07 -0700
For the most part they represent sets of binary and/or link compatible DSO's.
Performer DSO's with different major versions (ie [234]) will not work
together.
> I am specifically interested in how they relate to Performer releases
> (i.e. is sgi3.0 Performer 2.1, sgi2.0 Performer 2.0 etc?).
Perf. | DSO IVERSION
=================================
2.0.X | sgi2.X
2.1.X | sgi3.X
2.2.X.Y | sgi4.X.Y*
* "X" denotes maintenance version
* "Y" denotes alpha version
/usr/include/Performer/pr.h defines two or three version symbols. The
maintenance symbol is not defined in 2.0, 2.0.1, 2.0.2.
#define PF_MAJOR_VERSION 2
#define PF_MINOR_VERSION 2
#define PF_MAINT_VERSION 0
> Do I need to use them if I am writing my own libraries?
Yes.
> If so what convention should I follow?
Use the same convention as Performer. Loader's in particular much match the
version string that pfdLoadFile is using.
Regards.
--
+ Marcus Barnes, Technical Staff mailto:marcus++at++multigen.com +
+ Multigen Inc. http://www.multigen.com +
+ 550 S. Winchester Blvd. phoneto:1-408-556-2654 +
+ Suite 500 San Jose CA 95128 faxto:1-408-261-4102 +
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:55:03 PDT