LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

BuildTargetBuildSpecifications - error 1

Hi all,

 

I wanted to do a one-click build, so I have a buildAll.vi. It sometimes works. Sometimes, however, it returns and odd error after creating an installer programmatically: "Error 1 occured ... Unable to generate preview: Must specify one startup vi".

As I said, this occurs when creating the installer. The start up VI was already specified in the exe build, in the step before. What could be causing this?

 

It also sometimes happens when using BuildTargetBuildSpecifications only when building the installer, even not as part of the one-click build.

 

Any ideas?

 

Thanks,

Danielle

"Wisdom comes from experience. Experience is often a result of lack of wisdom.”
― Terry Pratchett
0 Kudos
Message 1 of 6
(2,885 Views)

Hi Danielle,

 

Could you send me your VI?

 
The issue must be when you create the ".exe".

 


Brice S.
National Instruments France

0 Kudos
Message 2 of 6
(2,877 Views)

Hi,

 

Here it is attached. (our project is called NWS). Any suggestions or imrpovements would be welcome.

 

Thanks for your help!

Danielle

"Wisdom comes from experience. Experience is often a result of lack of wisdom.”
― Terry Pratchett
Download All
0 Kudos
Message 3 of 6
(2,840 Views)

Hi dsavir,

 

In trying to look through the code you posed, I found that a number of files were missing. Could you please upload the following:

  • BuildNWS.lvlib
  • filtering_1d_array_strings
  • NWS type (this is Type Def, so it'll be saved as a .CTL file)

Otherwise, your code seems to look fine -- you are making use of the State Machine architecture, and seem to have all the VI Server calls down. As far as the error you are receiving, is the .EXE built successfully when you get errors about not having specified a startup VI? It may be that you are not able to catch the error until the step in which you build the installer, and that there really is an issue with setting up the startup VI in the previous step. Also, is there anything specific that you can do to repeat this behavior? This might provide some more insight about what's causing this issue.

Sanjay C.
Embedded Software Product Manager| National Instruments
0 Kudos
Message 4 of 6
(2,825 Views)

Hi,

 

I have attached the files.

 

As far as I saw, the exe is built successfully, with no errors. The files are created and work. Also, as I said before, the error also occurs when choosing the option "build installer" only, without doing the exe before.

 

On my computer the build.vi works if I first open the NWS project and run the installer build manually. On my colleague's computer it always fails.

 

It fails only on a specific build. We create two installers, one with startup VIs A and B and one with A and C. It succeeds in building the EXE and installer of the first version and fails creating the installer of the second. When running the installer builds manually there is no problem.

 

We very much appreciate your help.

 

Thanks again,

Danielle

"Wisdom comes from experience. Experience is often a result of lack of wisdom.”
― Terry Pratchett
0 Kudos
Message 5 of 6
(2,789 Views)

Hi dsavir,

 

Sorry for the delay in response, but I have had a chance to go through the code in more detail. I realize that some of the subVIs are locked (for example, the 'run build' VI), which means I wasn't able to understand what happened within those subVIs. Regardless, the logic you have implemented seems to make sense, and it's difficult to say why this program works sometimes and doesn't work other times. My recommendation is that you watch the execution (using highlight execution and probes) of the code you've written as it executes cases which you know will work (A and B) as well as the cases for which you know it will fail (A and C). Since you have these VIs (A, B, and C) which can repetably show both the pass and fail cases for your code, it's going to be a matter of distinguishing what is happenening differently in the case of A and C (as opposed to A and B) so that you can pinpoint the issue and address the true cause.

Sanjay C.
Embedded Software Product Manager| National Instruments
0 Kudos
Message 6 of 6
(2,762 Views)