/[pcre]/code/trunk/NON-AUTOTOOLS-BUILD
ViewVC logotype

Contents of /code/trunk/NON-AUTOTOOLS-BUILD

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1028 - (show annotations)
Thu Sep 6 16:55:38 2012 UTC (7 years, 1 month ago) by ph10
File size: 25030 byte(s)
Error occurred while calculating annotation data.
Set config.h NEWLINE values appropriately for EBCDIC, adding 
--enable-ebcdic-nl25 (and CMake equivalent) for the alternate NL encoding.
1 Building PCRE without using autotools
2 -------------------------------------
3
4 This document contains the following sections:
5
6 General
7 Generic instructions for the PCRE C library
8 The C++ wrapper functions
9 Building for virtual Pascal
10 Stack size in Windows environments
11 Linking programs in Windows environments
12 Comments about Win32 builds
13 Building PCRE on Windows with CMake
14 Use of relative paths with CMake on Windows
15 Testing with RunTest.bat
16 Building under Windows with BCC5.5
17 Building PCRE on OpenVMS
18 Building PCRE on Stratus OpenVOS
19
20
21 GENERAL
22
23 I (Philip Hazel) have no experience of Windows or VMS sytems and how their
24 libraries work. The items in the PCRE distribution and Makefile that relate to
25 anything other than Linux systems are untested by me.
26
27 There are some other comments and files (including some documentation in CHM
28 format) in the Contrib directory on the FTP site:
29
30 ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Contrib
31
32 The basic PCRE library consists entirely of code written in Standard C, and so
33 should compile successfully on any system that has a Standard C compiler and
34 library. The C++ wrapper functions are a separate issue (see below).
35
36 The PCRE distribution includes a "configure" file for use by the configure/make
37 (autotools) build system, as found in many Unix-like environments. The README
38 file contains information about the options for "configure".
39
40 There is also support for CMake, which some users prefer, especially in Windows
41 environments, though it can also be run in Unix-like environments. See the
42 section entitled "Building PCRE on Windows with CMake" below.
43
44 Versions of config.h and pcre.h are distributed in the PCRE tarballs under the
45 names config.h.generic and pcre.h.generic. These are provided for those who
46 build PCRE without using "configure" or CMake. If you use "configure" or CMake,
47 the .generic versions are not used.
48
49
50 GENERIC INSTRUCTIONS FOR THE PCRE C LIBRARY
51
52 The following are generic instructions for building the PCRE C library "by
53 hand". If you are going to use CMake, this section does not apply to you; you
54 can skip ahead to the CMake section.
55
56 (1) Copy or rename the file config.h.generic as config.h, and edit the macro
57 settings that it contains to whatever is appropriate for your environment.
58
59 In particular, you can alter the definition of the NEWLINE macro to
60 specify what character(s) you want to be interpreted as line terminators.
61 In an EBCDIC environment, you MUST change NEWLINE, because its default
62 value is 10, an ASCII LF. The usual EBCDIC newline character is 21 (0x15,
63 NL), though in some cases it may be 37 (0x25).
64
65 When you compile any of the PCRE modules, you must specify -DHAVE_CONFIG_H
66 to your compiler so that config.h is included in the sources.
67
68 An alternative approach is not to edit config.h, but to use -D on the
69 compiler command line to make any changes that you need to the
70 configuration options. In this case -DHAVE_CONFIG_H must not be set.
71
72 NOTE: There have been occasions when the way in which certain parameters
73 in config.h are used has changed between releases. (In the configure/make
74 world, this is handled automatically.) When upgrading to a new release,
75 you are strongly advised to review config.h.generic before re-using what
76 you had previously.
77
78 (2) Copy or rename the file pcre.h.generic as pcre.h.
79
80 (3) EITHER:
81 Copy or rename file pcre_chartables.c.dist as pcre_chartables.c.
82
83 OR:
84 Compile dftables.c as a stand-alone program (using -DHAVE_CONFIG_H if
85 you have set up config.h), and then run it with the single argument
86 "pcre_chartables.c". This generates a set of standard character tables
87 and writes them to that file. The tables are generated using the default
88 C locale for your system. If you want to use a locale that is specified
89 by LC_xxx environment variables, add the -L option to the dftables
90 command. You must use this method if you are building on a system that
91 uses EBCDIC code.
92
93 The tables in pcre_chartables.c are defaults. The caller of PCRE can
94 specify alternative tables at run time.
95
96 (4) Ensure that you have the following header files:
97
98 pcre_internal.h
99 ucp.h
100
101 (5) For an 8-bit library, compile the following source files, setting
102 -DHAVE_CONFIG_H as a compiler option if you have set up config.h with your
103 configuration, or else use other -D settings to change the configuration
104 as required.
105
106 pcre_byte_order.c
107 pcre_chartables.c
108 pcre_compile.c
109 pcre_config.c
110 pcre_dfa_exec.c
111 pcre_exec.c
112 pcre_fullinfo.c
113 pcre_get.c
114 pcre_globals.c
115 pcre_jit_compile.c
116 pcre_maketables.c
117 pcre_newline.c
118 pcre_ord2utf8.c
119 pcre_refcount.c
120 pcre_string_utils.c
121 pcre_study.c
122 pcre_tables.c
123 pcre_ucd.c
124 pcre_valid_utf8.c
125 pcre_version.c
126 pcre_xclass.c
127
128 Make sure that you include -I. in the compiler command (or equivalent for
129 an unusual compiler) so that all included PCRE header files are first
130 sought in the current directory. Otherwise you run the risk of picking up
131 a previously-installed file from somewhere else.
132
133 Note that you must still compile pcre_jit_compile.c, even if you have not
134 defined SUPPORT_JIT in config.h, because when JIT support is not
135 configured, dummy functions are compiled. When JIT support IS configured,
136 pcre_jit_compile.c #includes sources from the sljit subdirectory, where
137 there should be 16 files, all of whose names begin with "sljit".
138
139 (6) Now link all the compiled code into an object library in whichever form
140 your system keeps such libraries. This is the basic PCRE C 8-bit library.
141 If your system has static and shared libraries, you may have to do this
142 once for each type.
143
144 (7) If you want to build a 16-bit library (as well as, or instead of the 8-bit
145 library) repeat steps 5-6 with the following files:
146
147 pcre16_byte_order.c
148 pcre16_chartables.c
149 pcre16_compile.c
150 pcre16_config.c
151 pcre16_dfa_exec.c
152 pcre16_exec.c
153 pcre16_fullinfo.c
154 pcre16_get.c
155 pcre16_globals.c
156 pcre16_jit_compile.c
157 pcre16_maketables.c
158 pcre16_newline.c
159 pcre16_ord2utf16.c
160 pcre16_refcount.c
161 pcre16_string_utils.c
162 pcre16_study.c
163 pcre16_tables.c
164 pcre16_ucd.c
165 pcre16_utf16_utils.c
166 pcre16_valid_utf16.c
167 pcre16_version.c
168 pcre16_xclass.c
169
170 (8) If you want to build the POSIX wrapper functions (which apply only to the
171 8-bit library), ensure that you have the pcreposix.h file and then compile
172 pcreposix.c (remembering -DHAVE_CONFIG_H if necessary). Link the result
173 (on its own) as the pcreposix library.
174
175 (9) The pcretest program can be linked with either or both of the 8-bit and
176 16-bit libraries (depending on what you selected in config.h). Compile
177 pcretest.c and pcre_printint.c (again, don't forget -DHAVE_CONFIG_H) and
178 link them together with the appropriate library/ies. If you compiled an
179 8-bit library, pcretest also needs the pcreposix wrapper library unless
180 you compiled it with -DNOPOSIX.
181
182 (10) Run pcretest on the testinput files in the testdata directory, and check
183 that the output matches the corresponding testoutput files. There are
184 comments about what each test does in the section entitled "Testing PCRE"
185 in the README file. If you compiled both an 8-bit and a 16-bit library,
186 you need to run pcretest with the -16 option to do 16-bit tests.
187
188 Some tests are relevant only when certain build-time options are selected.
189 For example, test 4 is for UTF-8 or UTF-16 support, and will not run if
190 you have built PCRE without it. See the comments at the start of each
191 testinput file. If you have a suitable Unix-like shell, the RunTest script
192 will run the appropriate tests for you.
193
194 Note that the supplied files are in Unix format, with just LF characters
195 as line terminators. You may need to edit them to change this if your
196 system uses a different convention. If you are using Windows, you probably
197 should use the wintestinput3 file instead of testinput3 (and the
198 corresponding output file). This is a locale test; wintestinput3 sets the
199 locale to "french" rather than "fr_FR", and there some minor output
200 differences.
201
202 (11) If you have built PCRE with SUPPORT_JIT, the JIT features will be tested
203 by the testdata files. However, you might also like to build and run
204 the JIT test program, pcre_jit_test.c.
205
206 (12) If you want to use the pcregrep command, compile and link pcregrep.c; it
207 uses only the basic 8-bit PCRE library (it does not need the pcreposix
208 library).
209
210
211 THE C++ WRAPPER FUNCTIONS
212
213 The PCRE distribution also contains some C++ wrapper functions and tests,
214 applicable to the 8-bit library, which were contributed by Google Inc. On a
215 system that can use "configure" and "make", the functions are automatically
216 built into a library called pcrecpp. It should be straightforward to compile
217 the .cc files manually on other systems. The files called xxx_unittest.cc are
218 test programs for each of the corresponding xxx.cc files.
219
220
221 BUILDING FOR VIRTUAL PASCAL
222
223 A script for building PCRE using Borland's C++ compiler for use with VPASCAL
224 was contributed by Alexander Tokarev. Stefan Weber updated the script and added
225 additional files. The following files in the distribution are for building PCRE
226 for use with VP/Borland: makevp_c.txt, makevp_l.txt, makevp.bat, pcregexp.pas.
227
228
229 STACK SIZE IN WINDOWS ENVIRONMENTS
230
231 The default processor stack size of 1Mb in some Windows environments is too
232 small for matching patterns that need much recursion. In particular, test 2 may
233 fail because of this. Normally, running out of stack causes a crash, but there
234 have been cases where the test program has just died silently. See your linker
235 documentation for how to increase stack size if you experience problems. The
236 Linux default of 8Mb is a reasonable choice for the stack, though even that can
237 be too small for some pattern/subject combinations.
238
239 PCRE has a compile configuration option to disable the use of stack for
240 recursion so that heap is used instead. However, pattern matching is
241 significantly slower when this is done. There is more about stack usage in the
242 "pcrestack" documentation.
243
244
245 LINKING PROGRAMS IN WINDOWS ENVIRONMENTS
246
247 If you want to statically link a program against a PCRE library in the form of
248 a non-dll .a file, you must define PCRE_STATIC before including pcre.h or
249 pcrecpp.h, otherwise the pcre_malloc() and pcre_free() exported functions will
250 be declared __declspec(dllimport), with unwanted results.
251
252
253 CALLING CONVENTIONS IN WINDOWS ENVIRONMENTS
254
255 It is possible to compile programs to use different calling conventions using
256 MSVC. Search the web for "calling conventions" for more information. To make it
257 easier to change the calling convention for the exported functions in the
258 PCRE library, the macro PCRE_CALL_CONVENTION is present in all the external
259 definitions. It can be set externally when compiling (e.g. in CFLAGS). If it is
260 not set, it defaults to empty; the default calling convention is then used
261 (which is what is wanted most of the time).
262
263
264 COMMENTS ABOUT WIN32 BUILDS (see also "BUILDING PCRE ON WINDOWS WITH CMAKE")
265
266 There are two ways of building PCRE using the "configure, make, make install"
267 paradigm on Windows systems: using MinGW or using Cygwin. These are not at all
268 the same thing; they are completely different from each other. There is also
269 support for building using CMake, which some users find a more straightforward
270 way of building PCRE under Windows.
271
272 The MinGW home page (http://www.mingw.org/) says this:
273
274 MinGW: A collection of freely available and freely distributable Windows
275 specific header files and import libraries combined with GNU toolsets that
276 allow one to produce native Windows programs that do not rely on any
277 3rd-party C runtime DLLs.
278
279 The Cygwin home page (http://www.cygwin.com/) says this:
280
281 Cygwin is a Linux-like environment for Windows. It consists of two parts:
282
283 . A DLL (cygwin1.dll) which acts as a Linux API emulation layer providing
284 substantial Linux API functionality
285
286 . A collection of tools which provide Linux look and feel.
287
288 The Cygwin DLL currently works with all recent, commercially released x86 32
289 bit and 64 bit versions of Windows, with the exception of Windows CE.
290
291 On both MinGW and Cygwin, PCRE should build correctly using:
292
293 ./configure && make && make install
294
295 This should create two libraries called libpcre and libpcreposix, and, if you
296 have enabled building the C++ wrapper, a third one called libpcrecpp. These are
297 independent libraries: when you link with libpcreposix or libpcrecpp you must
298 also link with libpcre, which contains the basic functions. (Some earlier
299 releases of PCRE included the basic libpcre functions in libpcreposix. This no
300 longer happens.)
301
302 A user submitted a special-purpose patch that makes it easy to create
303 "pcre.dll" under mingw32 using the "msys" environment. It provides "pcre.dll"
304 as a special target. If you use this target, no other files are built, and in
305 particular, the pcretest and pcregrep programs are not built. An example of how
306 this might be used is:
307
308 ./configure --enable-utf --disable-cpp CFLAGS="-03 -s"; make pcre.dll
309
310 Using Cygwin's compiler generates libraries and executables that depend on
311 cygwin1.dll. If a library that is generated this way is distributed,
312 cygwin1.dll has to be distributed as well. Since cygwin1.dll is under the GPL
313 licence, this forces not only PCRE to be under the GPL, but also the entire
314 application. A distributor who wants to keep their own code proprietary must
315 purchase an appropriate Cygwin licence.
316
317 MinGW has no such restrictions. The MinGW compiler generates a library or
318 executable that can run standalone on Windows without any third party dll or
319 licensing issues.
320
321 But there is more complication:
322
323 If a Cygwin user uses the -mno-cygwin Cygwin gcc flag, what that really does is
324 to tell Cygwin's gcc to use the MinGW gcc. Cygwin's gcc is only acting as a
325 front end to MinGW's gcc (if you install Cygwin's gcc, you get both Cygwin's
326 gcc and MinGW's gcc). So, a user can:
327
328 . Build native binaries by using MinGW or by getting Cygwin and using
329 -mno-cygwin.
330
331 . Build binaries that depend on cygwin1.dll by using Cygwin with the normal
332 compiler flags.
333
334 The test files that are supplied with PCRE are in UNIX format, with LF
335 characters as line terminators. Unless your PCRE library uses a default newline
336 option that includes LF as a valid newline, it may be necessary to change the
337 line terminators in the test files to get some of the tests to work.
338
339
340 BUILDING PCRE ON WINDOWS WITH CMAKE
341
342 CMake is an alternative configuration facility that can be used instead of
343 "configure". CMake creates project files (make files, solution files, etc.)
344 tailored to numerous development environments, including Visual Studio,
345 Borland, Msys, MinGW, NMake, and Unix. If possible, use short paths with no
346 spaces in the names for your CMake installation and your PCRE source and build
347 directories.
348
349 The following instructions were contributed by a PCRE user. If they are not
350 followed exactly, errors may occur. In the event that errors do occur, it is
351 recommended that you delete the CMake cache before attempting to repeat the
352 CMake build process. In the CMake GUI, the cache can be deleted by selecting
353 "File > Delete Cache".
354
355 1. Install the latest CMake version available from http://www.cmake.org/, and
356 ensure that cmake\bin is on your path.
357
358 2. Unzip (retaining folder structure) the PCRE source tree into a source
359 directory such as C:\pcre. You should ensure your local date and time
360 is not earlier than the file dates in your source dir if the release is
361 very new.
362
363 3. Create a new, empty build directory, preferably a subdirectory of the
364 source dir. For example, C:\pcre\pcre-xx\build.
365
366 4. Run cmake-gui from the Shell envirornment of your build tool, for example,
367 Msys for Msys/MinGW or Visual Studio Command Prompt for VC/VC++. Do not try
368 to start Cmake from the Windows Start menu, as this can lead to errors.
369
370 5. Enter C:\pcre\pcre-xx and C:\pcre\pcre-xx\build for the source and build
371 directories, respectively.
372
373 6. Hit the "Configure" button.
374
375 7. Select the particular IDE / build tool that you are using (Visual
376 Studio, MSYS makefiles, MinGW makefiles, etc.)
377
378 8. The GUI will then list several configuration options. This is where
379 you can enable UTF-8 support or other PCRE optional features.
380
381 9. Hit "Configure" again. The adjacent "Generate" button should now be
382 active.
383
384 10. Hit "Generate".
385
386 11. The build directory should now contain a usable build system, be it a
387 solution file for Visual Studio, makefiles for MinGW, etc. Exit from
388 cmake-gui and use the generated build system with your compiler or IDE.
389 E.g., for MinGW you can run "make", or for Visual Studio, open the PCRE
390 solution, select the desired configuration (Debug, or Release, etc.) and
391 build the ALL_BUILD project.
392
393 12. If during configuration with cmake-gui you've elected to build the test
394 programs, you can execute them by building the test project. E.g., for
395 MinGW: "make test"; for Visual Studio build the RUN_TESTS project. The
396 most recent build configuration is targeted by the tests. A summary of
397 test results is presented. Complete test output is subsequently
398 available for review in Testing\Temporary under your build dir.
399
400
401 USE OF RELATIVE PATHS WITH CMAKE ON WINDOWS
402
403 A PCRE user comments as follows:
404
405 I thought that others may want to know the current state of
406 CMAKE_USE_RELATIVE_PATHS support on Windows.
407
408 Here it is:
409 -- AdditionalIncludeDirectories is only partially modified (only the
410 first path - see below)
411 -- Only some of the contained file paths are modified - shown below for
412 pcre.vcproj
413 -- It properly modifies
414
415 I am sure CMake people can fix that if they want to. Until then one will
416 need to replace existing absolute paths in project files with relative
417 paths manually (e.g. from VS) - relative to project file location. I did
418 just that before being told to try CMAKE_USE_RELATIVE_PATHS. Not a big
419 deal.
420
421 AdditionalIncludeDirectories="E:\builds\pcre\build;E:\builds\pcre\pcre-7.5;"
422 AdditionalIncludeDirectories=".;E:\builds\pcre\pcre-7.5;"
423
424 RelativePath="pcre.h">
425 RelativePath="pcre_chartables.c">
426 RelativePath="pcre_chartables.c.rule">
427
428
429 TESTING WITH RUNTEST.BAT
430
431 If configured with CMake, building the test project ("make test" or building
432 ALL_TESTS in Visual Studio) creates (and runs) pcre_test.bat (and depending
433 on your configuration options, possibly other test programs) in the build
434 directory. Pcre_test.bat runs RunTest.Bat with correct source and exe paths.
435
436 For manual testing with RunTest.bat, provided the build dir is a subdirectory
437 of the source directory: Open command shell window. Chdir to the location
438 of your pcretest.exe and pcregrep.exe programs. Call RunTest.bat with
439 "..\RunTest.Bat" or "..\..\RunTest.bat" as appropriate.
440
441 To run only a particular test with RunTest.Bat provide a test number argument.
442
443 Otherwise:
444
445 1. Copy RunTest.bat into the directory where pcretest.exe and pcregrep.exe
446 have been created.
447
448 2. Edit RunTest.bat to indentify the full or relative location of
449 the pcre source (wherein which the testdata folder resides), e.g.:
450
451 set srcdir=C:\pcre\pcre-8.20
452
453 3. In a Windows command environment, chdir to the location of your bat and
454 exe programs.
455
456 4. Run RunTest.bat. Test outputs will automatically be compared to expected
457 results, and discrepancies will be identified in the console output.
458
459 To independently test the just-in-time compiler, run pcre_jit_test.exe.
460 To test pcrecpp, run pcrecpp_unittest.exe, pcre_stringpiece_unittest.exe and
461 pcre_scanner_unittest.exe.
462
463
464 BUILDING UNDER WINDOWS WITH BCC5.5
465
466 Michael Roy sent these comments about building PCRE under Windows with BCC5.5:
467
468 Some of the core BCC libraries have a version of PCRE from 1998 built in,
469 which can lead to pcre_exec() giving an erroneous PCRE_ERROR_NULL from a
470 version mismatch. I'm including an easy workaround below, if you'd like to
471 include it in the non-unix instructions:
472
473 When linking a project with BCC5.5, pcre.lib must be included before any of
474 the libraries cw32.lib, cw32i.lib, cw32mt.lib, and cw32mti.lib on the command
475 line.
476
477
478 BUILDING UNDER WINDOWS CE WITH VISUAL STUDIO 200x
479
480 Vincent Richomme sent a zip archive of files to help with this process. They
481 can be found in the file "pcre-vsbuild.zip" in the Contrib directory of the FTP
482 site.
483
484
485 BUILDING PCRE ON OPENVMS
486
487 Dan Mooney sent the following comments about building PCRE on OpenVMS. They
488 relate to an older version of PCRE that used fewer source files, so the exact
489 commands will need changing. See the current list of source files above.
490
491 "It was quite easy to compile and link the library. I don't have a formal
492 make file but the attached file [reproduced below] contains the OpenVMS DCL
493 commands I used to build the library. I had to add #define
494 POSIX_MALLOC_THRESHOLD 10 to pcre.h since it was not defined anywhere.
495
496 The library was built on:
497 O/S: HP OpenVMS v7.3-1
498 Compiler: Compaq C v6.5-001-48BCD
499 Linker: vA13-01
500
501 The test results did not match 100% due to the issues you mention in your
502 documentation regarding isprint(), iscntrl(), isgraph() and ispunct(). I
503 modified some of the character tables temporarily and was able to get the
504 results to match. Tests using the fr locale did not match since I don't have
505 that locale loaded. The study size was always reported to be 3 less than the
506 value in the standard test output files."
507
508 =========================
509 $! This DCL procedure builds PCRE on OpenVMS
510 $!
511 $! I followed the instructions in the non-unix-use file in the distribution.
512 $!
513 $ COMPILE == "CC/LIST/NOMEMBER_ALIGNMENT/PREFIX_LIBRARY_ENTRIES=ALL_ENTRIES
514 $ COMPILE DFTABLES.C
515 $ LINK/EXE=DFTABLES.EXE DFTABLES.OBJ
516 $ RUN DFTABLES.EXE/OUTPUT=CHARTABLES.C
517 $ COMPILE MAKETABLES.C
518 $ COMPILE GET.C
519 $ COMPILE STUDY.C
520 $! I had to set POSIX_MALLOC_THRESHOLD to 10 in PCRE.H since the symbol
521 $! did not seem to be defined anywhere.
522 $! I edited pcre.h and added #DEFINE SUPPORT_UTF8 to enable UTF8 support.
523 $ COMPILE PCRE.C
524 $ LIB/CREATE PCRE MAKETABLES.OBJ, GET.OBJ, STUDY.OBJ, PCRE.OBJ
525 $! I had to set POSIX_MALLOC_THRESHOLD to 10 in PCRE.H since the symbol
526 $! did not seem to be defined anywhere.
527 $ COMPILE PCREPOSIX.C
528 $ LIB/CREATE PCREPOSIX PCREPOSIX.OBJ
529 $ COMPILE PCRETEST.C
530 $ LINK/EXE=PCRETEST.EXE PCRETEST.OBJ, PCRE/LIB, PCREPOSIX/LIB
531 $! C programs that want access to command line arguments must be
532 $! defined as a symbol
533 $ PCRETEST :== "$ SYS$ROADSUSERS:[DMOONEY.REGEXP]PCRETEST.EXE"
534 $! Arguments must be enclosed in quotes.
535 $ PCRETEST "-C"
536 $! Test results:
537 $!
538 $! The test results did not match 100%. The functions isprint(), iscntrl(),
539 $! isgraph() and ispunct() on OpenVMS must not produce the same results
540 $! as the system that built the test output files provided with the
541 $! distribution.
542 $!
543 $! The study size did not match and was always 3 less on OpenVMS.
544 $!
545 $! Locale could not be set to fr
546 $!
547 =========================
548
549
550 BUILDING PCRE ON STRATUS OPENVOS
551
552 These notes on the port of PCRE to VOS (lightly edited) were supplied by
553 Ashutosh Warikoo, whose email address has the local part awarikoo and the
554 domain nse.co.in. The port was for version 7.9 in August 2009.
555
556 1. Building PCRE
557
558 I built pcre on OpenVOS Release 17.0.1at using GNU Tools 3.4a without any
559 problems. I used the following packages to build PCRE:
560
561 ftp://ftp.stratus.com/pub/vos/posix/ga/posix.save.evf.gz
562
563 Please read and follow the instructions that come with these packages. To start
564 the build of pcre, from the root of the package type:
565
566 ./build.sh
567
568 2. Installing PCRE
569
570 Once you have successfully built PCRE, login to the SysAdmin group, switch to
571 the root user, and type
572
573 [ !create_dir (master_disk)>usr --if needed ]
574 [ !create_dir (master_disk)>usr>local --if needed ]
575 !gmake install
576
577 This installs PCRE and its man pages into /usr/local. You can add
578 (master_disk)>usr>local>bin to your command search paths, or if you are in
579 BASH, add /usr/local/bin to the PATH environment variable.
580
581 4. Restrictions
582
583 This port requires readline library optionally. However during the build I
584 faced some yet unexplored errors while linking with readline. As it was an
585 optional component I chose to disable it.
586
587 5. Known Problems
588
589 I ran the test suite, but you will have to be your own judge of whether this
590 command, and this port, suits your purposes. If you find any problems that
591 appear to be related to the port itself, please let me know. Please see the
592 build.log file in the root of the package also.
593
594
595 ==========================
596 Last Updated: 04 September 2012

  ViewVC Help
Powered by ViewVC 1.1.5