[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PVWave, IRIX and o32/n32 objects
- Subject: Re: PVWave, IRIX and o32/n32 objects
- From: rmlongfield(at)my-deja.com
- Date: Thu, 14 Oct 1999 08:07:11 GMT
- Newsgroups: comp.lang.idl-pvwave
- Organization: Deja.com - Before you buy.
- References: <01bf118d$d36e37e0$160b9482@basit47307033>
- Xref: news.doit.wisc.edu comp.lang.idl-pvwave:16844
In article <01bf118d$d36e37e0$160b9482@basit47307033>,
"Adrian Clark" <email@example.com> wrote:
> Dear All,
> I am trying to compile a number of applications linking pvwave
> objects/shared objects with objects from other products.
> The difficulty I am encountering is that the PVWave objects are in o32
> format while the objects from the other products are all in n32
> is impossible to combine these incompatible formats, and the only
> way round would be if I could obtain PVWave n32 objects.
> The last thing I heard was that VNI had no intention of releasing
> objects in n32 format. Does anybody know if this is still the case?
> n32 objects available under the recently released version 7.0 of
> Thanks for any help.
I use IDL on a Silicon Graphics and had similar trouble recently
when the operating system was upgraded to 6.2 (which meant n32). I had
to re-compile my C programs with a flag for -o32. Then I was able to
use them in IDL. Maybe this will work for you also.
I heard that the standard for SG is going to be n32
in the future so PVWAVE will eventually be forced to comply with it.
IDL also isn't ready for it, as far as I know.
There was some discussion on this group about this a while ago (Try
doing a search for n32 and o32). This included someone who understood
the problem more than I.
Sent via Deja.com http://www.deja.com/
Before you buy.