LabVIEW Idea Exchange

This is a real pain for me and I think this should not be considered expected behaviour of LabVIEW. But since I have been told it is I am posting this as an idea for the Idea Exchange. Let me explain:

Imagine you build an application which makes use of a large number of files (images, text files, etc) and you would like to include these in the build specification of your application. Imagine you want the files to go to various different custom locations on the computer (some in documents, some in a folder on your desktop, some in another location... the list goes on). I have such an application and it includes about 25 different folder locations I had to insert manually as destinations for the files. This is fine, I expect to do such a thing and it was simple enough (although time consuming).

Now comes the pain:

I now want to build an installer which uses this EXE build spec. If I use the EXE build spec in my installer build spec the result is to place all of these dependent files in the same folder as the installed executable, not the locations I defined in the EXE build! This means I have had to go back and create a new EXE build spec which contains no dependent files (so that it compiles without placing files everywhere) and then back to the installer to use that EXE build and then define all the location yet again! This has been super time consuming.

Upon discussion this is apparently expected behaviour as installer build specs are seperate to the exe build specs....... except am I not right in thinking the installer build spec relies on you having an EXE build spec???

So currently the situation is this: I have to have to have an EXE build spec containing the custom destinations which I can build and use to test my application. I then also have to have an EXE build containing no custom locations which when built is useless since it is missing dependent files, but purely there to then create the installer build specification which I have to define all custom locations in again.

My proposal is simple: When you create an installer that uses an EXE build spec with custom locations for files it should replicate those locations in the instaler. Simples!

Note: If this was super confusing download the attached project and see for yourself. (LabVIEW 2013)

Hi,

I have some suggestions for the Uninstall.sh script that comes with the OS X installer:

1) Copy it on installation into the main LabView application folder so that users don't need to find (or redownload, in my case) the original installer just to remove a seven-day evaluation copy (grrrr....).

2) Lines 85-88 need modification. They read:

[from the file Uninstall.sh]

echo "pid=\$( ps -axww | grep nisvcloc | grep -v grep | awk '{print \$2}')"
echo "if [ \$pid ]; then"
echo "sudo kill -6 $pid"
echo "fi"

When I ran the script, the $pid was omitted in the screen output:

[from the screen output of Uninstall.sh]

pid=$( ps -axww | grep nisvcloc | grep -v grep | awk '{print $2}')

if [ $pid ]; then

sudo kill -6 

fi

It looks like the "$" should be changed to "\$' on line 87:

[Corrected line 87 for the file Uninstall.sh]

echo "sudo kill -6 \$pid"

3) For my OS, there is an error in both the documentation lines 85-88 and the associated code on lines 189-193: the process ID is associated with the first variable of the grep expression, not the second. The second variable returns the TTY for the process, which for nisvcloc is given as "??".

[from the file Uninstall.sh]

echo "Stopping the NI Service Locator..."
pid=$( ps -axww | grep nisvcloc | grep -v grep | awk '{print $2}')
if [ $pid ]; then
sudo kill -6 $pid
fi

[from the screen output of Uninstall.sh]

Stopping the NI Service Locator...

kill: illegal process id: ??

[Corrected line 190 for the file Uninstall.sh]

pid=$( ps -axww | grep nisvcloc | grep -v grep | awk '{print $1}')

[Corrected line 85 for the file Uninstall.sh]

echo "pid=\$( ps -axww | grep nisvcloc | grep -v grep | awk '{print \$1}')"