| 45 |
|
|
| 46 |
An alternative approach is not to edit config.h, but to use -D on the |
An alternative approach is not to edit config.h, but to use -D on the |
| 47 |
compiler command line to make any changes that you need. |
compiler command line to make any changes that you need. |
| 48 |
|
|
| 49 |
NOTE: There have been occasions when the way in which certain parameters in |
NOTE: There have been occasions when the way in which certain parameters in |
| 50 |
config.h are used has changed between releases. (In the configure/make |
config.h are used has changed between releases. (In the configure/make |
| 51 |
world, this is handled automatically.) When upgrading to a new release, you |
world, this is handled automatically.) When upgrading to a new release, you |
| 165 |
./configure && make && make install |
./configure && make && make install |
| 166 |
|
|
| 167 |
This should create two libraries called libpcre and libpcreposix, and, if you |
This should create two libraries called libpcre and libpcreposix, and, if you |
| 168 |
have enabled building the C++ wrapper, a third one called libpcrecpp. These are |
have enabled building the C++ wrapper, a third one called libpcrecpp. These are |
| 169 |
independent libraries: when you like with libpcreposix or libpcrecpp you must |
independent libraries: when you like with libpcreposix or libpcrecpp you must |
| 170 |
also link with libpcre, which contains the basic functions. (Some earlier |
also link with libpcre, which contains the basic functions. (Some earlier |
| 171 |
releases of PCRE included the basic libpcre functions in libpcreposix. This no |
releases of PCRE included the basic libpcre functions in libpcreposix. This no |
| 172 |
longer happens.) |
longer happens.) |
| 173 |
|
|
| 174 |
If you want to statically link your program against a non-dll .a file, you must |
If you want to statically link your program against a non-dll .a file, you must |