porting guide for performer 2.3?

From: George Koharchik (georgek++at++skopen.rsc.raytheon.com)
Date: 01/26/2000 05:25:30

• Next message: Luc Renambot: "Textures + Performer + Cave"
• Previous message: Bo Staahle: "Getting input for a GUI in Performer C++"

Hi Folks,

   I'm porting an Irix/Performer 2.2 application to Linux/Performer 2.3. The
first time I call pfFrame it croaks with this stack trace:

#0 0x401dd487 in pfPipeWindow::pf_updateOpenStatus () from /usr/lib/libpf_ogl.so
#1 0x40207150 in appCullDraw () from /usr/lib/libpf_ogl.so
#2 0x40207f90 in pfFrame () from /usr/lib/libpf_ogl.so
#3 0x8051850 in main (argc=20, argv=0xbfffefc4) at ../main.c:209

   Since perfly works I'm assuming that there's something different about what
this application does that what the new perfly does. (Has anyone seen this
behavior before? Any clues where I should concentrate?)

   Since there are probably other things I should fix beyond what's causing this,
is there any documentation on the differences between Performer 2.2 and Performer
2.3, or any porting guide? (I looked at the FAQ and followed the pointers to the
online manuals-- if the answer is there I missed it.)

Thanks!

g-koharchik++at++raytheon.com

• Next message: Luc Renambot: "Textures + Performer + Cave"
• Previous message: Bo Staahle: "Getting input for a GUI in Performer C++"

This archive was generated by hypermail 2b29 : Wed Jan 26 2000 - 05:20:58 PST

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