I'm writing this tutorial so that people can benefit from my experiences with setting up WF 3.0 on a HP xw4600 running Ubuntu 8.10. I work as a mechanical design engineer and CAD administrator, and I have been working on getting WF 3.0 running smoothly on Ubuntu for a few days now. After alot of Googling for answers and figuring out things on my own, I have finally come up with a solution that should work for everyone.
Getting Started
Before you can install Pro/E from CD or from the packages downloaded from PTC, you need to prep a few things on your system. First of all, you need to make sure that your graphics card is setup properly and that OpenGL is working. This is beyond the scope of this tutorial, so please check out the following links for more info:
Using Nvidia Binary Drivers
Using ATI Binary Drivers
After you have OpenGL up and running, you need to install a few package so that you can run the Pro/E setup program. On my system I needed to install csh, libmotif3, libstdc++5, and portmap:
Now you should be able to run the installer without any problems.Code:sudo apt-get install csh libmotif3 libstdc++5 portmap
Running the Setup
You have two options for installing Pro/E: CD or online installer. it doesn't matter which one you use, just find the setup script and run it:
After this, the Pro/E setup program should launch and will run you through the installation steps. Just remember that you will need the license server information for your company, so have it handy when the program asks for it. If you are unsure of your license server or the license server triad, you can look at the launch scripts on another workstation to determine this information. Just open one of the following files in a text editor and search for "@7788".Code:cd /path/to/proe ./setup
On Windows:
C:\path\to\ProE\bin\proe.psf
On Unix/Linux:
/path/to/ProE/bin/proe1
Keep in mind that alot of companies use custom Pro/E lanuch scripts that may be under a different name such as proewf3_b300 (for release 3.0 build 300). In this case you would need to look for the following files:
On Windows:
C:\path\to\ProE\bin\proewf3_b300.psf
On Unix/Linux:
/path/to/ProE/bin/proewf3_b300
Library Fix
Now you should have Pro/E installed, but if you attempt to run it you will get a bunch of "Locking assertion failed" error messages on the command line. This is the one thing that was keeping me from getting WF 3.0 working until I found this bug report:
https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/185311
If you dig down through that bug, there is a post describing how to install a special version of libx11 that will prevent the Locking assertion errors and will allow Pro/E to run without any issues. The best part is that they wrote a script to automate the whole process and install the libraries outside of the package manager so that it does not affect Compiz or other applications.
You can download the script here:
http://launchpadlibrarian.net/16474477/install_libx11-noxcb_in_opt.sh
After you download the script, simply run it as follows (there is no need to run with sudo because it will do this for you):
Once the script has completed, you will have a new copy of libx11 installed in /opt/LIBx11-noxcb that can be used to launch Pro/E, Matlab, Mathematica, and several other applications that give the "Locking assertion failed" error message.Code:sh install_libx11-noxcb_in_opt.sh
Now on to the custom launch script
Custom Launch Script
Below is the custom launch script that I wrote to launch Pro/E on my workstation. The script will test to see if your working directory exits...if it doesn't it will create it for you. After this it will run a subroutine that will change to your working directory, set the LANG environment variable to "C", and disable compiz before launching Pro/E with the special libx11 libraries. When Pro/E is closed, the script will relaunch Compiz automatically.
To use my script, simply copy the text into a file and call it whatever you want (I called my proe_starter), then make the script executable and launch it:Code:#!/bin/bash WORKING_DIR=$HOME/working PROE_PATH=/usr/local/ptc/proeWildfire3.0/bin PROE_PID='/sbin/pidof proe1' # This will depend on your custom Pro/E launchers function launch_proe { cd $WORKING_DIR export LANG=C #Uncomment the line below if you are using Compiz metacity --replace & LD_LIBRARY_PATH=/opt/LIBx11-noxcb/lib:$LD_LIBRARY_PATH $PROE_PATH/proe & while [ -n "$PROE_PID" ]; do sleep 3 done if [ -z "$PROE_PID" ]; then #Uncomment the line below if you are using Compiz compiz --replace & fi } if [ -d $WORKING_DIR ]; then launch_proe else mkdir $WORKING_DIR launch_proe fi
Once you are sure that the proe_starter script is function properly, you can copy it to local bin directory so that it will be in your path:Code:chmod +x proe_starter ./proe_starter
Create a Desktop IconCode:sudo chown root:root proe_starter sudo cp proe_starter /usr/local/bin/
You can create a desktop icon by right clicking on the desktop and selecting "Create Launcher". Just enter "proe_starter" in the Command field and give it a name and description. If you want to use the default Pro/E icons, they are located in "/path/to/proe/install/nt".
That pretty much wraps up this tutorial. If you have questions feel free to ask them.
Adv Reply
Bookmarks