InterOp:Release Notes
From DocR21
This service pack is a collection of new features and updates that fix issues reported against the InterOp R21 release and incorporates all of the InterOp R21 content.
Important: The service pack is stand alone and needs to be installed into a directory that does NOT contain prior releases.
This service pack is not a required upgrade; however, if you are currently running InterOp R21, we encourage you to download this service pack to ensure that you are running the most current, up-to-date version of InterOp.
Note: This InterOp service pack should be used with the same service pack level of ACIS.
Contents |
Release Notes R21 SP1
| IMPORTANT |
|---|
| This Service Pack is standalone and must be installed into a directory that does NOT contain prior releases. |
Package and Build Changes
Visual Studio 2010
- R21 SP1 supports ACIS and InterOp on the Visual Studio 2010 32-bit development environment.
Windows 7
- InterOp R21 SP1 now supports CATIA V5 Reader and Writer on the Windows 7 x64 environment.
Enhancements and Functionality Changes
CATIA V5 Reader Component
- Support for Windows 7 x64 bit
- CATIA V5 Reader is supported on the Windows 7 x64-bit platform.
CATIA V5 Writer Component
- Support for Windows 7 x64 bit
- CATIA V5 Writer is supported on the Windows 7 x64-bit platform.
Inventor Reader Component
- Support for Inventor Version 2011
- The Inventor Reader component supports translation of part and assemblies for Inventor 2011 files. Refer to Inventor Reader for more details.
Unigraphics Manufacturing Option
- Support for NX7 PMI
- The Unigraphics Reader component supports translation of PMI for NX7 version files. Refer to Unigraphics Manufacturing Information for more details.
Pro/E Manufacturing Option
- Support for Wildfire 5 PMI
- The Pro/E Reader component supports translation of PMI for Pro/E Wildfire 5 version files. Refer to Pro/E Manufacturing Information for more details.
- Roughness Mapping
- The Pro/E roughness symbol has been enhanced to support isosurftext.sym and surftexture.sym symbols from Wildfire 5.0 onwards. The corresponding fields mapping is described in detail at Roughness Mapping.
Resolved Issues
For any issues you have submitted, log into the Downloads area at the Spatial Web site to check their status.
Platform Support
R21 GA Release Date: May 2010
| Compiler Build | Tested OS | Processor |
|---|---|---|
| Microsoft Windows | ||
|
Microsoft Visual C++ 2005 32-bit |
Windows XP Professional 32-bit SP3 | x86-64 |
| Red Hat Enterprise Linux1 | ||
| GNU C++ gcc 4.1.2 32-bit GNU C++ gcc 4.1.2 64-bit |
Red Hat Enterprise Linux Version 4.0 Update 7 | x86-64 |
| IBM AIX | ||
| VisualAge C++ Professional Version 8.0 32-bit VisualAge C++ Professional Version 8.0 64-bit | AIX Version 6.1 (TL02) | RS/6000 |
| Apple Macintosh | ||
| gcc 4.0.1 compiler (included with XCode 2.3) 32-bit | OS X 10.4.7 | Intel-based Macintosh |
1 Linux is built on RHEL4.0 Update 7 and links to glibc 2.3.4-2, thus the minimum OS for runtime is RHEL4.0.
Note: Spatial has been informed that when a customer application links against and initializes PHL V5, the Microsoft debug runtime reports leaks after their application exits. Refer to Understanding False Memory Leaks Reported in ACIS-based MFC Applications for more details.
End of Life Notifications
R20 was the last version for ACIS/InterOp binaries on HP-UX and Solaris platforms. Starting with R21, ACIS/InterOp binaries are not provided for Hewlett-Packard HP-UX nor for SUN Solaris operating systems. Contact Spatial Support for any additional information.
Downloading the Service Pack
To download this service pack:
- Go to the Spatial Downloads Center.
- Log in with your Customer ID and Password at this screen.
- At the next screen, select the service pack you want to download from the drop-down list box.
- Download the 3D InterOp Products service pack applicable to your platform and operating system.
Installing the Service Pack
The following sections explain the installation procedure for supported
IMPORTANT Service Packs are standalone and must be installed into a directory that does NOT contain prior releases.
Note: The Spatial installation software does not need to be run separately for each Spatial product or supported platform. You may extract packages for both the 3D Modeling and Visualization Product Suite and the 3D InterOp Product Suite across multiple platforms into one directory and run the installer once. However, you must not extract UNIX and Windows packages into the same directory.
Installing on Windows
To install the service pack on Windows:
- Download the product ZIP file.
- Extract the product ZIP file by double-clicking the file and specifying the desired installation directory.
- Double-click the setup.exe file in the location specified in Step 2.
- To install multiple products simultaneously, extract the install files to a single location and double-click setup.exe.
- At the Welcome screen, click Next to continue to the License Agreement screen. Select Yes to accept the license terms.
- The next screen prompts you for the destination folder. Select an empty folder to contain your InterOp installation. The installation then occurs in the selected location.
Installing on UNIX and Macintosh
To install the service pack on UNIX or Macintosh:
- Download the product TAR file.
- Extract the product TAR file to the desired location.
- Run the installation program iop_install.
- The first screen displayed contains information for navigating the installation program. After reading this screen, press <Enter> to continue the installation program.
- The next screen displays the license agreement. If you accept these terms and conditions, enter Y and then press <Enter>. If you do not accept these terms and choose N, the program quits the installation process.
- The last screen prompts you to verify the InterOp installation directory, <install_dir>, where the product is to be installed. Enter Y to confirm, and the installation program completes the installation process.
Platform Support
The following table illustrates supported platforms for the 3D InterOp products.
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Note: CSDK requires other components for its use. Supported platforms are limited by its components.
Installation Notes
The following sections explain the installation procedure for supported platforms and important post-installation information:
Note: The Spatial installation software does not need to be run separately for each Spatial product or supported platform. You may extract packages for both the 3D Modeling and Visualization Product Suite and the 3D InterOp Product Suite across multiple platforms into one directory and run the installer once. However, you must not extract UNIX and Windows packages into the same directory.
Digital Signatures
Spatial products on Windows Operating System with Microsoft Visual C++ 2005 compiler are now digitally signed for identification purposes. Digital signatures for Spatial products have been issued by VeriSign and recipients can use this to authenticate the identity of Spatial products.
Installing on Windows
- Download the product ZIP file from http://www.spatial.com/downloads.
- Extract the product ZIP file by double-clicking the file and specifying the desired installation directory.
- Double-click the setup.exe file in the location specified in step 2.
- At the Welcome screen, click Next to continue to the License Agreement screen. Select Yes to accept the license terms.
- The next screen prompts you for the destination folder. Select an empty folder to contain your InterOp installation. The installation then occurs in the selected location.
Important Runtime Installation Instructions for Windows
Note: The following instructions apply ONLY to customers who meet one or more of the following conditions:
- Build their application using the Microsoft Visual Studio .NET 2005 (SP1) compiler
- Use the CATIA V5 component with any Windows compiler
After you install your Spatial products, you must install the executable (for 32-bit or 64-bit) provided with your Spatial products installation package.
During the Spatial products installation process, two executable files are placed in a folder called redist, located in the Spatial products installation directory; for example:
<install_dir>\redist
.
.
.
VC8\vcredist_x86.exe (32-bit)
VC8\vcredist_x64.exe (64-bit)
where <install_dir> is the confirmed location of your Spatial products installation directory.
Note: The following instructions apply ONLY to customers who meet one or more of the following conditions:
- Build their application using the Microsoft Visual Studio .NET 2008 compiler
- Use any Parasolid component.
After you install your Spatial products, you must install the executable (for 32-bit or 64-bit) provided with your Spatial products installation package.
During the Spatial products installation process, two executable files are placed in a folder called redist, located in the Spatial products installation directory; for example:
<install_dir>\redist
.
.
.
VC9\vcredist_x86.exe (32-bit)
where <install_dir> is the confirmed location of your Spatial products installation directory.
Installing on UNIX and Macintosh
- Download the product TAR file from http://www.spatial.com/downloads.
- Extract the product TAR file to the desired location.
- Run the installation program iop_install.
- At the first screen, review the details about navigating the installation program. Press <Enter> to continue with the installation process.
- The License Agreement appears on the next screen. If you accept these terms and conditions, select Y and press <Enter>; otherwise, select N, and the program quits the installation process.
- The last screen prompts you to verify the installation directory, <install_dir>, where the product is to be installed. All products will be installed into this directory. After entering Y to confirm the location of the installation directory, the installation program completes the installation process.
Understanding False Memory Leaks Reported in ACIS-based MFC Applications
False memory leaks are reports of leaks by memory management systems that can be proven to be erroneous. In this case Spatial specifically refers to the leak reports generated by the Microsoft debug CRT when an ACIS-based MFC application exits.
Faulty leak reports are generated when the runtime library that was loaded last exits, not when the runtime library that was loaded first exits. In other words, the faulty leaks are reported when the first runtime library exits, not when the last one exits. (This is a bug that has been acknowledged by Microsoft.) Moreover, other libraries may be unloaded after the first runtime library exits. These other libraries may free memory when they unload, which is the case with ACIS libraries. These deallocations can occur after the leak report has already been generated, in which case they are incorrectly reported as leaks.
No faulty leaks are reported when all runtime libraries are loaded before other libraries during application startup. This desirable behavior can be achieved by managing link order and by managing the types of run-times used by the application.
Libraries specified as additional dependencies in the project settings are loaded in the order specified before all other libraries. (This is referred to as "explicit linkage".) Adding the appropriate MFC runtime library to the beginning of the link dependencies should remove erroneous leaks in most cases. Additionally, you can load all libraries with the use of pragmas. This is the suggested way to link ACIS libraries into your application. (This is referred to as "implicit linkage".) From our experience, applications that link libraries implicitly are less likely to encounter faulty leak reports. Note that pragmas added to source code will, therefore, require project rebuilds.
Faulty leak reports can also occur when mixed versions of runtime libraries are loaded because of dependencies from other libraries. For example, a typical MFC application may use MFC80D.DLL and have dependencies on other libraries that use MFC80UD.DLL. The latter library may be loaded after other libraries have been loaded, specifically after ACIS libraries are loaded. This is a scenario for faulty leak reports since libraries are unloaded in reverse load order. This cannot be solved with explicit linkage because of link errors (such as multiply defined symbols) and mixed runtime issues. The best solution is to manage the types of run-times used by the application by using the same ones whenever possible.
Licensing Information
Note: Application Licensing and Registration are supported on Windows operating systems only.
Use of this Spatial software and the associated documentation is governed by the license agreement between the parties. If you do not have such a written license agreement for this software, do not use this software or documentation. If you do not have a valid license, contact your sales representative or productsales_spatial@3ds.com to purchase a license.
Any use of this Spatial software or documentation without a valid license is illegal and is strictly prohibited.
========================================================================= == NOTICE file corresponding to section 4(d) of the Apache License == == Version 2.0, in this case for the Apache Xerces distribution. == ========================================================================= This product includes software developed by The Apache Software Foundation (http://www.apache.org/). Portions of this software were originally based on the following: - software copyright (c) 1999, IBM Corporation., http://www.ibm.com. See the text file XERCES_LICENSE for the complete Apache License, Version 2.0.
© 2010 Spatial Corporation, a Dassault Systèmes S.A. company. All rights reserved.
ACIS and SAT are registered trademarks of Spatial Corporation. All other names and products are trademarks of their respective owners.
