A similar question was asked in the APL2000 forum:
http://forum.apl2000.com/viewtopic.php?t=244
If you want to read about it here, the question was:
"I have programmed a model which I want to use on other computers, but
these computers do not have APL. That's why I'd like to make an
executable file of my model. Does anyone know how to do this?"
A good answer was proposed by Brent Hildebrand
"Everyone probably has their own pet way of making a APL+Win runtime
distribution, so here is my way. I take APLWR.EXE, and rename it to
the name of my program, say "MYPROG.EXE". I save my runtime workspace
as MYPROG.W3. I include APL20OCX.DLL. If you want to use the
APLUTIL.DLL or APLDRAW.OCX I include these. I frequently use APL+Win
as a COM object, so I rename APLWRCO.DLL as MYPROGCO.DLL and include
that file. And I include the APLWR.ADF renames as MYPROG.ADF for any
[]WCALL functions. I include a MYPROG.INI if desired.
So for a minimum, I have
MYPROG.EXE (alias for aplwr.exe)
MYPROG.W3 (my APL code)
MYPROG.ADF (alias for aplwr.adf or aplw.adf)
APL20OCX.DLL
and add the following as needed
APLDRAW.OCX
MYPROGCO.DLL (alias for aplwrCo.dll)
APLUtil.dll
MYPROG.INI
Note - you may want other files, data file, bitmap files, other
resources to be included in your distribution depending on your
needs.
Now, to distribute the program, I use INNOSetup (http://
www.jrsoftware.org), a free Setup utility which packages up all the
files as a single executable file. It can also make an uninstall
utility which will show up in Add/Remove program in the Control
Panel.
Note, I believe that the current APL+Win behavior is the same and
APL*Plus/PC, in that the workspace with the same name as the EXE gets
loaded."
|
