Run software without Labview

[papigo]

I have generated a software from labview. It runs fine on my PC with labview installed. Now I need to run this software on anonther PC without labview.I generate installation package and try to run it. In my application，I read and write some parameters in ini files，using relative path which is splitted once in test environment and twice in running environment. The ini files are also included when I generate installation package.The software stops when it tries to read parameters.I guess it is caused by the file path. Only a guess. Can anyone help？

[Yamaeda]

Assuming your installer also installs the LV Runtime it shouldn't be that, even though it's a quite common problem.

Have you tried the .exe on your computer? I'd assume you'll get the same problem there.

/Y

[GerdW · Accepted solution]

Hi papigo,

The software stops when it tries to read parameters.I guess it is caused by the file path. Only a guess. Can anyone help？

You can help yourself once you include some error logging in your VI/exe: have it log (or just display in a dialog) which path it tries to read those files!

using relative path which is splitted once in test environment and twice in running environment.

Why do you need to do that for a relative path?

Using the AppDir constant might help, too…

[papigo]

yes.The same problem. Application runs ok. Application install package failed. Any idea？

[Yamaeda]

Having it fail on your computer is a good thing, that makes bug searching easier. As Gerd wrote, have the program Show the path it's looking for, e.g. through a One button dialog and double check that the path is correct and that the file is actually there. That's usually where it fails, either in the path building or missing to include the file in the installer.

/Y

[altenbach]

If you use paths relative to the program, you need to make sure to read all this.

---

@papigo wrote:
The software stops when it tries to read parameters.I guess it is caused by the file path. Only a guess. Can anyone help？

---

I am not even sure what "stops" means (Stalls? Stops running? error popup? Becomes unresponsive? etc.) In any case, ensure that you do proper error handling and switch behavior according to error conditions. The code needs to keep running, but must inform the user about a problem in some way.

[JÞB]

---

@altenbach wrote:

If you use paths relative to the program, you need to make sure to read all this.

---

@papigo wrote:
The software stops when it tries to read parameters.I guess it is caused by the file path. Only a guess. Can anyone help？

---

I am not even sure what "stops" means (Stalls? Stops running? error popup? Becomes unresponsive? etc.) In any case, ensure that you do proper error handling and switch behavior according to error conditions. The code needs to keep running, but must inform the user about a problem in some way.

---

The progam "Stops"...is that not enough information to find the problem?  

Maybe the developer should have added some basic error handler.;D 

[papigo]

Thank you all.Inspired by you all，after a few tests，I find where my problem is. When I generate my install packacge，I  forget to add ini files from source to target. As a result，software is installed without ini files. Of course it can‘t read the files.A stupid mistake.A shame.

[JÞB]

---

@papigo wrote:

Thank you all.Inspired by you all，after a few tests，I find where my problem is. When I generate my install packacge，I  forget to add ini files from source to target. As a result，software is installed without ini files. Of course it can‘t read the files.A stupid mistake.A shame.

---

We all made similar mistakes once....glad we could help. 

[RavensFan]

Not every reply in this thread should qualify as a solution.  Only mark the one or two messages that actually would be a solution.

If you to give someone thanks for being helpful, then use the Kudo button.