how to make .exe file ?

J

jaffar

New Member
i made one application using appbuilder but i need to make a .exe file of that application so that i can run it in client machine ,so can u pls tell me the steps to create .exe file..



openedge 10.2b
win xp sp2

Thanks in advance
 
You can't create a .exe in Progress. The machine will need a runtime install of Progress, and will need to have things like the Propath set up. You can supply the machine with compiled code as individual files, or as a procedure library (a bit like a dll).
 
jaffar said:
i made one application using appbuilder but i need to make a .exe file of that application so that i can run it in client machine ,so can u pls tell me the steps to create .exe file..



openedge 10.2b
win xp sp2

Thanks in advance
Click to expand...

I strongly suggest you download the 10.2B documentation, and read the Managing ABL Applications manual. It discusses your options for compiling and deploying your code. You might also want to look at ABL Essentials. As Cringer said you don't compile to native executables in ABL. You compile to .r files (r-code), which are run in a Progress runtime client that is native to the platform. In Windows there is a character-mode client (_progres.exe) and a GUI client (prowin32.exe). On other platforms there is a character client (_progres).

If you run showcfg in a proenv window you can see which particular OpenEdge products are installed on your system. You need a deployment product like Client Networking to run your compiled code. Then you can create a shortcut with a command line like: d:\progress\bin\prowin32.exe -p myprogram.r.
 
In that aspect Progress is similar to Java: You don't build an executable - instead you compile your sources into byte code that gets interpreted by a virtual machine. For Progress/OpenEdge it is the AVM ( ABL Virtual Machine ) as it would be the JVM for Java. For both you need a run time installation in order to be able to have your byte code executed.

Progress provides to virtual machines:

  • prowin32 - the GUI 32 Bit executable, available on Windows only
  • _progres - the ChUI 32 or 64 Bit executable depending on the Bitness of your installation which is available on every supported plattform ( *nix )

At a minimum you would start your application calling the virtual machine with the -p parameter pointing to the start ABL procedure ( %DLC%/prowin32.exe -p your_procedure.p , where DLC is the environment variable pointing to your installation directory ).

I can only agree with Rob in strongly recommending you to read the documentation in order to figure out what your deploying options are.

Furthermore, it would be helpful to give you a more detailled
 
information about the Progress/OpenEdge version you are using and on which plattform ( OS ) you want to run your application.

Heavy Regards, RealHeavyDude.
 
You must log in or register to reply here.
Back
Top