Build specifications menu empty

Hi there,
Im currently trying to create a dll from a Labview project, following the instruction from this webpage : instructions on creating a dll from LV.
My problem is, when I right-click on "Build Specifications" I only have one item to choose from the "new" menu, which is "Source distribution".
How can I get the other options ? (I had the same frustrating problem when I tried to create an executable file).
My version of LV is 11 btw.
Thanks in advance for any help

Hi Johndoe77651244,
Do you have application builder installed into your computer?
You will need it to create a dll.
More information of application builder can be found from the below link,
http://sine.ni.com/nips/cds/view/p/lang/en/nid/210592
Best regards,
TuiTui

Similar Messages

Build specification Destination Does Not Preserve Hierarchy

I have a destination configured in my build specification (application) so that I can include required LabVIEW and non-LabVIEW files in my builds. This destination is configured as a directory with "Preserve disk hierarchy" checked. Under "Source File Settings", I have one of the folders in my project configured to use the aforementioned destination.
There are two issues that occur when I build my application. The first is that it ignores empty folders entirely. The second is that I have one folder that contains files (this folder is a child of the folder that is listed in the build spec) and when I build, it completely ignores the child hierarchical step. I.e. It omits the child folder completely and put's the child folder's contents in the parent/top-most folder. E.g.:
Source:
source/ParentFolder/ChildFolder/file1.ext
source/ParentFolder/ChildFolder/file2.ext
Build Result:
builds/ParentFolder/file1.ext
builds/ParentFolder/file2.ext
If I put a dummy file (or another child folder with a dummy file) in "ParentFolder", it will then actually preserve the hierarchy of the files (empty folders are still ignored though). Note that the ParentFolder is "Always Included" under the build spec's "Source Files".
I need to be able to preserve the hierarchy without having to use a dummy file (this would be extremely confusing and could get deleted easily by future developers) or having to remove this hierarchical step in the folder structure (this code was inherited).
I'm using LabVIEW 2013 SP1.

Actually this has been discussed before -- a lot. The builder will not create an empty directory, and it only counts files as contents.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Build Specification does not include all files for my VI.

Hi!
As a part of a semester project i have build a VI to control a filtration unit. The VI is working fine on my computer, but I graduate next month and I have to deliver the files on to a person on the university. The problem is that even though i use the "Build Specification" function (i use LabView 2011 Professional Development System), files are still missing when the program is started on the new computer. A warning in the project file indicates that files are missing or removed to a different location. A file named pid.lib is not found, and it seems like the path to each file is the same as on my computer, but the build specification doesn't change that to fit the new computer.
I am a LabView newbe, and I have searced this forum and help files to try to solve this by my self, but now my time is becoming limited. Can anyone help me with this?
Henrik jepsen
Masterstudent Chemical Enginnering
Denmark
Solved!
Go to Solution.

Hi Henrik
You can see what versions of LabVIEW and which Toolkits is installed in Measurement and Automation Explorer (MAX). If you Open MAX, and Select "My System" --> "Software in the left menu, then you can see all software installed.
If you click on the LabVIEW installation. In this case LabVIEW 2011, you can see all toolkits installed.
When you run a LabVIEW project / application on another PC, LabVIEW will use a defined priority of where to load the files from. This is specified in Tools --> Options --> Path --> VI Search Path.
So LabVIEW will frist try to find the VI/VI library in the folder of your project and if the VI is not located there it will look for it as a build function in the vilib, userlib or instrlib folders of LabVIEW. These folders contains VI's and VI libraries installed with LabVIEW.
In this case, as mentioned above you properly don't have the same toolkits installed on both machines. Therefore the PID.lib is not found in the vilib folder as it should be, and thereby you get the error. You can confirm this by reviewing the installed modules as mentioned above.
Best Regards
Anders Rohde
Applications Engineer
National Instruments Denmark

Is it possible to build a menu as my 1st page and navigate back to it?

I am building a rather long form and would like to have a menu (TOC) as the first page so the user can go right to the desired section. I would then like to be able to use the Navigate to Page to allow the user to return to the Menu if they want to, or navigate using the PREV and NEXT buttons. The Navigate to Page only allows forward skipping. Is my only option to build my menu using html and embed the form code?

Hi,
>> I would then like to be able to use the Navigate to Page to allow the user to return to the Menu if they want to,
This is not something that we support right now. As you indicated, the Navigate to Page is for foward pages, not backward.
>> navigate using the PREV and NEXT buttons
I am not sure if I understand this correctly. You can always use the PREV button to get back to the previous page and as you go back, you will reach the first page, which in this case your TOC. We currently do not support going back to a specific page in one PREV click.
>> Is my only option to build my menu using html and embed the form code?
Navigate to Page for backward pages is not supported in embedded form. Are you trying to build different forms for each item of your TOC?
Thanks,
Lucia

