LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

build problem with lv 7 under linux

When building my App. my custom controls are gone!...

LV 7.0 - Gentoo Linux.
0 Kudos
Message 1 of 6
(2,585 Views)
I made some more testing concerning disappearing controls ounce the application is built.
Test.vi -> plain boolean and a plain numeric control.
Works fine.
Build the app.
The boolean disappear!. ( running on same machine ).
I'm puzzled.
0 Kudos
Message 2 of 6
(2,568 Views)
You will need to include the custom control files when building the VI. How to do this is explained here:

http://digital.ni.com/public.nsf/websearch/378409F1F1B293BE862569E00000115E?OpenDocument

Hope this helps!

Laura
Message 3 of 6
(2,560 Views)
Thanks Laura,

Here is what I have done now.

I made test.vi it without any custom control.

The vi has
1. a numerical control connected to numerical display
2. a boolean control connected to a boolean display
3. a boolean to stop the vi

When it is run in the development env. everything is fine.

Now I build the app.
1. the up/down arrows of the numerical control does not show up
2. both boolean does not show up, except the dialog type boolean.

If I click on the invisible up/down arrow I can see inc/dec of the numerical display.

???

I have included as an attachement the test vi, test.vi and the built one.
0 Kudos
Message 4 of 6
(2,557 Views)
I'm not using Linux but the description of what you see can also occur under Windows.

The effect that all 3D parts are not drawn occurs when the OpenGL library and/or the model files are not found. Under Windows this is in the shared\Labview Run-Time\7.1 folder. The library is in the mesa.dll and the models are in a subfolder named models.

I think your application doesn't find the mesa shared library or the model files.
Waldemar

Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions
Message 5 of 6
(2,553 Views)
Many Thanks Waldemar,

It works!

It was the models subfolder installed somewhere else in the dev env.

Made a link to it in AppLibs dir and "voila!". Fixed
0 Kudos
Message 6 of 6
(2,550 Views)