| Line 1... |
Line 1... |
| 1 |
// $Id: README_MSVC 213 2006-04-12 07:43:07Z sda $
|
1 |
// $Id: README_MSVC 258 2006-08-15 11:39:34Z bj $
|
| 2 |
//
|
2 |
//
|
| 3 |
Building instructions for GEL under Visual Studio 7.1 and 8 (2003 and 2005)
|
3 |
Building instructions for GEL under Visual Studio 7.1 and 8 (2003 and 2005)
|
| 4 |
|
4 |
|
| 5 |
1. Project configuration
|
5 |
1. Project configuration
|
| 6 |
|
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.
|
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 |
|
8 |
|
| 9 |
More info on MPC can be found on:
|
9 |
More info on MPC can be found on:
|
| 10 |
http://www.ociweb.com/products/mpc
|
10 |
http://www.ociweb.com/products/mpc
|
| 11 |
|
11 |
|
| 12 |
Note that Perl must be installed to use MPC.
|
- |
|
| 13 |
|
- |
|
| 14 |
2. Subsetting
|
12 |
2. Subsetting
|
| 15 |
|
13 |
|
| 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.
|
14 |
The use of MPC allows relatively easy creation of subsets of GEL. An example subset is created using MPC and the Perl script makefiles/CGLA.pl which deletes all non-CGLA source code from GEL.
|
| 17 |
|
15 |
|
| 18 |
3. Build Configurations
|
16 |
3. Build Configurations
|
| 19 |
|
17 |
|
| 20 |
Each project contain three configurations: Debug, Release and
|
18 |
Each project contain three configurations: Debug, Release and
|
| 21 |
Install. Debug and Release have the usual functionality, while Install
|
19 |
Install. Debug and Release have the usual functionality, while Install
|
| Line 23... |
Line 21... |
| 23 |
|
21 |
|
| 24 |
We assume, that once GEL is installed, it should be used without
|
22 |
We assume, that once GEL is installed, it should be used without
|
| 25 |
adding the source and header files to the particular project.
|
23 |
adding the source and header files to the particular project.
|
| 26 |
|
24 |
|
| 27 |
Therefore we install GEL in an outside directory defined by the
|
25 |
Therefore we install GEL in an outside directory defined by the
|
| 28 |
environment variable GELEXT. In the configuration, this is done by
|
26 |
environment variables GEL_INCLUDE, GEL_LIB and GEL_BIN. In the configuration, this is done by
|
| 29 |
setting the Target Directory to
|
27 |
setting the Target Directory to $(GEL_LIB)
|
| 30 |
$(GELEXT)\lib\windows
|
- |
|
| 31 |
|
28 |
|
| 32 |
and, as a post-build event, all header files are copied to
|
29 |
and, as a post-build event, all header files are copied to
|
| 33 |
$(GELEXt)\include
|
30 |
$(GEL_INCLUDE)
|
| 34 |
|
31 |
|
| 35 |
The GELEXT variable should be the path where all 3rd party lib and
|
32 |
The environment variables should be the paths where all 3rd party lib and
|
| 36 |
header files are stored (like /usr/local/ on a *NIX system)
|
33 |
header files are stored (like /usr/local/ on a *NIX system)
|
| 37 |
|
34 |
|
| 38 |
|
35 |
|
| 39 |
IMPORTANT!!! Under Visual Studio 8 the following preprocessor defenition must be made to all projects using GEL, including GEL!!:
|
36 |
IMPORTANT!!! Under Visual Studio 8 the following preprocessor defenition must be made to all projects using GEL, including GEL!!:
|
| 40 |
Under debug configuration goto:
|
37 |
Under debug configuration goto:
|