Adding VIs to LLBs - Is there an Easy Way?

[PhilipJoeP]

Hi All,

I have a question about using the LLB Manager to make an LLB file.  I currently have a bunch of VIs in a LabVIEW project and would like to add them to an existing (or new) LLB.  The only way i've found to do this is by going into each VI and performing a "Save As" and saving the VI within the LLB.  Is there no simple way of dragging and dropping VIs into an LLB?  Or maybe even an batch save/import into the LLB?

Thanks!

[F._Schubert]

LLBs are outdated and should not be used. Use lvlib instead.

Felix 

[Dennis_Knutson]

Do not use llbs. There is simply no reason for llbs except possibly to do a final distribution. They are obsolete for development use. A quick search will show you some of the dangers - i.e. a single corrupt VI will rendoer the entire llb unuseable and they don't play well at all with SCC. Since you have the VIs in a project, create a lvlib instead.

Message Edited by Dennis Knutson on 10-06-2009 09:09 AM

[PhilipJoeP]

Well... I appreciate both of your responses. However... I believe that lvlibs cause more frustration then anything else.  My team has come across issues with lvlibs and conflicting paths (when using CM tools) and have resorted to using LLBs because they offer a clean set of file dependencies.  I understand that lvlibs are probably more robust, but they are not an option right now. Therefore...  the question I originally asked still remains.  Is there a quick and easy way to add a bunch of VIs to an LLB without having to save each one of them separately to the LLB?

[F._Schubert]

The OpenG builder for LV 7.1 (I don't know if newer versions still support llb's) is allowing to save as dll. As it is open source, you might find inside what you are looking for. I neither have the time or interst to dig it up on my own.

Felix 

[Darren · Accepted solution]

I think you can create a Source Distribution of your code and indicate that it should all go into an LLB.  Alternatively, you could use the VIs in vi.lib\utility\libraryn.llb to write a utility that would move all your VIs into an LLB.

[RipRock99]

I hate to pile on here, but I have to agree - lvlibs are very difficult/dangerous to use.  I reverted to just piling everything into one directory and zipping them.  Ugly, but it works everytime, while avoiding file dependency conflicts causing sub-vi's to be un-executable, and worse, un-removable from missing libraries.  May main desire is not too maintain change control, but to be able to distribute point versions once.  Most of the time I will have many working versions of a code, and if a library insists on trying to synchronize these across 5 computers upon which code development will be done, it is a guaranteed mess.

Rave off.

RipRock 

[PVAHamm]

 I know that it's over a year later, but I'm piling on too.  lvlibs drive me nuts...  dependency conflicts scare my customers.  I really shouldn't have to tell the compiler that I'm NOT using deleted files anymore.