lvoop build 8.2.1

[Intaris]

This question may have been answered before...... I've searched, but I can't find it.

I have a project using some LVOOP classes (as plug-ins) and I want to build an installer for the exe.  I'm having problems.

I managed, after much trial and error to get the EXE to compile.  I had to include the .lvclass in the exe and any override VIs outside the exe to get it to compile.

When I tried to create LLBs for the plug-in Classes, I keep getting Error 53 when I try to load them in the compiled program.  I'm able to find the *.lvclass, but calling App.Load Class raises Error 53.....

I'm following Tomi Maila's tips on Expressionflow (Thenx Tomi!), but I'm not making any progress at all.  I should be handing off an exe tomorrow, but this simply won't be hapening now.

Can anyone give me a hint as to what I'm doing wrong?  I think I might be muddling up my relative paths between classes or something, I really don't know.......

Shane.

[Eugen_Graf]

I used LVOOP in my projects and never got errors building EXE. A LV class is like a cluster and you don't need to include them to the included files to the EXE if you staticaly call class member VIs. If you call them dynamicaly, so you have to include them to your EXE. There are the same rules like without LVOOP.

[Intaris]

The program works fine compiled if I keep the classes statically-linked.

As soon as I try to keep the lvclass files OUTSIDE the exe and load them via APP.Load Class, I get Error 53.

I'll just have to deliver a statically.linked exe tomorrow.  At least I'll have an installer....

Shane.

[waldemar.hersacher]

Hello shane,

 I know you are a long time user here, but just to remind you of a thing.

If you build an exe only those VIs will go into the exe which are statically linked from each toplevel and dynamic VI. You say you keep the classes outside of the exe all VIs from other libraries will not go into the exe and you cannot load the VIs successfully.

As example: if you build a class around the Config Data VIs and you will only use them in this class then all VIs from <vi.lib>\Utility\config.llb will be missing in the exe but the class will try to load them. To solve this just create a folder named vi.lib in the folder where you exe resides and copy the part from <vi.lib> to this folder.

I do this in almost all newer projects but have until now not done with classes.

[Intaris]

Waldermar,

true, I'm a long-time member of the forum but that certainly doesn't mean that there's enough I don't know.....  I'm not Dennis after all.

Re. missing dependencies: I realised this problem during building, but the tips given by Tomi on Expressionflow goes into this saying that creating an LLB for a class must contain ALL dependencies.  I did that, but somehow I was not able to load the classes at run-time.  Maybe I should just create an exe and installer with 8.5.1.  Apparently a lot of  problems with classes were fixed in that release.

Shane.

Message Edited by Intaris on 11-08-2008 07:47 AM