Moving a library guidance

[Uke88]

Hello all,

I am not exactly sure what I am looking for, but I'm hoping someone can point me in the right direction.

I downloaded the LIFA (Labview Interface For Arduino) toolkit through VIPM on computer A.  I then modified the toolkit to communicate to an Arduino via Ethernet instead of Serial along with creating some custom VI's which I believe are in the LIFA library.  I now need to get that library to computer B.  

Whenever I try to create a new library and add the files and folders to it, the entire LIFA library is copied over with it.  Basically, my new library looks something like this:

-New Library 

  -LIFA
    +Subfolder
    +Subfolder
    +Subfolder
    +Subfolder

I've seen topics on creating a new Library from an existing one.  Is that what I'm looking for?  If so, can I just create a new library and then copy and paste it into the vi.lib folder on computer B?

Thanks, 

Matt

[Wire_Warrior]

Are you attempting to use VI Package Manager with this?  What's your transfer mechanism?

Libraries do "own" all the VIs that are members and do expect to have those VIs present on a machine.  Have you tried right clicking the VIs you don't want and choosing the "Remove from Library" option?

[Uke88]

Wire_Warrior,

I was planning on just using a USB drive for now.  I don't think I want to use VIPM yet, i'd say my version of LIFA is in beta and there is the working version created by Sammy_K which I have modified.  I wouldn't mind putting it on the VIPM once I consider it finished.  

I found the LIFA.lvlib file.  Is there a way I can just copy that and all of it onto a flash drive?  

[Uke88]

Update,

I've been looking into the difference between llb, lvlib, and lvlibp and determined i want to use lvlib.  I know I want everything in my vi.lib/LIFA folder (the VIs and subVIs) and menus/Categories (for the palette to accompany the VIs) in the lvlib from my old computer.  From there I can create a zip of the lvlib (http://www.ni.com/white-paper/3303/en) where I can save that to my flash drive and bring it over to my new computer.

My questions now are -

1) Do I just unzip everything into the corresponding folders on my new computer where Labview will automatically set up the links and I can start using it?

2) Am i missing any key information to bring over to the new computer (I think all I need is the VIs, subVIs, and menus)?

Thanks,

Matt

[Uke88]

Update

I tried several methods of distirbution to get my lvlib to my new computer, all of them just built the main VI which uses the library.  Ended up just coping and pasting all the parts of my library in their corresponding parts in Labview and almost everything seemed to work fine.  My only problem is the palette menu.  The original got transfered just fine, but all my modifications to it changed.  Is there a way I can mod the panel so everything is normal when I copy it to different computers?

Thanks,

Matt

[Mark_Yedinak]

Have you considered using source code control? This is a good mechanism to share code across multiple machines.

[Uke88]

Here is my end game, I am developing a VI which controls the Arduino through ethernet communications which I will distribute to my clients as needed.  Once the code works for me, I'd like to realease my LIFA-Enet library to the NI/LIFA community along with giving the library to my clients, so they can modify the top level VI's as they see fit.  

I think Sorce Code Control is to have multiple developers working on the same project, correct?  I haven't looked too far into it, but if its what I'm looking for, I'm not opposed to it.

Matt

Edit:

I am the only person that is working to develope code (that i know of) for LIFA-Enet.  Therefore, I feel like subversion would be excess if I'm the only one checking things in and out through the Sorce Control (which sounds like subversion to me).

[Mark_Yedinak]

---

@Uke88 wrote:

Here is my end game, I am developing a VI which controls the Arduino through ethernet communications which I will distribute to my clients as needed.  Once the code works for me, I'd like to realease my LIFA-Enet library to the NI/LIFA community along with giving the library to my clients, so they can modify the top level VI's as they see fit.  

I think Sorce Code Control is to have multiple developers working on the same project, correct?  I haven't looked too far into it, but if its what I'm looking for, I'm not opposed to it.

Matt

Edit:

I am the only person that is working to develope code (that i know of) for LIFA-Enet.  Therefore, I feel like subversion would be excess if I'm the only one checking things in and out through the Sorce Control (which sounds like subversion to me).

---

I use SVN at home for my projects that I am the single developer. Even for a single person source code control is useful. It allows you to maintain older copies of your code so if you really screw something up you can always go back to an earlier version. Tagging the code in the SVN repository is very useful for this.

As for distributing it to your clients have considered using packed project libraies? This would package everything up into a single file and make it very easy to distribute.

[Uke88]

Mark,

Does the packed project file allow someone to modify the sub VIs?  From my understandning of them, once I deploy the code, everything is set in stone for them and they can't modify anything.  I think of it like a .exe.  I've searched through the LV help and havent gotten a good understandning of the packed project library.  

If a packed project library is what im looking for with my customers, can I use that to release my code to the NI/LIFA community?

Thanks,

Matt

[Mark_Yedinak]

Have you read the info here? Specifically this:

"How do I distribute a project library?
In order to distribute a project library, you can simply distribute the .lvlib file along with all the other files the library owns. Alternatively, you can create a single zip file containing the entire library and distribute it. To accomplish that right-click Build Specifications, select New»Zip File, and include the project library under the Source Files category. For more information on creating zip files refer to Distributing Applications with the LabVIEW Application Builder."

You may be wright that the packed project libraby may prevent modification of the code.