/[pcre]/code/trunk/doc/html/pcrebuild.html
ViewVC logotype

Diff of /code/trunk/doc/html/pcrebuild.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 460 by ph10, Fri Sep 18 19:12:35 2009 UTC revision 461 by ph10, Mon Oct 5 10:59:35 2009 UTC
# Line 40  the optional features are selected or de Line 40  the optional features are selected or de
40  <b>configure</b> before running the <b>make</b> command. However, the same  <b>configure</b> before running the <b>make</b> command. However, the same
41  options can be selected in both Unix-like and non-Unix-like environments using  options can be selected in both Unix-like and non-Unix-like environments using
42  the GUI facility of <b>cmake-gui</b> if you are using <b>CMake</b> instead of  the GUI facility of <b>cmake-gui</b> if you are using <b>CMake</b> instead of
43  <b>configure</b> to build PCRE.  <b>configure</b> to build PCRE.
44  </P>  </P>
45  <P>  <P>
46  There is a lot more information about building PCRE in non-Unix-like  There is a lot more information about building PCRE in non-Unix-like
47  environments in the file called <i>NON_UNIX_USE</i>, which is part of the PCRE  environments in the file called <i>NON_UNIX_USE</i>, which is part of the PCRE
48  distribution. You should consult this file as well as the <i>README</i> file if  distribution. You should consult this file as well as the <i>README</i> file if
49  you are building in a non-Unix-like environment.  you are building in a non-Unix-like environment.
50  </P>  </P>
51  <P>  <P>
# Line 80  To build PCRE with support for UTF-8 Uni Line 80  To build PCRE with support for UTF-8 Uni
80  to the <b>configure</b> command. Of itself, this does not make PCRE treat  to the <b>configure</b> command. Of itself, this does not make PCRE treat
81  strings as UTF-8. As well as compiling PCRE with this option, you also have  strings as UTF-8. As well as compiling PCRE with this option, you also have
82  have to set the PCRE_UTF8 option when you call the <b>pcre_compile()</b>  have to set the PCRE_UTF8 option when you call the <b>pcre_compile()</b>
83  function.  or <b>pcre_compile2()</b> functions.
84  </P>  </P>
85  <P>  <P>
86  If you set --enable-utf8 when compiling in an EBCDIC environment, PCRE expects  If you set --enable-utf8 when compiling in an EBCDIC environment, PCRE expects
# Line 186  another (for example, from an opening pa Line 186  another (for example, from an opening pa
186  metacharacter). By default, two-byte values are used for these offsets, leading  metacharacter). By default, two-byte values are used for these offsets, leading
187  to a maximum size for a compiled pattern of around 64K. This is sufficient to  to a maximum size for a compiled pattern of around 64K. This is sufficient to
188  handle all but the most gigantic patterns. Nevertheless, some people do want to  handle all but the most gigantic patterns. Nevertheless, some people do want to
189  process enormous patterns, so it is possible to compile PCRE to use three-byte  process truyl enormous patterns, so it is possible to compile PCRE to use
190  or four-byte offsets by adding a setting such as  three-byte or four-byte offsets by adding a setting such as
191  <pre>  <pre>
192    --with-link-size=3    --with-link-size=3
193  </pre>  </pre>
# Line 215  to the <b>configure</b> command. With th Line 215  to the <b>configure</b> command. With th
215  <b>pcre_stack_malloc</b> and <b>pcre_stack_free</b> variables to call memory  <b>pcre_stack_malloc</b> and <b>pcre_stack_free</b> variables to call memory
216  management functions. By default these point to <b>malloc()</b> and  management functions. By default these point to <b>malloc()</b> and
217  <b>free()</b>, but you can replace the pointers so that your own functions are  <b>free()</b>, but you can replace the pointers so that your own functions are
218  used.  used instead.
219  </P>  </P>
220  <P>  <P>
221  Separate functions are provided rather than using <b>pcre_malloc</b> and  Separate functions are provided rather than using <b>pcre_malloc</b> and
# Line 224  requested are always the same, and the b Line 224  requested are always the same, and the b
224  order. A calling program might be able to implement optimized functions that  order. A calling program might be able to implement optimized functions that
225  perform better than <b>malloc()</b> and <b>free()</b>. PCRE runs noticeably more  perform better than <b>malloc()</b> and <b>free()</b>. PCRE runs noticeably more
226  slowly when built in this way. This option affects only the <b>pcre_exec()</b>  slowly when built in this way. This option affects only the <b>pcre_exec()</b>
227  function; it is not relevant for the the <b>pcre_dfa_exec()</b> function.  function; it is not relevant for <b>pcre_dfa_exec()</b>.
228  </P>  </P>
229  <br><a name="SEC11" href="#TOC1">LIMITING PCRE RESOURCE USAGE</a><br>  <br><a name="SEC11" href="#TOC1">LIMITING PCRE RESOURCE USAGE</a><br>
230  <P>  <P>
# Line 308  If you add Line 308  If you add
308  to the <b>configure</b> command, <b>pcretest</b> is linked with the  to the <b>configure</b> command, <b>pcretest</b> is linked with the
309  <b>libreadline</b> library, and when its input is from a terminal, it reads it  <b>libreadline</b> library, and when its input is from a terminal, it reads it
310  using the <b>readline()</b> function. This provides line-editing and history  using the <b>readline()</b> function. This provides line-editing and history
311  facilities. Note that <b>libreadline</b> is GPL-licenced, so if you distribute a  facilities. Note that <b>libreadline</b> is GPL-licensed, so if you distribute a
312  binary of <b>pcretest</b> linked in this way, there may be licensing issues.  binary of <b>pcretest</b> linked in this way, there may be licensing issues.
313  </P>  </P>
314  <P>  <P>
# Line 345  Cambridge CB2 3QH, England. Line 345  Cambridge CB2 3QH, England.
345  </P>  </P>
346  <br><a name="SEC18" href="#TOC1">REVISION</a><br>  <br><a name="SEC18" href="#TOC1">REVISION</a><br>
347  <P>  <P>
348  Last updated: 06 September 2009  Last updated: 29 September 2009
349  <br>  <br>
350  Copyright &copy; 1997-2009 University of Cambridge.  Copyright &copy; 1997-2009 University of Cambridge.
351  <br>  <br>

Legend:
Removed from v.460  
changed lines
  Added in v.461

  ViewVC Help
Powered by ViewVC 1.1.5