Application builder (using OpenG source)

I just made a LV program and executable thing in LV8.2.0.
Only one function (for converting cluster->ini) from OpenG was used to make the program easily.
When I copy the program folder, so many OpenG (maybe related to the converting routine) codes were created in subVI folder.
My question is,
1. In distributing source code, Is there some DLL or convenient format file for OpenG not to copy many Vis?
2. In making executable program by NI-application builder, how to treat the OpenG library if I have only one Vi ?
And as other question,
3. In NI buidler, the external libraries (run-time/DAQ/VISA) may be rather big.
How can I make the whole program( application+libraries installer) as small as possible?

labmaster wrote:
1. In distributing source code, Is there some DLL or convenient format file for OpenG not to copy many Vis?
2. In making executable program by NI-application builder, how to treat the OpenG library if I have only one Vi ?
And as other question,
3. In NI buidler, the external libraries (run-time/DAQ/VISA) may be rather big.
How can I make the whole program( application+libraries installer) as small as possible?
3: The DAQmx installer has several versions the smallest being 40 MB? and the largest 150 or something.
I think the VISA installer has the same options.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Similar Messages

Application Builder - Use of Global Variables

Hello,
I have an application which consists one one main VI running for the user interface, and one VI running in the background dealing with CAN communications. These two VIs must communicate using global variables. In the main VI, I have to open a reference to the global variable VI in order to write data to it. The application works correctly in LabVIEW environment. However when I build the application using application builder, I receive an error with the open reference VI in opening the global variable VI. The error given is Error Code 7: File not found. The path to the Global variable VI is correct however. I am pretty sure of this because in my main VI, I open up other VIs based on the open reference function and a path.
Therefore:
1) I can open references to normal VIs and use properties such as run VI without a problem.
2) This does not work for my global variable vi.
Build settings:
Im dont understand all the build options completely but the settings I use are:
1) Single target file contening all the VIs
2) All the VIs I use are located in the same folder
I hope the explaination is clear enough.
Do you have any suggestion to explain what happens and how can I make it work correctly?
Thanks
Julien

Duplicate.
Try to take over the world!

Application Builder: Additional Installers Source Location

I am having trouble creating an installer for my application. I can build the installer when I only inculde the NI LabVIEW Run-Time Engine, but I also need NI-FieldPoint for LabVIEW Real-Time and NI-VISA Runtime. When I try to include these I run into problems.
I think the problem is that I installed some of these from the discs, but now my company has an installer on the network that I have used as well, so now I don't have the discs. Is there a way to change the Installer Source Location in the Installer Properties? When I try to build the installer I am asked if I have the discs, but I do not. I want to be able to get the installers from my company's network or maybe I can download them from ni.com and have them on my computer, but I need to know how to change the Installer Source Location.
I reinstalled NI-VISA Runtime from my company's network and the Installer Source Location changed to the network location (which is what I thought I wanted), but it still asks for CDs and if I click throught I get the following errors:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
*** Error: An internal error occurred for which the cause is unknown. (Error code -41)
*** End Error Report
Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'NI-VISA Runtime 4.5' from: \\aerolabview\LabVIEW\LabVIEW 2009\DriverDVD\Products\NI-VISA_Runtime\ to: C:\PPG\installer\PPG\
*** Error: Windows SDK function returned an error. (Error code -12)
The system cannot find the path specified.
*** End Error Report
Done building deployment

