LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

multiple lvlib build problems, help!

Hello All,

I have a fairly serious concern that either I am doing something stupid, or there is a big problem with build applications which have multiple libraries (lvlib). I am running LV8.5

Basically, I have two libraries, each of these libraries has a VI called Main.vi.

e.g. Lib1
           ---> Main.vi

Lib2
    --> Main.vi

These lvlibs are in separate directories, and are included in a project. Main.vi from Lib1 is used within Main.vi in Lib2

When running in the IDE there is no problem, as each of the Main.vi are prefixed with the name of the library, as I would expect (i.e. Lib1.lvlib:Main.vi and Lib2.lvlib:Main.vi). Everything works fine.

However when I build it warns me that there is a namespace collision, but LaVIEW prevented this from happening. (Which is ok I suppose). The build appears to succeed.

But when I try and run it, I get "Top Level VI(s) could not be opened."

Attached is a sample project. I would really appreciate help on this as otherwise I am in a bit of a pickle! I have tried messing around with the various project options, all to no avail.

ps: I can get it to build fine if I manually override the filename as part of the build options, but this is not feasible for a bigger project. I thought using lvlibs was supposed to take away this pain?


0 Kudos
Message 1 of 3
(2,907 Views)
Still no luck here.

Are there any magical settings to put in the ini file to see why the compiled exe does not run properly?

I have tried using the debugging in the build options, but the VI seems to crash before the debugger has a chance to catch it (it doesnt actually load properly).

This is really frustrating...
0 Kudos
Message 2 of 3
(2,891 Views)
Update:

For anyone interested, I may have a work around...

It seems the root top level VI cannot have the same name as any other VI in any other library. Renaming the root VI (but still having VIs with conflicting names) seems to be fine, the application builds and places supports VIs in their own directories (which is ok for my application). I don't know what I would do if I wanted it all inside one exe.


0 Kudos
Message 3 of 3
(2,878 Views)