Make an installer

[Ray.R]

Saw this thread...

I didn't read all the posts...  just jumping in by reading the last ones..

I'm not sure I understand what you mean by: "Something i found somwhere in the forum , i dont remember , but i guess it is working well."

Are you referring to an installer?   Basically, when you create your executable, you also create the installer (by selection) and include the LV Run-Time Engine.  Of course, you need to create a project which includes all the support files, and include those files as part of the build.  Creating an executable or installer is specific to your own project, and is not portable to other projects.

R

[kmous]

Hi guys

I removed all my word documents that i was pointing to but still i have the same problem. My UI.VI freezes up

i know it is missing alot of VI's but just take a look at block diagram is there any thing i can do ?

Thank you

Message Edited by kmous on 09-12-2008 03:30 PM

[Ray.R]

There are many missing VI' s that are needed to have a full look at what is going on.

When does it freeze?  What selection?

R

[kmous]

Bonjour RAY ,

I have only 4 selections from the list . somtimes it freezes up from temperature selection , sometimes from densiometrey .....it depends sometimes i connot go back to select another VI.

I thought the problem would be the word documents that i am linking to make help page , i delte it them all , but still i have the same problem.

the link on my other thread has all my VI's.  http://www.megaupload.com/?d=YSHMD33U

I am that my problem is in the UI.VI 🙂 

[Captain_Kirby]

Hi kmous,

This may not be the answer, but its certainly a good observation.

I noticed from what I could see in your UI.vi (without the missing VIs,) that you sometimes use absolute paths.

This, as well as any other absolute paths in your code could be giving you problems when you move the location of your executable, or move to another machine with a different configuration. If you are creating an executable, it is always a good practice to use relative paths so that the executable does not depend on any type of specific file structure (besides the specific files set up from the executable.) I would start by changing the above path to a relative one, and then look over your code carefully for any other absolute paths that may be giving you problems.

Message Edited by Captain Kirby on 09-16-2008 12:26 PM

[kmous]

Thank you but how you make it relative ? u mean data/densiometry.exe ?

[Captain_Kirby]

Hi,

In order to make your paths relative, you need to start with a known location in your installer hierarchy, like the executables path. To do this, use the "Current VI's Path" constant.

Note that this will return a different path depending on weather your in development or in executable. See this KnowledgeBase for more information:

Accessing a VI's Current Directory From LabVIEW and a Stand-Alone Application

Once you have a starting point, then you can use the "Strip Path" and "Build Path" VIs to build the path to your external VIs and programs.

Keep in mind that you have to ensure that the path from your application to your external software is always the same. Also note that this is just a good programming practice, and a recommendation to you. This may not solve your problem.

Message Edited by Captain Kirby on 09-17-2008 12:48 PM

[kmous]

I have a service request with am application eng , i called and i left a voice mail 🙂 could you ask him to send me the example he found please ?

it is 1239585

thank you

[Captain_Kirby]

I informed the engineer. He mentioned he will be available all day today.