Use of "Open FPGA VI Reference" function --- Build Specification vs VI vs Bitfile

When using the "Open FPGA VI Reference" function in a LV2012 cRIO application, there are 3 options: Build Specification, VI, or Bitfile. What would be the reasons for selecting one over the others? Does it affect the resulting startup.rtexe when the cRIO application is built? I searched through the help and in these forums, but I don't see criteria for selecting one over the others; maybe I missed it.

Hello Chris,
Apologies in advance for a long reply.
The reference method won't change the functionality of your rtexe.exe. They all end up dropping a bitstream, based on a bitfile, onto the cRIO's FPGA.
To a degree, the method used to reference the FPGA code is a matter of taste, but there are situations where one method is better suited than the others.
Reference by VI:
Setting the configuration options to open reference by VI is helpful during development when you are making changes to an FPGA VI often and building/testing using the same spec. When this option is used, a bitfile is selected based on the default build specification for the project. A project may have only one default build specification. You can make any build the default by checking the option under the Source Files category in the build properties. The default build is indicated in the project explorer by the green box around the builds icon.
Reference by Bitfile:
This option references a bitfile directly. Through the configuration window, you can select one specific bitfile to open a reference to (this is not dynamic and does not change unless you physically go make a change to that path). If you're using this method, it helps to give your bitfiles more meaningful names than the ones that are automatically generated by LabVIEW. When you run subsequent compilations off of the same build specification and do not change the bitfile nname or path in the build configuration, the old bitfile is overwritten and replaced with the new one. When you are using this option, it is critical that you keep up with which bitfile is the one you want to be using. There is an option now that will help alleviate any problems referencing by bitfile through the Open FPGA VI Reference function. There is a new VI called Open Dynamic Bitfile Reference. It is typically used when you want to chose a specific bitfile to load depending on something in your host code (a configuration option etc) - but it allows you to dynamically reference a bitfile on the block diagram by path.
Referency by Build Specification:
This option is good for when you want to always use a bitfile that is associated with/compiled with the same build configuration. Say you have two options for top level FPGA VIs in your project (each with its own build spec). Both of these VIs have the same interface (read/write controls, DMA) but they run different algorithms or something. This is nice because you can easily switch your host application between them by picking the build spec associated with the FPGA VI you want to use. In this type of sutation, referencing by VI is no good because you can only have on default build spec.
cheers.
Matthew H.
Applications Engineer
National Instruments

Encore no longer behaving when building a menu. Help!

I have creative suite 5 for iMac. Premiere works fine but when I want to build a menu in Encore and try to put Text into it, it announces a “General Error“ or "sorry an abnormal condition has been detected” and the screen goes “mad”. I’d be grateful for any help!

My guess is that you have a scope problem. By putting the button inside a movieclip you have made the buttons scope the same as that clip.
So if you add a trace inside the release event handler, what do you get?
trace("My current scope is: "+this);
I'm guessing it is "_level0.mc_anim_backdrops_menu," right?
So since you are using the global function of gotoAndPlay() it is looking for that label in the current timeline and not finding it.
You should probably use the MovieClip method and specifiy which timeline it should look in.
_root.gotoAndPlay("Why");
_level0.gotoAndPlay("Why")
_parent.gotoAndPlay("Why");
both would probably work. I would never use the first two, other than to make sure that there wasn't something else going on...

Instrument Control Build Specifications

Dear Sir:
      I am trying to build a working *.exe instrument control program. This is a simple program which only queries my test instrument with a *IDN? command.
      The program fails to call my instrument driver and the program also runs on boot up when (running under normal conditions) it should wait for me to input the GPIB address of my test instrument.
      Let's begin with the failure of Labview to communicate with the instrument driver.   This is some background information.
       When I run the program as simple *.VI in the Labview environment, the program runs perfectly.    No issues.
       When I use Agilent Connection Expert or MAX to communicate to the test instrument, communication is established and there are no issues - I receive a reply, connectivity is established.
        After I build the *.VI into a *.EXE program, this is where the program's issues arise.
       The *.EXE program fails to initialize correctly and fails to establish connectivity with my test instrument.
        Here are some issues that I have noticed about the program running in *.EXE mode
1) The program runs on "boot up" when you click on the *.EXE program.   In *.VI mode, the program does not run on boot but waits for the user to input the GPIB address of the test instrument - program run is designed to be enabled by the user.
      I do not believe this is the source of the problem but only an incidental consequence of the problem.   If I stop the program and input the GPIB address, I receive a message about not being able to communicate to the driver.
