Build LLB using Applicatio​n Builder

Question

It would be nice if the Application Builder could create redistributable LLBs in addition to EXEs and DLLs. I know OpenG has an app that will do that called DEAB, but it doesn't have a "Build Manager" like the the Application Builder that comes with Labview. I don't think it would be too hard for NI to add this feature to Labview.
By the way, if someone knows of a "build manager" written to work with DEAB, I'd love to know about it.
P.S. In case you're confused what I mean by "Build Manager", I mean an environment where paths can be defined, and different builds can be loaded/created/edited/saved. Dynamic VIs can be defined. Basically, the GUI portion of Application Builder.

Answer 1

Alex,
> I was talking about organizing many build INIs
> with a GUI interface.
Yeah, that would be really cool! I was waiting for the build file format and requirements to settle down, before investing the time in a GUI. GUIs are always the very last thing that code -- doing things this way eliminates a lot potentially bad code (out of respect, I won't give any counter examples ;-).
> Defining support files to be copied over is a
> very useful feature as well.
Yeah, that's one feature that I need badly, too. Expect to see it in the very near future.
> I am having problems with creating accounts on
> the openg website, so I'll just post everything
> here.
Please send me an email jkring{at}openg{dot}org with the specifics
so that I can fix this problem.
> I still don't understand why you have to create
> the LLB building utility, and not NI. They
> should be the ones doing this, and they should
> have done this a long time ago.
I have stopped asking such questions a long time ago. Instead, I just provide NI with feedback about what I want, participate in beta programs, and solve the problems that are directly in front of me. NI will add features and tools when it is in their business interests to do so. But, as a precondition they have to know that such a requirements exists. It is up to us to provide this feedback either explicitly, or by creating and demonstrating our own tools to NI.
Also, be careful of the catch 22 -- the tools you ask NI for, just might cost you $995 when they're released.
If you are interested in making the DEAB better, please help with the requirements and specification development. Once the specification is completed, the implementation can be coded in no tim
e at all.
> p.s. Jim, do you ever sleep? :-)"
Yes, but I dream about LabVIEW ;-))
-Jim