Hi Bob,
My most recent attempt gave me this error immediately after clicking Yes on the Distribution Needed window. I was never prompter for anything after clicking Yes:
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
*** Abort requested.
Done building deployment
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'FieldPoint 6.0.1' from: C:\Documents and Settings\Administrator\Desktop\FIELDPOINT_601_20080201_final\ to: C:\PPG\installer\PPG\
Copying distribution 'NI-VISA Runtime 4.5' from: \\aerolabview\LabVIEW\LabVIEW 2009\DriverDVD\Products\NI-VISA_Runtime\ to: C:\PPG\installer\PPG\
*** Error: Windows SDK function returned an error. (Error code -12)
The system cannot find the path specified.
*** End Error Report
Done building deployment
When I build the application, I get a lvapp.lib.tmp file in the temp directory, but I get no new temp files when I try to build the installer.
I would also like to point out that if if I uncheck FieldPoint 6.0.1 from the Additional Installers, and select either FieldPoint 6.0 or FieldPoint 6.0.3 (which are other optiions that show up in the list), I still get the same error as above that references 6.0.1
-Chris

Application Builder using dblink

I created a database link to a remote database. I then created a synonym for one of the remote tables. I want to create an application to run against this remote table. The synonym doesn't show up in the list of table to select when creating a tabular form. If I key in the synonym (or the table_name@dblink) I get the following error when I try to add the page:
1 error has occurred
Source tables for forms and tabular forms must have a primary key.

This thread over in the Apex forum may be of help:
tabular form dml via db link fixed in XE / 2.1 ?
Sergio

Application Builder Applications List View Detail - Parsing Schema

When viewing all applications in the Application Builder using the View Detail option the list of applications is shown with the Parsing Schema showing APEX_040100 or APEX_040200 according to the apex version. Shouldn't it show the actual schema that the application will use?

Prabodh wrote:
Hi,
How will Apex know the actual schema without getting into the code and analyzing it?
I meant just showing the actual "parsing schema" which is set for the application, not all the possible schemas the application may actually reference. The parsing schema is one of the parameters asked for when importing an application. It is also defined in the application definition.
A workspace can have any number of schema assigned to it, other than the Default Parsing one. So, the only other option would be to list all the assigned schema. Which in my opinion (and most probably in the mind of the designers of Apex as well ) will be an unnecessary long list.In my opinion it seems unnecessary and fairly useless to show the APEX schema (APEX040100, APEX040200) when listing a few details of the application. Just wondering if it is on purpose or an overlooked bug.

Report Generation for Excel does not work after using the Application Builder

I have a VI that writes data to an Excel file using the Report Generation Toolkit. I recently compiled the VI into a single Application (EXE) using the Application Builder. My VI runs its tests properly, but no data is written to Excel. What could be the cause? I don't receive any error messages.

Hi
I usually build exe-files, which sometimes also have report functionality.
Open the Application Builder and check the following things:
1. Add the following vis: _Word Dynamic VIs.vi, _Excel Dynamic VIs.vi They should be located in the directory ..\LabVIEW X.X\vi.lib\addons\_office in the llbs _wordsub.llb and _exclsub.llb (report1.jpg)
2. If you use an Installer, go to the Advanced Settings. There you can select some things to include in the Installer. Check if "NI Reports Support" is selected. (report2.jpg)
These are the things I always do, if I need reports and I never had problems up to now. I made two screen-shots of these settings.
Hope this helps.
Thomas
Using LV8.0
Don't be afraid to rate a good answer...
Attachments:
report.zip ‏25 KB

After installing an application that was created using the Application Builder

After installing an application that I created using the Application Builder I get this error if I try to run " ANY " LabVIEW App's that I have built. "Executable Version 7.1.1 doesn't match Resource File 7.1. Check your configuration."
The way that I tried to fix this is to reload LabVIEW 7.1 and DAQmx 8.0. I am using two NI-6528 switch cards.
After I reload LabVIEW and DAQmx I can run my applications but as soon as I install one on this development machine the error begins again.
The executable that I built works fine on the development machine and any other machine that I try it on but it appears that the Run-Time engine 7.1 becomes corrupt after I run setup.exe for the newly created application.
I have built numerous Installers, setup.exe's in the past without this error. Just this latest one caused this problem to start.
I can NOT upgrade to 7.1.1. I am doing work for many different sections of this factory and I can not force them to upgrade. I've asked. Others supply code for the same machines using LabVIEW 7.1.
I am stuck creating executables and manualing moving the correct files to the target machines.
What can be done?

