| 1 |
// author : bj
|
1 |
// author : bj
|
| 2 |
Building instructions for GEL under Visual Studio 7.1
|
2 |
Building instructions for GEL under Visual Studio 7.1
|
| 3 |
|
3 |
|
| 4 |
Each project contain three configurations: Debug, Release and Install. Debug and Release have the usual functionality, while Install is special.
|
4 |
Each project contain three configurations: Debug, Release and Install. Debug and Release have the usual functionality, while Install is special.
|
| 5 |
|
5 |
|
| 6 |
We assume, that once GEL is installed, it should be used without adding the source and header files to the particular project.
|
6 |
We assume, that once GEL is installed, it should be used without adding the source and header files to the particular project.
|
| 7 |
|
7 |
|
| 8 |
Therefore we install GEL in an outside directory defined by the environment variable GELEXT. In the configuration, this is done by setting the Target Directory to
|
8 |
Therefore we install GEL in an outside directory defined by the environment variable GELEXT. In the configuration, this is done by setting the Target Directory to
|
| 9 |
$(GELEXT)\lib\windows
|
9 |
$(GELEXT)\lib\windows
|
| 10 |
|
10 |
|
| 11 |
and, as a post-build event, all header files are copied to
|
11 |
and, as a post-build event, all header files are copied to
|
| 12 |
$(GELEXt)\include
|
12 |
$(GELEXt)\include
|
| 13 |
|
13 |
|
| 14 |
The GELEXT variable should be the path where all 3rd party lib and header files are stored (like /usr/local/ on a *NIX system)
|
14 |
The GELEXT variable should be the path where all 3rd party lib and header files are stored (like /usr/local/ on a *NIX system)
|
| 15 |
|
15 |
|
| 16 |
|
16 |
|
| 17 |
|
17 |
|