Building a stand alone application

[nicholas03]

Is this what you wanted to see? 

Message Edited by nicholas03 on 03-18-2009 08:55 PM

[Bob_Preis]

No.

That is not what I'm talking about. There should be a file with the extension ".log" in that folder if the LabVIEW.ini token is properly enabled and if LabVIEW.exe has been rerun after the token was enabled. The file name will match the build specification name. Try a search for "My Installer.log" (without the quotes).

Bob

[nicholas03]

I looked for the file by searching all files that have a ".log" and only found 3 relating to LabView.  I opened them and found one called "memerror."I do not know if this helps but I do ont know what to do.

 

I also recieved an error while trying to run the set-up.

Message Edited by nicholas03 on 03-19-2009 11:41 AM

Message Edited by nicholas03 on 03-19-2009 11:43 AM

[Andrew_E]

Hi Nicholas,

You will find the LabVIEW.ini file in C:\Program Files\National Instruments\LabVIEW X.x . This is where you would add the line (CDK.EnableLog=true) then save.

Then you want to rerun your executable and until the error occurs. Find he temporary file explained previously as well as the log file that will be created once you addthe above line to your ini file.

[KittF]

I spoke with Nicholas.

Here is the simplified case:

With a brand new project, he builds an installer with nothing but the LV 8.6 RTE as an additional installer.

    This gives error code -12

If the LV 8.6 RTE is removed from the additional installer, the build occurs without error.

The problem seems to be when including the LV RTE (or any additional isntaller - I haven't tried other).

The LV RTE 8.6 is cached on his hard drive. 

This is as far as we got.

My thought is to delete the cached RTE and let the build ask for the RTE.  

Another option would be to try a diff installer to see if it is a more general probelm.

Suggestions?

[nicholas03]

I made the setup.ini file where the installer was looking for the program and now I have hit a roadblock because I do not know what to put in the file.

Any ideas? I put the "CDK.EnableLog=true" command line into the file.

Message Edited by nicholas03 on 03-22-2009 10:20 AM

Message Edited by nicholas03 on 03-22-2009 10:23 AM

[Bob_Preis]

There's still quite a bit of confusion going on. The token needs to go into your LabVIEW.ini file (not your setup.ini file). The purpose of the token is so that LabVIEW records additional debugging information when you attempt to build your installer. The token doesn't "fix" anything -- it just gives us more information about the build failure.

As you and Nemo noted, building the installer fails when you include the LVRTE part on the Additional Installers page. I need you to reproduce that scenario with the token in your LabVIEW.ini file. One of the AEs (Nemo?) should be able to walk you through it step-by-step if more assistance is needed. Once you've got the .log file, attach it to this thread please.

Thanks,

Bob

[Andrew_E]

Hello Nicholas,

Could you follow the steps in this knowledgebase article. They will help you create the log file.