2) Once the *.EXE program runs, there is a condition whereby the operating system cannot close the program and WINDOWS itself cannot shut down itself unless I manually close all the programs associated with the *.EXE program in the WINDOWS operating environment.
3) If the labview program and *.EXE program are closed but the operating system is still running, Agilent Connection Expert and MAX can no longer communicate with the test instrument.   They no longer see the test instrument.
It is obvious that the *.EXE program is making a change which is causing the operating system to "hang" on shutdown and is also preventing the other programs from operating as they should.
I believe the source of my problem may be how I programmed my build specifications.     In reply, can you please tell me what are the minimum requirements for the build specification so that my test instrument can reply to a simple *IDN? query?   What files are normally required for a successful build?
Other information as to the source of my issues are welcome as well.
Thank you.
Solved!
Go to Solution.

Thanks for you advice.
I think this problem is a lot easier than you might think.   I just started using Labview and the *.VI is super simple. I am away from my development computer right now so I can't post it.
The information I need to know right now are the typical files that are needed to be added in the build.
I found this quote that I found on a webpage to be interesting, (although I am not building an installer):
" Do I need to include NI-488.2 2.7.3 module if I use only basic GPIB Write.vi and GPIB Read.vis in my project?
Yes, if you are making an installer ..."
This is a link to the webpage:
http://forums.ni.com/t5/LabVIEW/Uninstalling-LabVIEW-after-an-application-EXE-build/td-p/1553310
My program involves only simple reads and writes using NI-488.2 calls to a test instrument.   A simple list of files specified with filename extensions to get me started would be appreciated.

Labview project build specification

I created a LabVIEW8 project. WIthin it I have a few folders that organize my code. I'm trying to create a Build Specification (found at the bottom of the project view). I created a new Build Spec and began populating it. I can add information to all fields, except the Source Files category. When in the Source Files category I'm able to specify the Dynamic VIs and Support VIs in the bottom box by selecting Full OI - Top Level VI.vi. However, when I try to select any single file (Launcher.vi in this case) as the Startup VI, all my VI files become grayed out. I can't select any of them. I tried placing my launcher file in a new folder (apart from the majority of my code). It allows me to move the folder into the Startup VIs area, but when I say 'OK' or 'Build' at the bottom, it comes back telling me that it can't continue because I haven't selected a Startup VI. Any ideas?

Have you tried saving the project and trying again. I tried to create one on the fly and it wouldn't allow me to select it as a top level VI until I saved the project and the VIs in the project. Give that a try and let us know how it goes.
Tyler H.
National Instruments

Scrambled destination view in installer build specifications LV8.5

I don't think this build specifications bug has been mentioned yet. I am using LV8.5 Pro under Win XP.
When configuring a new installer build specs, under Source Files, I select my application item in the Project View and click on the arrow button to add it to the Destination View. The latter then faithfully reproduces the application files hierarchy, for example:
Application Directory
    Manuals Directory
       Manual.pdf
    Application.exe
    Application.ini
    Startup.exe
    Startup.ini
However, after I close and reopen the installer properties, the Destination View hierarchy appears scrambled, for example:
Application Directory
    Manuals Directory
       Startup.ini
    Application.exe
    Application.ini
    Manual.pdf
Supporting files get moved around the directory tree, some disapper, and others actually appear in duplicate. The outcome is exactly the same every time I repeat this process, but there is no apparent pattern to it.
Now, when I actually build the installer and later use it, the application gets installed properly, with correct files hierarchy. What doesn't work are the shortcuts. For instance, in the above example, if I create a shortcut to Manual.pdf, it will actually point to Startup.exe. And if I need a shortcut to Startup.exe, I cannot create it because the target is not part of the Destination View.
Thoughts?

Dear Zador,
Bug number 4CM921LJ titled "Shortcuts Added in Installers Are Not Created Properly" is a LabVIEW 8.5 Known Issue. More information on the bug can be found in Knowledge Base 4EGEL6HY: Wrong or Incorrectly Disabled File Names Displayed in LabVIEW
8.5 Installer Builder. If you need an alternative to the workaround presented in the Knowledge
Base, you can create separate folders for each file you need to have a
shortcut created for instead of putting them all in one.
This issue has been fixed in LabVIEW 8.5.1. Please post back bug 4CM921LJ does not describe your problem.

Programmatically Changing Build Specifications from command line