No. The KB article was talking about a machine with 7.1.1 installed. I have LabVIEW 7.1 installed.
The machine that I am having trouble with is my development machine. LabVIEW 7.1, DAQmx 8.0.
If I build the executable all is fine. I can still run old executables including the one I just built.
If I create the installer all is fine. I can still run old executables including the one I just built.
When I install the app on my development machine the corruption occurs. I can " NOT " run old executables including the one I just built. The subject error pops up.
I have not moved any executables to the other machines yet. I don't want to corrupt others.

How can I use a shared library made with the application builder?

Hi,
I am using LabVIEW 7.1 running on Slackware 10.1 (kernel 2.4.29) and I am trying to call a graph display from a C program that I use for debugging VME access from a VMIVME controler. So using the application builder I built the VI as a shared library (graph.vi -> graph.so) containing a function called "graph". In my main program the call to the dlopen fails with the error: "graph.so: undefined symbol: UninitLVClient". When I examin graph.so with nm I see that UninitLVClient and other LabVIEW functions are indeed undefined and using ldd shows that graph.so has dependencies only on libc.so.* and *linux*.so.* but not on LabVIEW related stuff. Those functions are defined in the liblv.so that's in the cintools directory but I have no idea if the user is supposed to use that.
So I think I am missing an important concept here. Can somebody help or direct me to some documentation (I found lots of information about how to link external code to LabVIEW but nothing about how to link LabVIEW code to an external program)?

