How can I save a VI into llb programmatically and build application

[zhichao]

I used the librarian vis in vi.lib > utility > libraryn.llb to copy a vi into llb. But it can't be build to appalication. I have ever modified all the vi name but I don't know why the application can't work. There is always a error. I am absolutely sure it work well before building. Is there any other way to copy/save a vi to llb? I know the VI server can't do.

[hulaj]

zhichao wrote in message news:<506500000008000000282A0000-999158726000@exchange.ni.com>...
> I used the librarian vis in vi.lib > utility > libraryn.llb to copy a
> vi into llb. But it can't be build to appalication. I have ever
> modified all the vi name but I don't know why the application can't
> work. There is always a error. I am absolutely sure it work well
> before building. Is there any other way to copy/save a vi to llb? I
> know the VI server can't do.

It is problem of LabVIEW Run Time Engine, where this feature is not
implemented in case of smaller size of engine ...
I had the same problem when I want to copy VIs in application, and I
solve it by using Copy File VI, but it can not be used to store to
LLB.

[David Moerman]

I would like to know if NI has done anything to solve this problem yet. I would like to create a "patcher" utility to replace a single VI within a built application's support llb. I have LV 6.1 and I still can't use the libraryn tools as they fail after they have been built.

[Greg_McKaskle2]

> I would like to know if NI has done anything to solve this problem
> yet. I would like to create a "patcher" utility to replace a single
> VI within a built application's support llb. I have LV 6.1 and I
> still can't use the libraryn tools as they fail after they have been
> built.

The libraryn tool cannot update a library since that code is not a part
of the runtime. The runtime engine cannot save VIs, and while it could
be made to manipulate llb files, at this time it doesn't. Since
changing this would involve releasing another runtime, which would have
to be installed on your customer's machine before your EXE would work on
LLBs, this may not be that convenient.

I did a quick search for binary patch utilities and found some th
at are
for purchase, and I'm sure there are some free ones as well. These
patch utilities should work on LLBs or EXEs built with LV the same as
with any other binary file. Especially if you want something that works
immediately, you may want to look at these general purpose tools.

Greg McKaskle

[JoeCAE]

HI,

I am using LabVIEW 8.0.1 and I am trying to programmatically build an application (.exe) out of VIs by first creating a library (.llb) and then compile the .exe file. I succeeded the first step to create the llb. To build the application, I am using a VI found in labview library, called:
C:\Program Files\National Instruments\LabVIEW 8.0\vi.lib\AppBuilder\ABAPI Build Application.vi

I am providing these inputs:
- LLB to convert (the one I've just created using LLB Manager to first create an empty llb and then C:\Program Files\National Instruments\LabVIEW 8.0\vi.lib\Utility\libraryn.llb\Librarian Copy.vi to copy into the llb a VI that simply pops up a message box showing "Hello World!")
- Application Destination (e.g. C:\Hello world.exe)
- Application Info (the name only, e.g. "Hello world")

The following error occured:

Error 6 occurred at Invoke Node in ABAPI Dist Build App from LLB.vi->ABAPI Build Application.vi->Builder.vi
Possible reason(s):
LabVIEW:  Generic file I/O error.
---
NI-488:  I/O operation aborted.
Method Name: Build:Application

Can somebody help me with this?

[bburress]

Hey Joe,
    I saw a couple of instances where previous customers have ran into a similar situation.  Here's a link to another forum post talking about the same error, and here's another forum post about creating builds programmatically.  Also, the message could be coming from any other files you have in the LLB you are trying to build.  Make sure the file paths are current, and possibly try mass compiling them to make sure they are all upgraded to the right version of LabVIEW.