Re: Performer Debug Libraries

New Message Reply Date view Thread view Subject view Author view

From: Allan Schaffer (allan++at++sgi.com)
Date: 08/10/2000 18:32:07


On Aug 10, 1:58pm, Mark Acosta wrote:
> I'm trying to do some debugging with the Performer debug libraries
> and the ones I currently have seem to be quite old. I think they're original
> 2.2.0 Performer release libraries. They don't work for me at all. I need at
> least 2.2.2 debug libraries. What I want to know is, have there been later
> releases of the Performer development CD that have newer versions of the
> Debug libraries? If not, is there any other way to get newer versions of the
> libraries?

Very unfortunately there isn't, the way Performer 2.2 was packaged,
in combination with the forwards & backwards binary-compatibility
requirements for the IRIX 6.5 series, has made the distribution of
"dev" updates very difficult for the Performer 2.2 series.

As you've discovered, the updates to the runtime libraries
(performer_eoe) and perfly/etc (performer_demo) have been included in
the IRIX bundles for 6.5.x, but not the static or debug libraries, or
other parts of performer_dev such as updates to the sample source
code.

But giving this some thought, there's no technical reason why the
Debug DSOs alone couldn't be updated (as opposed to the static
libraries which have many reasons why not). However it wouldn't
happen until 6.5.10 at a very optimistic minimum or more likely
6.5.11, by which time 2.4 should already be released anyways. If
there's a huge pent-up demand for updated Debug DSO's that couldn't
just be served by the release of 2.4, I'd like to hear about it.

And some good news, the things that caused these distributability
problems are much improved in 2.4, so at least we can avoid a repeat
of all this in the next series.

Allan

-- 
Allan Schaffer                                            allan++at++sgi.com
Silicon Graphics                           http://reality.sgi.com/allan


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Thu Aug 10 2000 - 18:32:11 PDT

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