Re: C++, Shadows, and Shared Libraries

New Message Reply Date view Thread view Subject view Author view

From: Allan Schaffer (allan++at++sgi.com)
Date: 01/11/2000 11:38:47


On Jan 11, 5:45pm, Christian Skluzacek wrote:
> When using the pfLightSource shadow features, I've found that they only
> work when linking with the *static* Performer libraries (by using
> -L/usr/lib32/Performer/Static on the link ine). Is there a reason for
> this? and is there any way of using shared libraries with shadowing? My
> shadowing code is in a (C++) library which when linked in statically,
> forces all my other libraries to be linked in statically (which is
> causing other problems because of template instantiations, etc). Being
> able to use the shared library will help me out in the short term but
> I know I have to do some more configuration management to get all my
> libraries straightened out.

[What OS version are you running? 'uname -R']

Multi-part handwaving answer:

1. The static Performer libraries are version 2.2; (2.2.0)

2. I believe that the multipass-lighting features (such as shadows)
    had bugs introduced around Performer 2.2.2 and have been steadily
    rearchitected since then, currently version 2.2.6.

    2a. More things are fixed for the version which will ship with
         IRIX 6.5.7.

So if you're running 6.5.1 to 6.5.4 I bet the reason why the static
libraries work but DSOs don't is because the DSO versions you have
contain regressions in the shadow code. As much of that has been
redone you might try upgrading to 6.5.6 which contains the most
up-to-date DSOs -- 6.5.6 is available for web download from
http://support.sgi.com/ or on CD.

If shadows in 6.5.6 still have problem please let us know more..

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 : Tue Jan 11 2000 - 11:38:53 PST

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