I use a batch file that calls a VI to build several LV projects. I found the article http://zone.ni.com/devzone/cda/epd/p/id/5051 to get started and build projects; however, I was wondering if anyone has been able to change build specifications without opening the Application Builder dialog? -> I would like to build an app. with a version number using the command syntax: labview.exe <mybuild.vi> -- "project1.lvproj" "version number"
Any thoughts regarding this problem?
Thanks,
Adam

I have done some research and there doesn't seem to be a way to change the version number when building a project with this method. If I find out otherwise I will post to let you know but I don't think it is possible. I would look for another way to accomplish what you want by incorporating the version into the file name or something like that.
Eric A.
National Instruments
Distributed I/O Product Support Engineer

RT Build Specifications: Component Definition Category is unresponsive

Hi,
I am using LabVIEW 2013 SP1 f2, with Real-Time 13.0.1
When I open the Properties page for a Real-Time Application build specification (to run on a cRIO-9075), and select the Component Definition category, I find that the following occurs:
- LabVIEW becomes unresponsive, and thinks for a while. It takes approximately 20-30 seconds or so to finally show the Component Defintion page.
- When I click on Create a component definition file (.cdf), nothing happens. As I write this, I see "Required software components", and then these are greyed out: "Software component description", and "Software version" - but there is nothing to select or change?
- If I click on another category, it takes in the order of 20 seconds to finally show this category.
- To close the build spec (by pressing OK), it also takes a long time (more than 60 seconds).
- Things are fine with the build spec if I never enter the Component Definition category.
Is anyone else experiencing this?
Any help would be appreciated.
Christopher Farmer
Certified LabVIEW Architect
Certified TestStand Developer
http://wiredinsoftware.com.au
Solved!
Go to Solution.

Hey Chris,
I believe the following patch is the fix that you are looking for.
LabVIEW Real-Time Module 2013 SP1 Application Builder Patch Details
http://digital.ni.com/public.nsf/allkb/D72B45C6905D327A86257CC800547992?OpenDocument
There's a link to download the patch at the bottom of that page.
Regards,
Ryan

Missing Build Specifications in LV8 Full Development package

After installing LV8 Full Development Version, the only Build Specification option available is "Source Distribution". The options "Application", "Installer", "Shared Library" and "Zip File" are missing. The correct serial number appears on the About screen so I assume I activated the package correctly.
How do I make those other build options available?

Buy the application builder - or upgrade to the professional version...
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Some build specifications change on different machines

Hi all,
I often need to move my LabVIEW projects from a machine to another one. In this cases, I copy all the contents of my project folder in the new machine.
My projects are built without errors, but some build specifications are not kept.
Build specifications that are not maintained are additional installer list (see attachment).
In the machine 1, I include only Math kernel Libraries and NI VC2008MCMS.
When I open the same project on the Machine 2, all the elements in NI LabVIEW Run-Time engine 2012 SP1 f3 list are checked. (see attachments)
Thank you
Attachments:
machine1.png ‏5 KB
machine2.png ‏5 KB

Hi AC_85,
have machine 1 and machine 2 the same installed software? Is it the same version? Maybe on the machine on which you copy your project some additional installer is not installed.
You could try to Duplicate the entire project (from project explorer File >> Save as >> Duplicate project >> Include all dependencies) before moving it from machine 1 to machine 2.
Hoping this will help you.
Best Regards.
Cla_CUP
NI ITALY

Exporting build specifications to other project

Hai all,
I have created the build specification for developing a exe in my project. There are too many destination directories am creating in the project and its a lengthy process too. Is there a way to export the build specifications (of a exe) to another project and reuse the specification there.
I am using LabVIEW 8.5 Professional development system.
Previous versions of LabVIEW has *.bld file that can be called while creating new exe's is there any such option in 8.5
With regards,
JK
With regards,
JK
(Certified LabVIEW Developer)
Give Kudos for Good Answers, and Mark it a solution if your problem is solved.

Hi JK,
you can open your project file with a normal editor. It is a xml file. There is an item with name = build specification. If you copy this part to another project, then it shall be possible to use it there.
Hope it helps.
Mike

Build Specifications gone with LabVIEW 2009

I'm using LabVIEW 2009 and I still have the same problem as described in the following post (where all the answers were for older LabVIEW versions):
http://forums.ni.com/t5/LabVIEW/build-specifications-gone/m-p/625815
When I move a LabVIEW project from one PC to another, parts of the build specifications are gone. In the specification for the executable I have to redefine the start-up VI, the included files and the icon.
Is this a known issue and is there a fix for it?

Hello,
this might be a corrupt project file. Does this only happen with this project?
If so, then I'd suggest recreating the project and the build specifications on the original PC and trying to migrate it again to the other PC.
Regards,
Joseph Tagg

Build specifications menu empty

Similar Messages

Maybe you are looking for