To enable Parasolid support, the sandbox must be compiled with the USING_PARASOLID preprocessor flag, and must be linked to hps_sprk_parasolid.lib.
The pskernel.dll must be located in your system path. Or, for debugging, in the Configuration Properties, under Debugging in the Environment field, set the PATH variable to PATH=<PARASOLID_INSTALL_DIR>\base64_vXXX\dll\<LocalDebuggerEnvironment>
Also in the Configuration Properties, under Additional Include Directories for the C/C++ section, add the location of your Parasolid header files, for example:
In the Linker section of Configuration Properties, in the Additional Library Directories field, set the location of the Parasolid DLLs. For example:
The WPF sandbox requires that you add USING_PARASOLID to the list of "Conditional Compilation Symbols" in its project file, and you must add a reference to cs_sprk_parasolid.
Additionally, some Parasolid files require schema files for import. For those files, it is necessary to set the schema directory using either HPS::World::SetParasolidSchemaDirectory or the P_SCHEMA environment variable. Alternatively, you can place the schema subdirectory in the same folder as the executable.
To use the Exchange-Parasolid sprocket, follow the instructions above for Exchange and Parasolid. In addition, your application must be linked to hps_sprk_exchange_parasolid.lib.
Please note, you must be a RealDWG licensee in order to use the RealDWG interface. RealDWG is only available on Windows platforms.
To use RealDWG with the WPF sandbox, you must add USING_DWG to the list of "Conditional Compilation Symbols" in the WPF Visual Studio project file. You must also add a Reference in the Visual Studio project to hps_cs_sprk_dwg.dll. In the properties for the Reference to hps_cs_sprk_dwg.dll, set the Copy Local property to False.
To enable RealDWG support in the MFC Sandbox, the project must be compiled with the USING_DWG preprocessor flag, and must be linked to hps_sprk_dwg.lib.
For more information on using RealDWG, please see the Programming Guide.
Notes on Qt Sandbox
For users of the Qt Sandbox, please note that we do not ship project build files other than the canonical Qt .pro format. Generation of Visual Studio projects, Xcode projects, and makefiles can be done through the Qt package's utilities.
Mac users: Starting with Catalina, macOS will now warn if dynamic libraries are loaded outside system directories or app bundles. If you see a message from Qt Creator when deploying the Sandbox saying the HPS libraries appear to be "malware" or "may be corrupt" - it is because Qt Creator is trying to load the libraries stored outside the bundle. This can be resolved by going to the "Project" tab, navigating to the "Run" configuration, expanding the "Run Environment" section and modifying the <span class='code">DYLD_LIBRARY_PATH entry so that it doesn't include an entry for the HPS package's bin/mac directory.