LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Getting very large application with LVOOP

Hello to everybody

I'm programming a quite large application using LVOOP. The application will later be split in several dll's which are called by a C++ main program, so instead of having a large 6MB executable I expected to have  a  few smaller dll's up to a size of 1MB. Using a "by reference approach" using objects stored in queues everything seems to work, however I noticed that as soon as an exported VI is a member of class the resulting dll will compile all the other members of the class and include that code in the dll. So even an empty(!) VI exported to a dll will have a size of about 4MB. If I drag the VI out of the class the VI still has somehow the class information stored inside the VI and the resulting size of the dll will be the same. I'm wondering if anybody can confirm this strange behaviour (?). Since the application must be transmitted over slow analog modem lines the application size matters and I might be forced to recode my application using GOOP, something I basically want to avoid. Also compiling takes a very long time.

Alex
0 Kudos
Message 1 of 2
(2,535 Views)
Hi Alex,

this seems to be normal behavier, all members of a class will be included in the dll. In addition you have to take care about your parameters, LabVIEW objects can only be processed inside the dll. Classes cannot be transfered as output parameter to your C/C++ development environment, using conventioal datatypes as parameter is possible.

regards,

Nikolai
0 Kudos
Message 2 of 2
(2,502 Views)