Thanks Watermann,
your message has been very useful so now I am linking to the proper library but I still have problems when trying to load dynamically the shared library produced with LabVIEW. It is strange that I could successfully load the lvrt library at loading time but it does not work when I am loading the library at execution time.
I made a small LabVIEW program that prints a hello window and I am calling it from a C program. In the first program main.c I am linking to the lvrt library at loading time and it works but in the second one I am linking dynamically at execution time and it does not work. For my work I need to be able to load code done in LabVIEW at execution time. Any help is appreciated!
Program main.c:
// small program to call a LabVIEW shared library
#include
#include
#include "hello.h" // got this from the LabVIEW builder, i.e. when I made the hello.so
int main(void)
printf("Hello from C!\nLets call LabVIEW now\n");
hello();
printf("Bye ... \n");
return 0;
The command to compile main.c, i.e. linking shared library lvrt when loading main program:
gcc -Wall -I /usr/local/lv71/cintools/ -o main main.c hello.so -l lvrt
The LD_LIBRARY_PATH has been defined and exported:
$ LD_LIBRARY_PATH=$PWD
$ export LD_LIBRARY_PATH
IT WORKS!
Program main2.c:
// small program to call a LabVIEW shared library
#include
#include
#include
int main(void)
void * h_lvrt;
void * h_hello;
void (* hello)(void);
char * error;
printf("Hello from C!\nLets call LabVIEW now\n");
// open LabVIEW RunTime shared library
// in my computer located at /usr/local/lib/liblvrt.so
h_lvrt = dlopen("/usr/local/lib/liblvrt.so", RTLD_NOW);
// check for error
error = dlerror();
if (error) {
printf("error : could not open LabVIEW RunTime library\n");
printf("%s\n", error);
return 1;
// open hello shared library
// in my computer located at /home/darss/lv_call/hello.so
h_hello = dlopen("hello.so", RTLD_NOW);
// check for error
error = dlerror();
if (error) {
// close LabVIEW RunTime shared library
dlclose(h_lvrt);
printf("error : could not open hello library\n");
printf("%s\n", error);
return 1;
// get function hello from library hello.so
hello = dlsym(h_hello, "hello");
// check for error
error = dlerror();
if (error) {
// close hello shared library
dlclose(h_hello);
// close LabVIEW RunTime shared library
dlclose(h_lvrt);
printf("error : could not get the hello function\n");
printf("%s\n", error);
return 1;
// call hello function
hello();
// close hello shared library
dlclose(h_hello);
// close LabVIEW RunTime shared library
dlclose(h_lvrt);
printf("Bye ... \n");
return 0;
The command to compile main2.c, i.e. dynamically linking library lvrt at execution of main2 program:
gcc -Wall -o main2 main2.c -l dl
The LD_LIBRARY_PATH still defined and exported.
IT DOES NOT WORK!
Program output:
Hello from C!
Lets call LabVIEW now
error : could not open hello library
/home/darss/lv_call/hello.so: undefined symbol: WaitLVDLLReady

Using data source in adf application.

Hi ,
JDev version : 11.1.1.6.0
I am planning to use data source in the application , but there is an issue facing while running with data source.
Exception in thread "main" javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:197)
    at com.cisco.complianceutil.WizardDataSourceUtil.main(WizardDataSourceUtil.java:42)
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
    at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
So I used "Weblogic.jar" once and "wlfullclient.jar" . By using one of these jars issue fixed but because of it while loading the application it is throwing the below error .
<Sep 10, 2013 2:42:05 PM IST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: [HTTP:101216]Servlet: "weblogic.wsee.jaxws.client.async.AsyncTransportProvider" failed to preload on startup in Web application: "ComplianceWizard".
javax.xml.ws.WebServiceException: javax.xml.ws.WebServiceException: java.lang.InstantiationException: weblogic.wsee.jaxws.client.async.AsyncTransportProvider
    at weblogic.wsee.jaxws.WLSInstanceResolver.getSingleton(WLSInstanceResolver.java:36)
    at weblogic.wsee.jaxws.WLSInstanceResolver.start(WLSInstanceResolver.java:55)
    at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.start(WLSInstanceResolver.java:82)
    at com.sun.xml.ws.server.InvokerTube.setEndpoint(InvokerTube.java:85)
    at weblogic.wsee.jaxws.EndpointAwareLateInitTube.postCreateEndpoint(EndpointAwareLateInitTube.java:48)
    at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:150)
    at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
For this I observed that solution is removing the wlfullcient.jar or weblogic.jar from the libraries. But If I do not use any one of them then data source does not work. Please guide me with your suggestions.

This is configured in your database access layer - if it is using ADF BC then in the Application Module go to the configuration tab and edit the local configuration to see the information about which DB you are accessing.

I have a application build in labview 8.5 for Windows XP using NI Visa functions to interact with hardware , how to make is work in Windows 7 32 bit and Win 7 64 bit

I have a application build in Labview 8.5 which wroks fine with Windows XP , this program uses basic read /write functions of NI Visa to communicate with Hardware . This application doesnt work with Windows 7 32 bit/64 and Vista . What changes i need to do to make it work for the said operating system

srinivas wrote:
Sorry for confusion ,
My question is what changes i need to do in code or while making the installer to make the existing program work with other Windows operating system
You need to make sure the machine have the corresponding NI-VISA installed. Check in the NI software pages for the right version.
Also make sure that the com port's can be selected when you first start the application. Eg. if you refer to VISA "COM1" on the XP machine It might be "COM2" on the Win7 machine.
Br,
/Roger

Using dynamic VI referencing in combination with Application Builder

Hi.
In this thread (http://forums.ni.com/t5/LabVIEW/How-to-access-a-known-control-in-a-VI-reference/td-p/1255244) I attempted to modify our under development test system, so that we didn't have to change the same main VI for every test that we are adding, since we are several persons who'll be adding tests (i.e. conflicts would arise, that we would have to iron out manually every time). The solution in the thread above works very well, by opening a reference to the test sub VI and calling the reference. I then can pass data to the sub VI, and can get the test results from the sub VI. Great!
The problem came when running the program through the Application Builder. The test system starts up fine, but the above method fails miserably, since the sub VI files are no longer there. It seems that the sub VI's are not a part of the exe binary file coming from the Application Builder.
So I'm drawing a blank here. Does anyone have a suggestion on how to to this? I'm only seeing the two options. Either adding the sub VI's in the same main VI file, but then we have to be very careful on not getting conflicts (or fix the conflicts manually when they arise). Or use the dynamic VI referencing, but then the system doesn't work with the Application Builder (which means that this method is out). Is there a third method of doing this?

Hi Mike.
I use LabVIEW 2009.
Well, I actually *can* use the dynamic call solution now. The problem was that (1) the files weren't included in the exe file (fixed by adjusting the Application Builder settings), and (2) the Check if File or Folder Exist VI doesn't work if I try to check if the sub VI is present inside the exe file. The solution here was basically to ommit the whole Check if File or Folder Exist VI, and just do an error check on the Open VI Reference VI. The Open VI Reference VI will fail if trying to open a reference to a file that doesn't exist, so I just wired that to a case loop around the Call By Reference VI.

Building an application that uses Daq-mx cards

hi,
I'm using Labviex 7.1 to develop an apllication that uses a couple
of Daq-mx cards as well as a few RF instruments. The
2 cards are for the moment in the computer I use to develop
my application. My problem is that when the application will be over, i
have to remove Labview from the computer to let the License free.
That's why i used the application builder to make a .exe with my app.
The .exe file works without problems on the computer with labview. I
then installed Labview runtime 7.1.1 on an other computer to try my app
on a computer where labview is not installed but this time it doesn't
work as a lot (more than a dozen) of DLL seem to be missing, almost all
the library that deal with the Daq-mx.
Do I have to install the cards on the computer on wich i want to test
the application ? Or maybe only the drivers of the cards ? Maybe some
of you have already faced this problem and can help me ^^
Thank you in advance and see you soon in the forum
P.S. It's gonna be quite hard to show youthe program as the computer I use to develop is not connected to the network
Message Edited by Xavier Pajona on 07-29-2005 08:08 AM

This may not help the issue you are having, but starting with NI-DAQ 7.4 you can simulate many of National Instruments' DAQ, tell Measurement and Automation Explorer ("MAX") that they are installed. This has solved some of my "develop on one machine, deploy on another" problems, which as a consultant seems to happen a lot.
P.M.
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

How can I build a LabView application that uses the 2012 runtime, on a development system with LabView 2013 or 2014 installed?

I need to build a LabView application .exe to run with the 2012 Runtime, for legacy support. I currently have LabView 2013 installed on my development system, and have 2014 available. How can I build an application that uses the 2012 runtime on this development system? Do I have to downgrade to 2012? Thank you.

We have existing customers that have installed our application that was originally built with 2012 (provided by a contractor that is no longer available). Due to IT regulations, it is far easier to update these customers by simply replacing the .exe file, than creating an install that their IT department must run.
If I have to downgrade to LabView 2012, where can I get the installation for this?

How to submit my builds using Xcode 5.1.1 or later, or Application Loader 3.0 or later?

I am using Apple Developer to make an app. How can I submit my builds using Xcode 5.1.1 or later, or Application Loader 3.0 or later?

The controls in your screenshot are Mac controls, not iOS ones. If you have an iOS project, you can't access those controls. If you want to access those controls, create a Cocoa application project and select the xib file Xcode creates.

Using JMF source codes to build applets........

hi anybody tried to use the source codes to build an applet
that installs/creates JMF registry or its fuctionality on client side make JMF use with no need to install on client side.
if anybody have any idea's abt this please help me...
or please give any references about the same..
thanks

This was announced in November.
Unfortunately after May 1, you’ll need to have a full DPS license or know someone that has one, in order to create or update Single Edition apps.
There are several threads on this topic already. Here's one: The end of DPS Single Edition

Application builder (using OpenG source)

Similar Messages

Maybe you are looking for