| 202 |
bj |
1 |
// $Id: README_MSVC 202 2005-12-19 08:39:17Z bj $
|
|
|
2 |
//
|
|
|
3 |
Building instructions for GEL under Visual Studio 7.1 and 8 (2003 and 2005)
|
| 39 |
bj |
4 |
|
| 202 |
bj |
5 |
1. Project configuration
|
|
|
6 |
|
|
|
7 |
We use MPC to maintain .sln and .vcproj files, since the format of these files changes with each new version of Visual studio. The average GEL-user need not bother with this, since .bat files have been created to ease the use.
|
|
|
8 |
|
|
|
9 |
More info on MPC can be found on:
|
|
|
10 |
http://www.ociweb.com/products/mpc
|
|
|
11 |
|
|
|
12 |
Note that Perl must be installed to use MPC.
|
|
|
13 |
|
|
|
14 |
2. Subsetting
|
|
|
15 |
|
|
|
16 |
The use of MPC allows relatively easy creation of subsets of GEL. An example subset is created using the file build_vc71_solution_CGLA.bat creates the subset .sln and vcproj files using MPC and the Perl script makefiles/CGLA.pl which deletes all non-CGLA source code from GEL.
|
|
|
17 |
|
|
|
18 |
3. Build Configurations
|
|
|
19 |
|
| 114 |
jab |
20 |
Each project contain three configurations: Debug, Release and
|
|
|
21 |
Install. Debug and Release have the usual functionality, while Install
|
|
|
22 |
is special.
|
| 39 |
bj |
23 |
|
| 114 |
jab |
24 |
We assume, that once GEL is installed, it should be used without
|
|
|
25 |
adding the source and header files to the particular project.
|
| 39 |
bj |
26 |
|
| 114 |
jab |
27 |
Therefore we install GEL in an outside directory defined by the
|
|
|
28 |
environment variable GELEXT. In the configuration, this is done by
|
|
|
29 |
setting the Target Directory to
|
| 39 |
bj |
30 |
$(GELEXT)\lib\windows
|
|
|
31 |
|
|
|
32 |
and, as a post-build event, all header files are copied to
|
|
|
33 |
$(GELEXt)\include
|
|
|
34 |
|
| 114 |
jab |
35 |
The GELEXT variable should be the path where all 3rd party lib and
|
|
|
36 |
header files are stored (like /usr/local/ on a *NIX system)
|
| 39 |
bj |
37 |
|
|
|
38 |
|