View size of files that make up an LLB?

[LeroyBogz]

Does anyone know if there is a way to view 'by size' in the LLB manager? 

[Dennis_Knutson]

I don't know of any method. Why are you using an llb? It's been obsolete for several years.

[rolfk]

You could always hack up the LLB Manager to do what you want. It's written in LabVIEW and resides in <LabVIEW>/projects/llbedit.llb.

[Bob_Schor]

---

@Dennis_Knutson wrote:
I don't know of any method. Why are you using an llb? It's been obsolete for several years.

---

Really?  It was my understanding that the .rtexe, the format that is the default "executable" format for Remote Targets such as a PXI chassis, is a compressed version of an LLB.  I also understood that the only other way to deploy something to a remote PXI was as a "source distribution", which I also understood was an LLB.

How does one configure "stand-alone" code (meaning code not deployed "by hand" from Project) to run on a remote RT system other than as a single .rtexe ("skinny LLB") or as a Source Distribution (LLB)?

I'm not trying to be cute, here -- I'm just "migrating myself" and my code from LabVIEW 7 to LabVIIEW 2012, and this is the one detail that I've not completely understood.

Bob Schor

[rolfk]

I'm not sure about rtexe, but normal exes are since about LabVIEW 2009 really disguised ZIP files inside an executable wrapper, unless you select the "Use LabVIEW 8.x layout" in the Build options. So I wouldn't be to surprised if they use that in LabVIEW RT executables as well.

[Dennis_Knutson]

I don't use the RT version and I'm not familiar with the deployment options but for using an llb in development, yes it is obsolete. It has always been somewhat fragile on that a single corrupt VI will make the whole thing unreadable. It is not compatible with source code control. With the introduction of the project in LabVIEW 8, simply no reason to use it.

[LeroyBogz]

Dennis, can you please expand on this point? What is the modern way to keep everything together?  

[Dennis_Knutson · Accepted solution]

In a project or lvlib.

[LeroyBogz]

wait a sec though, the lvlib seems to offer scope protection but takes away from having "one file" that has all of your subvis in it. What's the best way to have that? I want to send my code to bob all in one file what's the best way to do this? 

[rolfk]

The packed LabVIEW Library. Basically it's a ZIP file of a lvlib but with the extensione lvlibp.