This section provides information that may be helpful to users who need to access results in an output database from an existing application. Most users should find that the ABAQUS/Make procedure is sufficient for their postprocessing needs. Since linking and executing with dynamically linked runtime libraries is highly system dependent, the information in this section is intended for users who have an advanced working knowledge of compilation and linking with runtime libraries. It is important to ensure that the compiler used to compile and link the existing application is consistent with the compilers used to generate the ABAQUS release. The ABAQUS web site www.abaqus.com lists the name and version of the compiler used for the ABAQUS release on each supported platform. You can find the information under the system requirements described on the “Technical Support” pages.
The following topics are covered in this section:
Before any calls are made to the C++ interface, the following call must be made to initialize the interface:
odb_initializeAPI();This call is generated automatically when the ABAQUS/Make procedure is run but must be included in any application that is not compiled and linked using the ABAQUS/Make procedure. After all calls to the C++ interface have been completed, the interface may be deactivated by including a call to
odb_finalizeAPI();If the finalization call is not made explicitly, the finalize routine will be called automatically when the application exits.
The libraries necessary to link applications that access the C++ interface are located in the following directories:
UNIX
abaqus_dir/cae/exec/lbr
Windows
abaqus_dir\cae\exec\lbr
During linking, the ABQodb library and several other libraries shipped with the ABAQUS release are used to resolve all the functions available in the interface to the output database. The command used by ABAQUS to link runtime libraries (for example, for user subroutines) is available through the ABAQUS environment variable link_sl. Additional information about linking with the ABAQUS libraries, including the names of all libraries which must be specified as part of the link command, may be obtained by running the ABAQUS/Make procedure in verbose mode with a verbosity level of 3.
The runtime libraries required to execute a program that accesses the C++ interface are located in the following directories:
UNIX
abaqus_dir/cae/exec/lbr
Windows
abaqus_dir\cae\exec\lbr
The correct path to the ABAQUS runtime libraries must be specified prior to starting the user application. The runtime library path is typically set using the system environment variable LD_LIBRARY_PATH, but the method used to set the path may vary depending on your operating system configuration. The ABQodb library and several utility libraries resolve all the functions available in the interface to the output database, as described in “Link library location,” Section 9.7.2. At runtime these libraries depend on many of the underlying ABAQUS libraries. As a result, if you do not define the correct runtime library path, your application will not run.
The header files required to compile a program that accesses the C++ interface are located in the following directories:
UNIX
abaqus_dir/cae/include
Windows
abaqus_dir\cae\include
Only odb_API.h must be included to access the C++ interface, but the path to the header files must be provided during compilation.