This chapter gets you started porting to Open Inventor 2.1. It steps you through the porting process, pointing to other relevant information as appropriate.
The process of porting to Open Inventor 2.1 is much simpler if your application has no custom classes derived from the Inventor classes. This chapter therefore discusses the process in two separate sections:
Compile your application under Inventor 2.1.
If you have compile or link problems, go to “Overview of Changes By Class Name” and from there to the more detailed description.
Fix all your problems in sequence and recompile, or recompile after each fix. The approach you take depends on your application and your personal preference.
When your application compiles and links without errors, run it and watch carefully whether there are changes to the appearance of your scenes. Because some defaults changed, things may not look exactly as they did before.
If you find problems, go to Chapter 3, “Scene Appearance Changes in Inventor 2.1.” The chapter provides a table that lets you access the API problem description based on the appearance problem description.
After the application compiles and runs satisfactorily, you are urged to also prepare it for the future by removing obsolete nodes, fields, and so on, that are supported for compatibility only.
In some cases, the old version of the API is supported in addition to the new version. This is done only to make the transition from 2.0 to 2.1 easier. To flush out cases where your code is still using the old version, compile your code with -DIV_STRICT as an option to cc.
Finally, optimize the application to really get the most out of Inventor 2.1 as follows:
Look at the other new features discussed in Chapter 4, “New Features,” and make sure you're taking advantage of the available enhancements and optimizations.
Look at the information in Chapter 6, “Optimizing Open Inventor Applications.” It has been updated for 2.1 from the booklet of the same name (which was not previously available online). Optimize your program using that information as appropriate.
Attempt to update your classes as appropriate before you compile the application for the first time. See Chapter 5, “Incompatible Extender API Changes,” for information that's useful when updating custom classes.
When you believe you've fixed most problems, go through the steps in “Porting Applications With No Custom Classes”.
If compiling or linking uncovers further problems with your custom classes, see also the include files in /usr/include/Inventor.