To build exe file?

Hi every body,
I want to make the exe file. I know how to create the executeable jar file.
In programme, I have used some properties file. Therefore my exe file should consists of jre,some properties file and jar file.
I have found a no. of tools like JExecutor, Launch4j, inno setup, JCreator, JSmooth, Java Launcher. But I could not find the tutorial. Can any body recommend me the open source tool (*Most important is tutorial defined in steps*) to make the exe file?
Thanks in advance
Best regards

DrLaszloJamf wrote:
georgemc wrote:
Common Java misconception #4783: deployment as a Windows binary is desirable
Don't bother, unless you've got a really compelling reason to. Just deliver jars
[Here's a disturbing jar|http://www.shikasuki.com/images/np_pink_jar_med_SSWM.jpg]
Nice. Reminds me of the now-defunct bonsai kitten website. Only with little girls

Similar Messages

After build exe file . the config.ini file change the path

i have config.ini in my proj
after build exe file i get that error
Error 7 occurred at Open VI Reference in Open Config.vi->Start Main.vi.
VI Path: C:\IRP Burn SW\Labview Proj\EXE Build\SWDL.exe\IRP Burn SW\Labview Proj\configuration.vi
in my proj configuration file locat in : C:\IRP Burn SW\Labview Proj\Config File\config.ini
how can i solved this problem ?

http://digital.ni.com/public.nsf/allkb/FD7DE8BC8FFC256C862565F4006BE363

Building exe file fails (not enough memory) in LV 2011

Hello,
I have a project with about 900 VIs. I'm using Win7 32 Bit with 4 GB RAM (a 32 Bit OS can address about 3,3 GB) with LabVIEW 2011 SP1.
When trying to build an executable, I allways get the error "Not enough memory to complete the operation" (or something like that).
My RAM is full at this time.
Without building the exe file I can start the project without any problems and with only half RAM usage.
What can I do to generate the exe file with my system?
Are there any options I can set, that the application builder will not use so much memory?
Regards
Matthias

Hello
"how much memory do those 900+VIs take on disk????"
53 MB
"Ctrl+Run Button is a force compile for a single VI"
I used Ctrl + Shift + Run
I also tried the mass compilation tool itself and it doesn't change anything.
"If the source distribution also plows the memory, you want to split the distribution into several packages"
That sounds very coimplicated ...
Did I understand it correctly? I have to create several source distributions (option "directory" and not "llb"). And in my build specification for my exe file, I can chose these source distributions?
Do I need to prepare my VIs or can I directly create the source distribution with the option "remove block diagram"?
"I had that problem several times in a large project. I did a mass compile, saved all the VIs, then closed out of the project and LabVIEW. I opened up LabVIEW again and loaded only the main VI. I performed a build and it worked successfully."
I tried it and a still get the same error.
My customer need to get the update because it a critical one. And I can't build it.
An update to Win7 64 bit on my machine is also not a solution because all our customers use Win7 32 bit and the 64 bit executable won't run on a 32 bit operating system.
Regards
Matthias

Can go back the Main VI after build exe file (by Application builder)

Dear all,
I am writing some vi similar to the vis below.
It work properly at the vi mode, but after I build it to a exe file
(by Application builder). I found when it go back to Main Menu from
Sub Menu, it will close the vi automatically.
Can anyone tell me how to slove this problem?
Here are the vis.
Attachments:
mainmenu.vi ‏31 KB
submenu.vi ‏11 KB
Menu&SubMenu.exe ‏63 KB

Hi,
The problem is that the executable closes the first window, because there is
no reference open to its front panel. A solution might be to pass the
reference of the main VI to the sub VI.
You can also use FP.state iso FP.open. This alows you to hide the front
panel, without automatically closing the vi. I'd prefer this over the first
solution.
Regards,
Wiebe.
"MusicIsLive" wrote in message
news:[email protected]..
> Dear all,
>
> I am writing some vi similar to the vis below.
> It work properly at the vi mode, but after I build it to a exe file
> (by Application builder). I found when it go back to Main Menu from
> Sub Menu, it will close the vi automatically.
>
> Can anyone tell me how to slove this pr
oblem?
>
> Here are the vis.

Labview- Excel template path at run time(to build .exe file)

I am new to labview and I have one doubt in it. I have one main.vi file where I use local drive path to invoke one excel template, Now I have to convert this .vi file in to .exe file. So now I cannot give the local drive path to invoke the template because the client will not have the same path as mine. So what I did is I created one project. Under this project I created one virtual folder which contains the excel templates. My doubt is how to give path for the excel-template in main.vi file. Please let me know if you guys know. thanks in advance.
Thanks & Regards
saamy

Hi again.
Here is a strategy I always use when I create a project:
Create a folder named for example "My project". In this folder I create new folders called "Bin", "Doc", "Data" and "Img". I put my main Vi in the "Bin" folder and for example the excel template in the "Data" folder.
I then create a project in LabVIEW and I add the "My project" folder into this project as an autopopulating folder. This means if I add a file in i.e the "Bin" folder it will automatically come up in the project.
When I create my Main.vi and want to use the excel template, I simply add a folder path constant to the "Data" folder on my computer. I don't care about the LabVIEW project file.
After I'm done programming and I'm happy with the result I need to prepare the VI for being converted into an .exe file. This means I have to remove all the path constants and add the application folder node mentioned above. I have to know what folder hiearchy I want the installer to create. In this example we can use the folder where the .exe file will be and then a sub-folder named "Data" where the excel template will be. The path will be like "the_folder_where_the_exe_is\data\exceltemplate.xlsx."
When I create the .exe file I can add which files that will always be included. Here I add the Data folder containing the excel template. After that I create an installer where I add the folder where the exe file is, which I just created.
Regards,
Even
Certified LabVIEW Associate Developer
Automated Test Developer
Topro AS
Norway

Problems in using Application Builder to Build a exe file with Report generation Toolkit

Hello,
It's my first time to build exe. But I have Problem when the VI have Report Generation toolkit VI.
It's no problem in VI Format , But It can't work when I build as EXE format
Can Anyone help me, and state step clearly in how to solve the problems?
Thank you!!

If the code works OK in the development system but not in an executable there are a few things you can check. The two most likely causes are:
There is an error occuring that your code isn't reporting.
There is a file path that under the executable isn't valid.
First make sure that all the error clusters are daisy-chained together in the subVI that you wrote to create and populate the excel file. Next make sure that the end of that chain goes to an indicator on the VI's front panel.
Second, make sure there are indicators on other key parameters like the path the file is trying to write to.
Third, temporarily modify the VI properties of that excel IO VI to open it's front panel when called, and rebuild your application. The next time you run the application the front panel will open when you try to write to the excel file and you should be able to see what is happening.
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

Does anyone know how to build an exe file of a complete dsc system ?

Creating an exe file of a VI that uses dsc components is not that difficult, although it could be easier. But, I also use vi-servers to communicate with the tagengine, and this is where I fall short. The document "viserver.pdf" located in the labview\manuals folder, describes how to create, develop and test VI-based servers using vis from the DSC Server Development
palette. But how should a vi-server be handled when used with an application that among other things uses a taglist (scf file) that requires certain vi-servers to run to update tag values etc. I have found that one option is to include the vi-servers in the "LabVIEW DSC Run-Time System 7.0", register them there and include all vis needed f
or them to run in subfolders of the "LabVIEW DSC Run-Time System 7.0". Servers will not load vis from the \vi.lib folder nor from \user.lib or any other \labview 7.0 folder. Can these servers instead be created as exe files, and how can this be done ?

Soren,
sorry but it's not possible to build an executable from a vi-based server. You need to distribute this type of server as an llb. Please follow this link to the NI knowledge base for more information:
http://digital.ni.com/public.nsf/websearch/082B10137820BF5886256C250062DBB4?OpenDocument
The document is not very specific which options you should use when you save your server vis but I assume it should be "Application Distribution".
Best regards,
Jochen Klier
Applications Engineering Group Leader
National Instruments Germany GMbH

File location surprizes when building .exe

Hi,
I'm working on a project which I'm saving to my "D:\Documents and Settings\My Name\My Documents\Customer\Project" folder. The project contains VIs located in "\Project" and a couple of DLLs located in a '\Project\api' subfolder. When I build an installer using Application Builder which installs the project to "C:\Program Files\Project", the resulting .exe file that I launch looks for the DLLs in "D:\Documents and Settings\My Name\My Documents\Customer\Project\api" and prompts me to find the files. I configured Application Builder to install the DLLs in "C:\Program Files\Project\lib" folder during installation of the project.
I don't want the .exe to look for the DLLs in the "\Projects\api" folder. I want the .exe to automatically find the DLLs in the "C:\Program Files\Project\lib" folder without asking me. How can I do this?
Is this an Application Builder problem or a LabVIEW problem?
Thanks.

I guess you forgot to include the DLLs in the EXE. Please post back if my assumption is wrong.

Project Builder Can it be run as an Exe file at any PC?

Dear Sir,
I am planning to make a Project based on my Forms(fmx) and Reports(Rep), database Schema, etc as a whole in a Project.
Now the question is that Can this project be treated a an Exe file and can be Installed on any PC and shall it work without install Developer(Deployement version) and Personal Oracle(8 or higher)..?
Please advise in me What options we have in Project building and what are not?
I search lot through net but could not find Enough material.
Thanking you in advance.
Sayeed

As for as I know, you cannot do the task with the project builder which you'r supposed to do. You cannot create exe file containing FMBs and repoets etc. with the Project Builder to run on another PC.
The project builder is used to manage the modules FMBs, MMBs, Plls etc.

Build an exe-File with jre

Hi,
is there any possibillity to build a file which I can execute on windows machines with no JRE?

hehe, use C++
Well, I could call up a couple of ways but it depends on your intention of what you want to do with it:
is it a downloadable program?
or is it a CD-ROM distributed program?
if it's a CD-ROM distributed program, there is a way to put java.exe and javaw.exe and all the libraries onto the CD-ROM and then execute it from CD-ROM without installing it.
If it's a downloadable version... well I would suggest for windows computers to use jview and have the program 1.1.8 compatible.

Upgrading from Luna to Marse our ant build scripts stopped creating the launcher exe files

Hi,
I upgraded our product to Mars from Luna but when i now kick off our ant script that produces the our product (from all the targets that we want so windows 32/64, linux and macosx (now with mars only 64 bit))
It does create the zip files that has all the plugins and so on.
But no executable, (which should be in our name servoy.exe and servoy.ini)
We only have a eclipse.ini (so not the launchers name) and no exe file what so over.
If i run it from eclipse product file/editor itself (so export product) then it works.
Any idea where i need to search?
In our script we call this:
<ant antfile="${eclipse.pdebuild.scripts}/productBuild/productBuild.xml" />
to get the product build started up. As i said in Luna this all worked just fine.

Hi,This typically happens if there are no specific platform objects
available. I think you miss the platform specific components.
see:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=419246
https://bugs.eclipse.org/bugs/show_bug.cgi?id=419246#c28
https://bugs.eclipse.org/bugs/show_bug.cgi?id=419246#c54
http://stackoverflow.com/questions/4261866/eclipse-rcp-how-to-download-delta-pack-from-software-site-in-the-target-definit
>
> I upgraded our product to Mars from Luna but when i now kick off our ant
script that produces the our product (from all the targets that we want so
windows 32/64, linux and macosx (now with mars only 64 bit))
>
> It does create the zip files that has all the plugins and so on.
>
> But no executable, (which should be in our name servoy.exe and servoy.ini)
> We only have a eclipse.ini (so not the launchers name) and no exe file what
so over.
>
> If i run it from eclipse product file/editor itself (so export product)
then it works.
>
> Any idea where i need to search?
> In our script we call this:
>
> <ant antfile="${eclipse.pdebuild.scripts}/productBuild/productBuild.xml" />
>
> to get the product build started up. As i said in Luna this all worked just
fine.

Need assistance to build EXE or HTA file

I worked for a company that when WinPE booted from a boot.wim file, it executed an exe file that essentially gave options to Boot to WDS, open CMD, Map Network Drives, Migrate User Profiles, etc. I want to develop something like this for the company I work for now. I am not a programmer (hence my posting here) and am looking for assistance and/or pointers to get me to achieve my task.
Any help will be appreciated.
This topic first appeared in the Spiceworks Community

We need users to be able to use the virtual machines we create for them and install on their local workstations but not create their own.The VMs will run locally so they can access them from a console without having a connected network between them and because the hardware and licensing costs of hosting them on redundant, highly available servers with the same performance level is so much higher than running the VMs locally on the individual workstations that they will already be using.I see that with VMWare Workstation, you can create "restricted" virtual machines where settings changes are locked with a password.https://www.youtube.com/watch?v=ybpY9YOxSW0However, to use a restricted VM, the user must use VMWare Player Pro (or another copy of VMWare Workstation). Unlike the free version of VMWare Player, VMWare Player Pro includes the...

Creating a link on exported exe files

I have 9 separate projects I need to burn to a CD. I have
created an html menu. I am exporting each of the 9 projects as
stand alone exe files, each one automatically opening the next one.
But at any given time I would like the viewer to be able to exit to
the main menu. Should I just put a button linking to the main menu
on every single screen of a single project, to allow the user to
exit to the menu if they want?
FYI, I had initially created the 9 projects as html files,
linking to one another. I posted a message about that earlier. But
I am running into browser issues and don't want to run that risk
with the completed CD. Help! :)

