Building a Standalone .exe 1

[Scott15239]

Okay,
Here's a really stupid question. I've got FPW 2.6 and the Distrib. Kit, and would like to know the proper method for building a standalone .exe. I must be doing something fundamentally wrong, because the only way I can develop a working .exe is to put it the root C:\FPW26 directory. What am I missing?

Thanks in advance for any aid!

 

[rgbean]

Create your project in a directory where ever you want - normally all your source files will be in this or it's sub-directories. When you fire up FPW, set the FP default to this directory, and the FP path to this and any sub-directories.

Rick

 

[JRB-Bldr]

Just to add a small bit to what Rick (rgbean) has already said.

To manage my own defaults, etc. I typically have a variety of small PRG files located within my C:\FPW26 directory. They contain lines like the following to establish the "defaults" for a particular application.

Example:
SET_CM.PRG

it contains:
* --- Return To Default Menu ---
SET SYSMENU TO DEFAULT

* --- Turn INSERT On & OVERWRITE Off ---
=INSMODE(.T.)

SET ESCAPE ON
ON KEY LABEL esc KEYBOARD "{esc}" PLAIN
ON KEY LABEL PGDN KEYBOARD "{pgdn}" PLAIN
ON KEY LABEL PGUP KEYBOARD "{pgup}" PLAIN

* --- Set Default Development Directory ---
SET DEFAULT TO C:\foxpro\col_mgr

* --- Set Default Development Data Path ---
SET PATH TO C:\foxpro\fp_26w; C:\foxpro\cm_mgr; D:\oakst\01

SET EXCLUSIVE OFF

You can have it contain whatever you need it to have. I just execute it from the Command window and it sets up everything that I need to begin a Development session.

Once you have created the Project for your application, you will click on Build. From there you are offered a number of options. Select Build Executable.

Good Luck,
jrbbldr
jrbbldr@yahoo.com

 

[Scott15239]

Do I need to include anything like foxuser or any of the environment files in the .exe's directory? For example, I want to create an executable application, burn it to a cd, then install it from there on a machine that does not have foxpro installed. Up to now I've generated the .exe's, putting them in the root FPW library, but of course FPW is already installed in the machine.

Thanks again for any help.
Scott

 

[rgbean]

Scott,
For your CD, you'll need not only your .EXE (and data), but also the FPW runtime file (FOXW2600.ESL) and it should have been patched with the High Speed CPU fix. In addition, if your application uses FoxTools.FLL or any special fonts, etc. you'll need to include them. If your application requires more variables (MVCOUNT) or memory limitations (MEMLIMIT), or specific locations for your temp files, it's good to have a CONFIG.FPW file.

It's always good to have a fresh non-FoxPro developement machine to test your install procedure on - then you'll catch (most) all the potential problems.

Rick

 

[JRB-Bldr]

If you are creating a CD you might want to consider tools like the following:

Freeware setup generator named -- CreateInstall
It will compress all the specified files into a single
SETUP.EXE file.
It is simplistic, but it works well.

http://www.gentee.com/

Freeware tool to build Autorun.inf file --
Autorun.inf Editor
So that your CD can launch an auto-install.

http://www.karenware.com/

NOTE: Remember that if you are creating and distributing a
commercial product, you will not want to be using Freeware
tools. Instead you should use their commercial tools (or
other commercial tools) so that you are not taking un-fair
advantage of these fine Freeware developers.

Good Luck,
jrbbldr
jrbbldr@yahoo.com