Re: Performer2.0 installation

New Message Reply Date view Thread view Subject view Author view

Rémi Arnaud (remi++at++remi.asd.sgi.com)
Thu, 27 Feb 1997 11:04:50 -0800 (PST)

Kaylor Brett wrote:
>
> I have been using Performer2.0 in IRIX 5.3 for some time now. We just
> upgraded to IRIX6.2 on a cleaned hard drive. So I installed
> Performer2.0
> on the clean system. One library (libpfs) did not show up. I look all
> over
> the CD and couldn't find it. I got everything else ok. I went ahead
> and
> installed patch 1347 which brings Performer up to 2.0.2. That got me
> the
> dynamic libpfs.so library, no static though. Here are my questions:
>
> 1. Shouldn't the distribution disk contain a static and dynamic version
> of
> the libpfs library?
>
> 2. Patch 1347 only contained patches for the dynamic libraries. Does
> that mean if I link dynamic I get Performer2.0.2 and if I link static I
> get
> Performer2.0?
>
> If anybody can clear this up for me I would be most grateful.
>
> Brett.
>
> P.S. The static lib /usr/lib/Performer/Static/libpfs.a was there before
> the
> upgrade to 6.2. I just don't remember how it got there.
>

 Hi,

  The libpfs is the Terrain feature for performer, which was not
  available before 2.0.2. That's why it's not in 2.0

  A patch is for the eoe environement (execution only). It is to
  be installed on a computer to remove the bugs without recompiling
  any application. It is not usefull to include a static library
  into a patch as it will not change the behaviour of any application.
  A static library is therefore part of the development environnement,
  (the one you have to pay for !)

  Note that the eoe of Perfomer is free, so are patches. It is delivered
  automatically in the system since 6.2

  Only performer MR (releases) have static libraries. Using static libraries
  means using the MR, and never be perturbated by the eoe. It also
  means that an application linked in static will not be enhanced by
  any patches (ain't that static ?)

  There is ONLY ONE exception to the above statement. This is the patch 1392
  that is for the Performer dev environement.
  Performer made this exception to give access to pfASD for 2.0 users.
  ASD has been developped for 2.1 (IR only), but there are no
  technical problem to use that 100% software technique on any
  SGI.

  So, that's what you want to do:
  - install patch 1347 and patch 1392 on the SGI with the Performer
  dev env. It is required to have the dev env to install this patch.
  This patch is free IF you paid for 2.0 dev.It's the only
  exception, all other patches are 100% free.
  - install patch 1347 only on execution only machine.

  You'll find the libpfs static libs in the 1392 patch if you want to
  link staticaly.

  Please ask if you have any further question.

    _ / _ _
|_) _ ._ _ o /\ |_)|\ | /\ | || \
| \(/_| | || /--\| \| \|/--\|_||_/
                                           
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
            Submissions: info-performer++at++sgi.com
        Admin. requests: info-performer-request++at++sgi.com

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:54:46 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.