Hello Captiv8r and others,
This thread is pretty interesting. I have been struggling
with creating a project using Captivate 3 that will
reside fully on a CD. I am looking at maybe three workflows
for this, one using exe files, one using swf files and an html page
which serves as a "menu page" (the Captivate Menu builder just does
not have enough options, in terms
of graphic display, buttons, etc.), and the last one (which
is the hardest), using some sort of Flash container, a Flash
loader, and some menu buttons built in Flash, that call up
Captivate created swf files, etc. So far we have not had to track
state. I am trying to develop a training course on MS Excel, and am
using audio and Captivate for screen shots, mouse movements, etc.
After all the BS above, I do have a question. Is there a
reason to publish to an exe file in Captivate? Or what is the
reason(s) to publish a Captivate project to an exe file in the
first place. I have searched around for the answer on this, but
have found no good answer on this. Perhaps those of you more "sage"
Captivate users can provide some insight.
Thanks again for a very helpful forum,
eholz1

Excel invalid path in exe file

Hi,
I have an issue with my application I'm using the report file generation tool to read data from an excel file and I receive an error
"Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on UNIX."
when I open my xls file I was told that it is because the path in the exe file doesn't match the path during devellopement, in the exe file it seems to point to a dll file.
Does anybody have a solution?
Thank you
Olivier

Hi,
Does your program work fine in the development system, and the problem occures after building an exe-file ?
If that.s the case, I have had a similar problem. I solved it by adding some of the VIs in the _excelsub.llb located in "C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\addons\_office" to my project and then to "dynamic VIs and support files" in the build specification. I could not add the complete llb because some of the VIs where broken (maybe some issue with my installation.. ). If you look trough the code in the report VIs you use you find the VIs that are dynamicly linked and therefore have to be added to the build.
Good Luck !
/Sture

Build EXE error in excel dispose report

I have seen much discussion about path-relative-to-current vi problems when building EXE apps.
I am compiling an EXE which happens largely successfully, but when it encounters the Excel Dispose Report vi at the end of my Excel report creation section, it stops with 'error 7 at open vi reference in Dispose report ...excel quit vi ... file not found'. It works without a problem in the un-compiled version. I am just using the standard Excel Dispose Report vi out of the report generation library.
Can anyone enlighten me about how to clear this problem?
Fred

Fred,
Did you include the dynamic VIs? See: http://digital.ni.com/public.nsf/allkb/C38CE3F30542D65B86256F0E00740DD8
More confirmation it is dynamic VI issue: http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

To build exe file?

Similar Messages

Maybe you are looking for