How can I install labVIEW to another path?

Question

Greetings,
I am trying to install labVIEW 8.2.1 for our R.H. Linux labs campus wide.
I am able to install the software onto a single machine.
And in the installation script it outputs:
NOTE: LabVIEW will install by default in /usr/local/natinst/LabVIEW-8.2,
or in the natinst/LabVIEW-8.2 subdirectory if you specify an alternate location.
But it doesn't say how to specify an alternate location.
I need to install labVIEW into:
/afs/bp.ncsu.edu/dist/labview821/
which is a network filesystem we have here. Most of our commercial apps are installed this way. Your app is the first
commercial app I've had to install that uses RPM instead of a tarball.
I can't install the RPMs on every machine on campus because we only have root access
to a small subset of these machines. In the past we've been able to install apps into
AFS space and have anyone on campus be able to access the application.
(By adding each apps bin/ in the network directory to the search $PATH)
So I want to put labview in
/afs/bp.ncsu.edu/dist/labview821/bin/labview
instead of
/usr/local/bin/labview
Will this be possible with labview? Or will labview only work if installed on a local hard disk drive?
Thanks,

Answer 1

Greetings,
We have a site license for the college of engineering.
I was never prompted for any licensing info for the Linux version. (Durring install or running the labview
app post install on my test machine) I know some of our employees set up a LabVIEW license server. I know its IP address...
(152.1.68.81)
How do we specify that the Linux installed software should use that? Is it done via an environmental variable? Or does only
the windows version of the software use the license server? The Linux version appeard to have no copy protection? I never was prompted for
serial numbers or anything...
I also tried using the
 ./INSTALL --no-rpm
command line option to install the app but it failed to give me a way to specify a new install location. In fact, it seemed
to still use rpm for its install.
I looked at the readme.html docs on the install CD and it refered to a pdf that you can only read
after installing the program. (To learn how to install the software you first have to install the software)
This document was called: "LabVIEW release notes."
ON page 8 of "LabVIEW release notes" it says:
LINUX:
Complete the following steps to install LabVIEW for Linux.
1. Log into the system as root.
2. Insert the LabVIEW 8.2 installation CD. Uswe mount /mnt/cdrom to
   mount the CD. On some systems, the CD mounts automatically.
3. To change the current directoty to the mounted CD, enter the
   following command:
   cd /mnt/cdrom
4. To run the installation script, enter the following command:
sh ./INSTALL
5. (Optional) Install LabVIEW add-ons. Refer to the Installing LabVIEW
   Add-Ons section of this document for more information.
6. (Optional) Install and configure National Instruments hardware. Refer
   to the INstalling and Configuring Hardware section of this document for
   more information.
7. Refer to the Where to go from here section of this document for more
   informationabout getting started with and using labVIEW.
The INSTALL script prompts you to enter the directory where you want to
install LabVIEW, which is typically /usr/local.
But the install scipt never prompts you like it says it would in the release notes.
Maybe it did that in version 8.2 and doesn't in 8.2.1? (And they just forgot to update
the documentation or its just wrong?)
If rpm is the only supported option for installing the Linux version and if it can't
be relocated than we can tell the departments paying for the site license that
they will have to run the program only on our 200 or so Linux lab machines. Not their
Linux machines hooked up to whatever instruments they plan to interface with this
software.
But before I tell them that I'd like to hear someone tell me that what I'm trying to do
is impossible. (Install LabVIEW on a network directory) I  am having a hard time
finding any further installation documentation for the Linux version on the ni website.
And the documentation I've read from within the program in the form of the Release Notes
seems to have errors.
Many thanks for any ideas anyone has.