3.1 From ST-Developer v11
You should not require any additional source code changes to software previously working with ST-Developer v11. Since the binary layout of the libraries may have changed, you must completely recompile (i.e. remove all object files) any applications you have developed.
If your application used the EXPRESS "binary" type, you may need to update some source code, since the ROSE API has changed, however, this is unlikely since none of the STEP Application Protocols have ever used this feature.
To begin using new features, such as the Part28 XML reader and writer, or the ROSE logging window, follow the instructions given in the previous chapter.
3.2 From ST-Developer v10
Since additional methods have been added to the rose library, you must completely recompile (i.e. remove all object files) any applications you have developed.
If you are using either the RoseP21Parser::add_schema_fn or the RoseP21Writer::schema_name_fn hook functions, you will need to change the declarations of your functions to accommodate the new arguments. Your code will not compile if you use the old prototypes, so you will know immediately if this affects you.
If you are including RoseP21Lex.h , RoseP21Parser.h or RoseP21Writer.h , you no longer need to do so. These are now brought in automatically by rose.h .
3.3 From ST-Developer v9
In addition to the changes described above, the stepi18n library has been merged into the rose library, so any references to it should be removed from your makefiles.
All runtime support files required by ST-Developer applications are now in the redistributable ST-Runtime package. The contents of the system_db directory have been either moved to ST-Runtime or to the lib subdirectory (for items only used by ST-Developer).
On Windows, ST-Runtime is provided as a stand-alone Windows Installer (msi) and as an installer merge module. You can merge ST-Runtime into your installer or just ship the ST-Runtime installer along with your application, and let the user install the two independently. On UNIX and MacOS, ST-Runtime is provided as zip file.
For more information, see Packaging Applications for Distribution in the Rose Library Reference Manual.
The sortnames files ( *.nam ) now use the same syntax as the AP documents (longname first, then shortname). If you have any of your own *.nam files, you should update them to the new syntax. Shortname files for all of the STEP APs are already present in ST-Runtime.
3.4 From ST-Developer v8 and earlier
You should not require any additional API changes with ST-Developer v8 or earlier. If you are using any compiled schemas files that are not already present in the ST-Runtime package, you must regenerate them with the EXPRESS compiler.
In ST-Developer v7 and earlier, the C++ classes for aggregates were generated in separate files, but now they are kept with their base type. You may need to update your makefiles or VC projects for the new set of source files.