3 |
|
|
4 |
I (Philip Hazel) have no knowledge of Windows or VMS sytems and how their |
I (Philip Hazel) have no knowledge of Windows or VMS sytems and how their |
5 |
libraries work. The items in the PCRE distribution and Makefile that relate to |
libraries work. The items in the PCRE distribution and Makefile that relate to |
6 |
anything other than Unix-like systems have been contributed by PCRE users and |
anything other than Unix-like systems have been contributed by PCRE users and |
7 |
are untested by me. |
are untested by me. |
8 |
|
|
9 |
There are some other comments and files in the Contrib directory on the ftp |
There are some other comments and files in the Contrib directory on the ftp |
10 |
site that you may find useful. See |
site that you may find useful, although a lot of them are now out-of-date. See |
11 |
|
|
12 |
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Contrib |
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Contrib |
13 |
|
|
20 |
|
|
21 |
GENERIC INSTRUCTIONS FOR THE C LIBRARY |
GENERIC INSTRUCTIONS FOR THE C LIBRARY |
22 |
|
|
23 |
The following are generic comments about building PCRE. The interspersed |
The following are generic comments about building the PCRE C library "by hand". |
|
indented commands are suggestions from Mark Tetrode as to which commands you |
|
|
might use on a Windows system to build a static library. |
|
|
|
|
|
(1) Copy or rename the file config.h.in as config.h, and change the macros that |
|
|
define HAVE_STRERROR and HAVE_MEMMOVE to define them as 1 rather than 0. |
|
|
Unfortunately, because of the way Unix autoconf works, the default setting has |
|
|
to be 0. You may also want to make changes to other macros in config.h. In |
|
|
particular, if you want to force a specific value for newline, you can define |
|
|
the NEWLINE macro. The default is to use '\n', thereby using whatever value |
|
|
your compiler gives to '\n'. |
|
|
|
|
|
rem Mark Tetrode's commands |
|
|
copy config.h.in config.h |
|
|
rem Use write, because notepad cannot handle UNIX files. Change values. |
|
|
write config.h |
|
|
|
|
|
(2) Compile dftables.c as a stand-alone program, and then run it with |
|
|
the single argument "pcre_chartables.c". This generates a set of standard |
|
|
character tables and writes them to that file. |
|
|
|
|
|
rem Mark Tetrode's commands |
|
|
rem Compile & run |
|
|
cl -DSUPPORT_UTF8 -DSUPPORT_UCP dftables.c |
|
|
dftables.exe pcre_chartables.c |
|
|
|
|
|
(3) Compile the following source files: |
|
|
|
|
|
pcre_chartables.c |
|
|
pcre_compile.c |
|
|
pcre_config.c |
|
|
pcre_dfa_exec.c |
|
|
pcre_exec.c |
|
|
pcre_fullinfo.c |
|
|
pcre_get.c |
|
|
pcre_globals.c |
|
|
pcre_info.c |
|
|
pcre_maketables.c |
|
|
pcre_newline.c |
|
|
pcre_ord2utf8.c |
|
|
pcre_refcount.c |
|
|
pcre_study.c |
|
|
pcre_tables.c |
|
|
pcre_try_flipped.c |
|
|
pcre_ucp_searchfuncs.c |
|
|
pcre_valid_utf8.c |
|
|
pcre_version.c |
|
|
pcre_xclass.c |
|
|
|
|
|
and link them all together into an object library in whichever form your system |
|
|
keeps such libraries. This is the pcre C library. If your system has static and |
|
|
shared libraries, you may have to do this once for each type. |
|
|
|
|
|
rem These comments are out-of-date, referring to a previous release which |
|
|
rem had fewer source files. Replace with the file names from above. |
|
|
rem Mark Tetrode's commands, for a static library |
|
|
rem Compile & lib |
|
|
cl -DSUPPORT_UTF8 -DSUPPORT_UCP -DPOSIX_MALLOC_THRESHOLD=10 /c maketables.c get.c study.c pcre.c |
|
|
lib /OUT:pcre.lib maketables.obj get.obj study.obj pcre.obj |
|
|
|
|
|
(4) Similarly, compile pcreposix.c and link it (on its own) as the pcreposix |
|
|
library. |
|
|
|
|
|
rem Mark Tetrode's commands, for a static library |
|
|
rem Compile & lib |
|
|
cl -DSUPPORT_UTF8 -DSUPPORT_UCP -DPOSIX_MALLOC_THRESHOLD=10 /c pcreposix.c |
|
|
lib /OUT:pcreposix.lib pcreposix.obj |
|
|
|
|
|
(5) Compile the test program pcretest.c. This needs the functions in the |
|
|
pcre and pcreposix libraries when linking. |
|
|
|
|
|
rem Mark Tetrode's commands |
|
|
rem compile & link |
|
|
cl /F0x400000 pcretest.c pcre.lib pcreposix.lib |
|
|
|
|
|
(6) Run pcretest on the testinput files in the testdata directory, and check |
|
|
that the output matches the corresponding testoutput files. Note that the |
|
|
supplied files are in Unix format, with just LF characters as line terminators. |
|
|
You may need to edit them to change this if your system uses a different |
|
|
convention. |
|
|
|
|
|
rem Mark Tetrode's commands |
|
|
pcretest testdata\testinput1 testdata\myoutput1 |
|
|
windiff testdata\testoutput1 testdata\myoutput1 |
|
|
pcretest -i testdata\testinput2 testdata\myoutput2 |
|
|
windiff testdata\testoutput2 testdata\myoutput2 |
|
|
pcretest testdata\testinput3 testdata\myoutput3 |
|
|
windiff testdata\testoutput3 testdata\myoutput3 |
|
|
pcretest testdata\testinput4 testdata\myoutput4 |
|
|
windiff testdata\testoutput4 testdata\myoutput4 |
|
|
pcretest testdata\testinput5 testdata\myoutput5 |
|
|
windiff testdata\testoutput5 testdata\myoutput5 |
|
|
pcretest testdata\testinput6 testdata\myoutput6 |
|
|
windiff testdata\testoutput6 testdata\myoutput6 |
|
24 |
|
|
25 |
Note that there are now three more tests (7, 8, 9) that did not exist when Mark |
(1) Copy or rename the file config.h.generic as config.h, and edit the macro |
26 |
wrote those comments. The test the new pcre_dfa_exec() function. |
settings that it contains to whatever is appropriate for your environment. |
27 |
|
In particular, if you want to force a specific value for newline, you can |
28 |
|
define the NEWLINE macro. |
29 |
|
|
30 |
|
An alternative approach is not to edit config.h, but to use -D on the |
31 |
|
compiler command line to make any changes that you need. |
32 |
|
|
33 |
|
(2) Copy or rename the file pcre.h.generic to pcre.h. |
34 |
|
|
35 |
|
(3) Compile dftables.c as a stand-alone program, and then run it with |
36 |
|
the single argument "pcre_chartables.c". This generates a set of standard |
37 |
|
character tables and writes them to that file. |
38 |
|
|
39 |
|
(4) Compile the following source files: |
40 |
|
|
41 |
|
pcre_chartables.c |
42 |
|
pcre_compile.c |
43 |
|
pcre_config.c |
44 |
|
pcre_dfa_exec.c |
45 |
|
pcre_exec.c |
46 |
|
pcre_fullinfo.c |
47 |
|
pcre_get.c |
48 |
|
pcre_globals.c |
49 |
|
pcre_info.c |
50 |
|
pcre_maketables.c |
51 |
|
pcre_newline.c |
52 |
|
pcre_ord2utf8.c |
53 |
|
pcre_refcount.c |
54 |
|
pcre_study.c |
55 |
|
pcre_tables.c |
56 |
|
pcre_try_flipped.c |
57 |
|
pcre_ucp_searchfuncs.c |
58 |
|
pcre_valid_utf8.c |
59 |
|
pcre_version.c |
60 |
|
pcre_xclass.c |
61 |
|
|
62 |
|
Now link them all together into an object library in whichever form your |
63 |
|
system keeps such libraries. This is the basic PCRE C library. If your |
64 |
|
system has static and shared libraries, you may have to do this once for |
65 |
|
each type. |
66 |
|
|
67 |
|
(5) Similarly, compile pcreposix.c and link it (on its own) as the pcreposix |
68 |
|
library. |
69 |
|
|
70 |
|
(6) Compile the test program pcretest.c. This needs the functions in the |
71 |
|
pcre and pcreposix libraries when linking. |
72 |
|
|
73 |
|
(7) Run pcretest on the testinput files in the testdata directory, and check |
74 |
|
that the output matches the corresponding testoutput files. Note that the |
75 |
|
supplied files are in Unix format, with just LF characters as line |
76 |
|
terminators. You may need to edit them to change this if your system uses a |
77 |
|
different convention. |
78 |
|
|
79 |
(7) If you want to use the pcregrep command, compile and link pcregrep.c; it |
(8) If you want to use the pcregrep command, compile and link pcregrep.c; it |
80 |
uses only the basic PCRE library. |
uses only the basic PCRE library (it does not need the pcreposix library). |
81 |
|
|
82 |
|
|
83 |
THE C++ WRAPPER FUNCTIONS |
THE C++ WRAPPER FUNCTIONS |
84 |
|
|
85 |
The PCRE distribution now contains some C++ wrapper functions and tests, |
The PCRE distribution also contains some C++ wrapper functions and tests, |
86 |
contributed by Google Inc. On a system that can use "configure" and "make", |
contributed by Google Inc. On a system that can use "configure" and "make", |
87 |
the functions are automatically built into a library called pcrecpp. It should |
the functions are automatically built into a library called pcrecpp. It should |
88 |
be straightforward to compile the .cc files manually on other systems. The |
be straightforward to compile the .cc files manually on other systems. The |
90 |
xxx.cc files. |
xxx.cc files. |
91 |
|
|
92 |
|
|
93 |
FURTHER REMARKS |
BUILDING FOR VIRTUAL PASCAL |
94 |
|
|
95 |
If you have a system without "configure" but where you can use a Makefile, edit |
Stefan Weber contributed the following files in the distribution for building |
96 |
Makefile.in to create Makefile, substituting suitable values for the variables |
PCRE for use with VP/Borland: !compile.txt, !linklib.txt, makevp.bat, |
|
at the head of the file. |
|
|
|
|
|
Stefan Weber contributed the following files in the distribution for building |
|
|
PCRE for use with VP/Borland: !compile.txt, !linklib.txt, makevp.bat, |
|
97 |
pcregexp.pas. |
pcregexp.pas. |
98 |
|
|
99 |
|
|
100 |
|
BUILDING UNDER WINDOWS WITH BCC5.5 |
101 |
|
|
102 |
Michael Roy sent these comments about building PCRE under Windows with BCC5.5: |
Michael Roy sent these comments about building PCRE under Windows with BCC5.5: |
103 |
|
|
104 |
Some of the core BCC libraries have a version of PCRE from 1998 built in, |
Some of the core BCC libraries have a version of PCRE from 1998 built in, |
110 |
the libraries cw32.lib, cw32i.lib, cw32mt.lib, and cw32mti.lib on the command |
the libraries cw32.lib, cw32i.lib, cw32mt.lib, and cw32mti.lib on the command |
111 |
line. |
line. |
112 |
|
|
113 |
|
|
114 |
|
OUT-OF-DATE COMMENTS ABOUT WIN32 BUILDS |
115 |
|
|
116 |
|
[These comments need looking at by someone who knows about Windows.] |
117 |
|
|
118 |
Some help in building a Win32 DLL of PCRE in GnuWin32 environments was |
Some help in building a Win32 DLL of PCRE in GnuWin32 environments was |
119 |
contributed by Paul Sokolovsky. These environments are Mingw32 |
contributed by Paul Sokolovsky. These environments are Mingw32 |
120 |
(http://www.xraylith.wisc.edu/~khan/software/gnu-win32/) and CygWin |
(http://www.xraylith.wisc.edu/~khan/software/gnu-win32/) and CygWin |