how to generate an executable with lvclasses?

[vix]

Probably there's a simple detail I've missed, but I can't understand what...

I developed my first project using LabVIEW classes, and It works fine into development system.

When I tried to build the EXE I found the VIs with the class functions in the executable folder. But I don't want to include these "source" files into the EXE directory.

If I build the EXE of the Board Testing shipped example I have the same problem (see attached).

How can I generate an EXE without these VIs in the output folder?

[Ben]

In my case, my challange was to include those files so I will have to speculate.

You could put all of your classes in a dll included with the app. You will have to makes sure your paths in the exe are correct.

I'll watch for others (that actually know what they are talking about).

Ben

[tst]

The problem is that executables are built as an LLB and can't have two VIs with the same name inside them, but classes often have VIs with the same name (used for overriding). The solution NI came up was to place the class VIs outside the executable.

The good news is that NI is aware that people don't like it, so hopefully this should be solved soon.

[shew82]

The current solution, as has already been hinted at, is to put the class files into a separate LLB (you can rename this to be .DLL if you want to be *really* sneaky):

1. In the Destinations options create an LLB destination for each of your classes

2. In the Source File Settings options, set the destination of each class to be your newly created destination instead of "same as caller"

(see attached screenshots) 

Shaun 

 

 

Message Edited by shew82 on 05-19-2009 09:37 AM

[vix]

---

shew82 wrote:

1. In the Destinations options create an LLB destination for each of your classes

2. In the Source File Settings options, set the destination of each class to be your newly created destination instead of "same as caller"

---

This seems not to work in LabVIEW 8.2.1...

I did a test with an evaluation of 8.6 and it works, ... but I need a solution in LabVIEW 8.2.1