How to set-up a Parasolid environment to use the TranslateToPkParts sample on Linux

This guide describes all the required steps to quickly use Parasolid within HOOPS Exchange by setting up the TranslateToPkParts sample available with every package:

  1. First of all, download any HOOPS Exchange Linux package on our developer zone.
  2. Replace the “include\hoops_license.h” license file with one you can generate here.
  3. Before compiling, it’s required to export the PARASOLID_INSTALL_DIR environment variable.
    The command to execute (be sure to complete it with your Parasolid installation folder first) can be found in the Makefile of the TranslateToPkParts sample (but don’t uncomment this line since it has to be run before launching CMake, otherwise it won’t work).
  4. After having successfully compiled (by running the “make“ command), it’s still needed to update the LD_LIBRARY_PATH as follows: “export LD_LIBRARY_PATH=/path_to_parasolid_folder/shared_object:…/…/…/…/bin/linux64:$LD_LIBRARY_PATH” (Notice the :$LD_LIBRARY_PATH repetition here to not overwrite any other library paths you may have previously defined).
    If this is not working, then try to remove any possible space in your paths.
  5. The last thing to do is to set up the P_SCHEMA environment variable by running the following command “export P_SCHEMA=/path_to_parasolid_folder/schema”. If you forget this one, you’ll still be able to generate the log saying that it cannot find the Parasolid schema.

For avoiding redoing steps 5 to 7 each time you close your shell, it’s possible to add all those commands at the end of the .bashrc file (which is located inside your user folder).

To check if any dependency is missing, it may be helpful to use the ldd command on the corresponding executable file (it’s also possible to use strace for dynamic ones).

On virtual environments, be careful about the symlink, which could be broken if the package is extracted and transferred from Windows.