| [12] | 1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
|---|
| 2 | <html> |
|---|
| 3 | <head> |
|---|
| 4 | <title>Boost.Regex: Installation</title> |
|---|
| 5 | <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> |
|---|
| 6 | <LINK href="../../../boost.css" type="text/css" rel="stylesheet"></head> |
|---|
| 7 | <body> |
|---|
| 8 | <P> |
|---|
| 9 | <TABLE id="Table1" cellSpacing="1" cellPadding="1" width="100%" border="0"> |
|---|
| 10 | <TR> |
|---|
| 11 | <td vAlign="top" width="300"> |
|---|
| 12 | <h3><A href="../../../index.htm"><IMG height="86" alt="C++ Boost" src="../../../boost.png" width="277" border="0"></A></h3> |
|---|
| 13 | </td> |
|---|
| 14 | <TD width="353"> |
|---|
| 15 | <H1 align="center">Boost.Regex</H1> |
|---|
| 16 | <H2 align="center">Installation</H2> |
|---|
| 17 | </TD> |
|---|
| 18 | <td width="50"> |
|---|
| 19 | <h3><A href="index.html"><IMG height="45" alt="Boost.Regex Index" src="uarrow.gif" width="43" border="0"></A></h3> |
|---|
| 20 | </td> |
|---|
| 21 | </TR> |
|---|
| 22 | </TABLE> |
|---|
| 23 | </P> |
|---|
| 24 | <HR> |
|---|
| 25 | <P>When you extract the library from its zip file, you must preserve its internal |
|---|
| 26 | directory structure (for example by using the -d option when extracting). If |
|---|
| 27 | you didn't do that when extracting, then you'd better stop reading this, delete |
|---|
| 28 | the files you just extracted, and try again! |
|---|
| 29 | </P> |
|---|
| 30 | <P>This library should not need configuring before use; most popular |
|---|
| 31 | compilers/standard libraries/platforms are already supported "as is". If you do |
|---|
| 32 | experience configuration problems, or just want to test the configuration with |
|---|
| 33 | your compiler, then the process is the same as for all of boost; see the <A href="../../config/config.htm"> |
|---|
| 34 | configuration library documentation</A>.</P> |
|---|
| 35 | <P>The library will encase all code inside namespace boost. |
|---|
| 36 | </P> |
|---|
| 37 | <P>Unlike some other template libraries, this library consists of a mixture of |
|---|
| 38 | template code (in the headers) and static code and data (in cpp files). |
|---|
| 39 | Consequently it is necessary to build the library's support code into a library |
|---|
| 40 | or archive file before you can use it, instructions for specific platforms are |
|---|
| 41 | as follows: |
|---|
| 42 | </P> |
|---|
| 43 | <H3><A name="bjam"></A>Building with bjam</H3> |
|---|
| 44 | <P>This is now the preferred method for building and installing this library, |
|---|
| 45 | please refer to the <A href="../../../more/getting_started.html">getting started |
|---|
| 46 | guide</A> for more information.</P> |
|---|
| 47 | <H3><A name="unicode"></A>Building With Unicode and ICU Support</H3> |
|---|
| 48 | <P>A default build of this library does not enable <A href="unicode.html">Unciode |
|---|
| 49 | support</A> via ICU. There is no need to enable this support if you |
|---|
| 50 | don't need it, but if you use ICU for your Unicode support already, and want to |
|---|
| 51 | work with Unicode-aware regular expressions then read on.</P> |
|---|
| 52 | <P>If you're building on a Unix-like platform, and ICU is already installed in |
|---|
| 53 | you're compilers search path (with an install prefix of /usr or /usr/local |
|---|
| 54 | for example), then set the environment variable HAVE_ICU to enable ICU |
|---|
| 55 | support. For example you might build with the command line:</P> |
|---|
| 56 | <PRE>bjam -sHAVE_ICU=1 -sTOOLS=<A href="../../../more/getting_started.html#Tools">my-compiler</A></PRE> |
|---|
| 57 | <P>If ICU is not already in your compilers path then you need to set the |
|---|
| 58 | environment variable ICU_PATH to point to the route directory of your ICU |
|---|
| 59 | installation, for example if ICU was installed to /usr/local/icu/3.3 you might |
|---|
| 60 | use:</P> |
|---|
| 61 | <PRE>bjam -sICU_PATH=/usr/local/icu/3.3 -sTOOLS=<A href="../../../more/getting_started.html#Tools" >my-compiler</A></PRE> |
|---|
| 62 | <P>Note that ICU is a C++ library just like Boost is, as such your copy of ICU |
|---|
| 63 | must have been built with the same C++ compiler (and compiler version) that you |
|---|
| 64 | are using to build Boost. <STRONG>Boost.Regex will not work correctly unless |
|---|
| 65 | you ensure that this is the case:</STRONG> it is up to you to ensure that |
|---|
| 66 | the version of ICU you are using is binary compatible with the toolset you use |
|---|
| 67 | to build Boost.</P> |
|---|
| 68 | <H2><A name="make"></A>Building via makefiles</H2> |
|---|
| 69 | <H3><A name="bcb"></A>Borland C++ Builder: |
|---|
| 70 | </H3> |
|---|
| 71 | <UL> |
|---|
| 72 | <LI> |
|---|
| 73 | Open up a console window and change to the <boost>\libs\regex\build |
|---|
| 74 | directory. |
|---|
| 75 | <LI> |
|---|
| 76 | Select the appropriate makefile (bcb4.mak for C++ Builder 4, bcb5.mak for C++ |
|---|
| 77 | Builder 5, and bcb6.mak for C++ Builder 6). |
|---|
| 78 | <LI> |
|---|
| 79 | Invoke the makefile (pass the full path to your version of make if you have |
|---|
| 80 | more than one version installed, the makefile relies on the path to make to |
|---|
| 81 | obtain your C++ Builder installation directory and tools) for example: |
|---|
| 82 | </LI> |
|---|
| 83 | </UL> |
|---|
| 84 | <PRE>make -fbcb5.mak</PRE> |
|---|
| 85 | <P>The build process will build a variety of .lib and .dll files (the exact number |
|---|
| 86 | depends upon the version of Borland's tools you are using) the .lib and dll |
|---|
| 87 | files will be in a sub-directory called bcb4 or bcb5 depending upon the |
|---|
| 88 | makefile used. To install the libraries into your development system use:</P> |
|---|
| 89 | <PRE>make -fbcb5.mak install</PRE> |
|---|
| 90 | <P>library files will be copied to <BCROOT>/lib and the dll's to |
|---|
| 91 | <BCROOT>/bin, where <BCROOT> corresponds to the install path of |
|---|
| 92 | your Borland C++ tools. |
|---|
| 93 | </P> |
|---|
| 94 | <P>You may also remove temporary files created during the build process (excluding |
|---|
| 95 | lib and dll files) by using:</P> |
|---|
| 96 | <PRE>make -fbcb5.mak clean</PRE> |
|---|
| 97 | <P>Finally when you use regex++ it is only necessary for you to add the |
|---|
| 98 | <boost> root director to your list of include directories for that |
|---|
| 99 | project. It is not necessary for you to manually add a .lib file to the |
|---|
| 100 | project; the headers will automatically select the correct .lib file for your |
|---|
| 101 | build mode and tell the linker to include it. There is one caveat however: the |
|---|
| 102 | library can not tell the difference between VCL and non-VCL enabled builds when |
|---|
| 103 | building a GUI application from the command line, if you build from the command |
|---|
| 104 | line with the 5.5 command line tools then you must define the pre-processor |
|---|
| 105 | symbol _NO_VCL in order to ensure that the correct link libraries are selected: |
|---|
| 106 | the C++ Builder IDE normally sets this automatically. Hint, users of the 5.5 |
|---|
| 107 | command line tools may want to add a -D_NO_VCL to bcc32.cfg in order to set |
|---|
| 108 | this option permanently. |
|---|
| 109 | </P> |
|---|
| 110 | <P>If you would prefer to do a dynamic link to the regex libraries when using the |
|---|
| 111 | dll runtime then define BOOST_REGEX_DYN_LINK (you must do this if you want to |
|---|
| 112 | use boost.regex in multiple dll's), otherwise Boost.regex will be statically |
|---|
| 113 | linked by default. </P> |
|---|
| 114 | <P>If you want to suppress automatic linking altogether (and supply your own |
|---|
| 115 | custom build of the lib) then define BOOST_REGEX_NO_LIB.</P> |
|---|
| 116 | <P>If you are building with C++ Builder 6, you will find that |
|---|
| 117 | <boost/regex.hpp> can not be used in a pre-compiled header (the actual |
|---|
| 118 | problem is in <locale> which gets included by <boost/regex.hpp>), |
|---|
| 119 | if this causes problems for you, then try defining BOOST_NO_STD_LOCALE when |
|---|
| 120 | building, this will disable some features throughout boost, but may save you a |
|---|
| 121 | lot in compile times!</P> |
|---|
| 122 | <H3><A name="vc"></A>Microsoft Visual C++ 6, 7, 7.1 and 8</H3> |
|---|
| 123 | <P>You need version 6 of MSVC to build this library. If you are using VC5 then you |
|---|
| 124 | may want to look at one of the previous releases of this <A href="http://ourworld.compuserve.com/homepages/john_maddock/regexpp.htm"> |
|---|
| 125 | library</A> |
|---|
| 126 | </P> |
|---|
| 127 | <P>Open up a command prompt, which has the necessary MSVC environment variables |
|---|
| 128 | defined (for example by using the batch file Vcvars32.bat installed by the |
|---|
| 129 | Visual Studio installation), and change to the <boost>\libs\regex\build |
|---|
| 130 | directory. |
|---|
| 131 | </P> |
|---|
| 132 | <P>Select the correct makefile - vc6.mak for "vanilla" Visual C++ 6 or |
|---|
| 133 | vc6-stlport.mak if you are using STLPort.</P> |
|---|
| 134 | <P>Invoke the makefile like this:</P> |
|---|
| 135 | <PRE>nmake -fvc6.mak</PRE> |
|---|
| 136 | <P>You will now have a collection of lib and dll files in a "vc6" subdirectory, to |
|---|
| 137 | install these into your development system use:</P> |
|---|
| 138 | <PRE>nmake -fvc6.mak install</PRE> |
|---|
| 139 | <P>The lib files will be copied to your <VC6>\lib directory and the dll |
|---|
| 140 | files to <VC6>\bin, where <VC6> is the root of your Visual C++ 6 |
|---|
| 141 | installation.</P> |
|---|
| 142 | <P>You can delete all the temporary files created during the build (excluding lib |
|---|
| 143 | and dll files) using:</P> |
|---|
| 144 | <PRE>nmake -fvc6.mak clean </PRE> |
|---|
| 145 | <P>If you want to build with ICU support, then you need to pass the path to your |
|---|
| 146 | ICU directory to the makefile, for example with: |
|---|
| 147 | </P> |
|---|
| 148 | <PRE>nmake ICU_PATH=c:\open-source\icu -fvc71.mak install</PRE> |
|---|
| 149 | <P>Finally when you use regex++ it is only necessary for you to add the |
|---|
| 150 | <boost> root directory to your list of include directories for that |
|---|
| 151 | project. It is not necessary for you to manually add a .lib file to the |
|---|
| 152 | project; the headers will automatically select the correct .lib file for your |
|---|
| 153 | build mode and tell the linker to include it. |
|---|
| 154 | </P> |
|---|
| 155 | <P>Note that if you want to dynamically link to the regex library when using the |
|---|
| 156 | dynamic C++ runtime, define BOOST_REGEX_DYN_LINK when building your project.</P> |
|---|
| 157 | <P>If you want to add the source directly to your project then define |
|---|
| 158 | BOOST_REGEX_NO_LIB to disable automatic library selection.</P> |
|---|
| 159 | <P>There are several important caveats to remember when using boost.regex with |
|---|
| 160 | Microsoft's Compiler:</P> |
|---|
| 161 | <UL> |
|---|
| 162 | <LI> |
|---|
| 163 | There have been some reports of compiler-optimization bugs affecting this |
|---|
| 164 | library, (particularly with VC6 versions prior to service patch 5) the |
|---|
| 165 | workaround is to build the library using /Oityb1 rather than /O2. That is to |
|---|
| 166 | use all optimization settings except /Oa. This problem is reported to affect |
|---|
| 167 | some standard library code as well (in fact I'm not sure if the problem is with |
|---|
| 168 | the regex code or the underlying standard library), so it's probably worthwhile |
|---|
| 169 | applying this workaround in normal practice in any case. |
|---|
| 170 | <LI> |
|---|
| 171 | If you have replaced the C++ standard library that comes with VC6, then when |
|---|
| 172 | you build the library you must ensure that the environment variables "INCLUDE" |
|---|
| 173 | and "LIB" have been updated to reflect the include and library paths for the |
|---|
| 174 | new library - see vcvars32.bat (part of your Visual Studio installation) for |
|---|
| 175 | more details. |
|---|
| 176 | <LI> |
|---|
| 177 | If you are building with the full STLPort v4.x, then use the vc6-stlport.mak |
|---|
| 178 | file provided and set the environment variable STLPORT_PATH to point to the |
|---|
| 179 | location of your STLPort installation (Note that the full STLPort libraries |
|---|
| 180 | appear not to support single-thread static builds). |
|---|
| 181 | <LI> |
|---|
| 182 | If you are building your application with /Zc:wchar_t then you will need to |
|---|
| 183 | modify the makefile to add /Zc:wchar_t before building the library. |
|---|
| 184 | </LI> |
|---|
| 185 | </UL> |
|---|
| 186 | <H3><A name="gcc"></A>GCC(2.95 and 3.x) |
|---|
| 187 | </H3> |
|---|
| 188 | <P>You can build with gcc using the normal boost Jamfile in |
|---|
| 189 | <boost>/libs/regex/build, alternatively there is a conservative makefile |
|---|
| 190 | for the g++ compiler. From the command prompt change to the |
|---|
| 191 | <boost>/libs/regex/build directory and type: |
|---|
| 192 | </P> |
|---|
| 193 | <PRE>make -fgcc.mak </PRE> |
|---|
| 194 | <P>At the end of the build process you should have a gcc sub-directory containing |
|---|
| 195 | release and debug versions of the library (libboost_regex.a and |
|---|
| 196 | libboost_regex_debug.a). When you build projects that use regex++, you will |
|---|
| 197 | need to add the boost install directory to your list of include paths and add |
|---|
| 198 | <boost>/libs/regex/build/gcc/libboost_regex.a to your list of library |
|---|
| 199 | files. |
|---|
| 200 | </P> |
|---|
| 201 | <P>There is also a makefile to build the library as a shared library:</P> |
|---|
| 202 | <PRE>make -fgcc-shared.mak</PRE> |
|---|
| 203 | <P>which will build libboost_regex.so and libboost_regex_debug.so.</P> |
|---|
| 204 | <P>Both of the these makefiles support the following environment variables:</P> |
|---|
| 205 | <P>ICU_PATH: tells the makefile to build with Unicode support, set to the path |
|---|
| 206 | where your ICU installation is located, for example with: <code>make |
|---|
| 207 | ICU_PATH=/usr/local install -fgcc.mak</code></P> |
|---|
| 208 | <P>CXXFLAGS: extra compiler options - note that this applies to both the debug and |
|---|
| 209 | release builds.</P> |
|---|
| 210 | <P>INCLUDES: additional include directories.</P> |
|---|
| 211 | <P>LDFLAGS: additional linker options.</P> |
|---|
| 212 | <P>LIBS: additional library files.</P> |
|---|
| 213 | <P>For the more adventurous there is a configure script in |
|---|
| 214 | <boost>/libs/config; see the <A href="../../config/config.htm">config |
|---|
| 215 | library documentation</A>.</P> |
|---|
| 216 | <H3><A name="sun"></A>Sun Workshop 6.1</H3> |
|---|
| 217 | <P>There is a makefile for the sun (6.1) compiler (C++ version 3.12). From the |
|---|
| 218 | command prompt change to the <boost>/libs/regex/build directory and type: |
|---|
| 219 | </P> |
|---|
| 220 | <PRE>dmake -f sunpro.mak </PRE> |
|---|
| 221 | <P>At the end of the build process you should have a sunpro sub-directory |
|---|
| 222 | containing single and multithread versions of the library (libboost_regex.a, |
|---|
| 223 | libboost_regex.so, libboost_regex_mt.a and libboost_regex_mt.so). When you |
|---|
| 224 | build projects that use regex++, you will need to add the boost install |
|---|
| 225 | directory to your list of include paths and add |
|---|
| 226 | <boost>/libs/regex/build/sunpro/ to your library search path. |
|---|
| 227 | </P> |
|---|
| 228 | <P>Both of the these makefiles support the following environment variables:</P> |
|---|
| 229 | <P>CXXFLAGS: extra compiler options - note that this applies to both the single |
|---|
| 230 | and multithreaded builds.</P> |
|---|
| 231 | <P>INCLUDES: additional include directories.</P> |
|---|
| 232 | <P>LDFLAGS: additional linker options.</P> |
|---|
| 233 | <P>LIBS: additional library files.</P> |
|---|
| 234 | <P>LIBSUFFIX: a suffix to mangle the library name with (defaults to nothing).</P> |
|---|
| 235 | <P>This makefile does not set any architecture specific options like -xarch=v9, |
|---|
| 236 | you can set these by defining the appropriate macros, for example:</P> |
|---|
| 237 | <PRE>dmake CXXFLAGS="-xarch=v9" LDFLAGS="-xarch=v9" LIBSUFFIX="_v9" -f sunpro.mak</PRE> |
|---|
| 238 | <P>will build v9 variants of the regex library named libboost_regex_v9.a etc.</P> |
|---|
| 239 | <H3><A name="other"></A>Makefiles for Other compilers: |
|---|
| 240 | </H3> |
|---|
| 241 | <P>There is a generic makefile (<A href="../build/generic.mak">generic.mak</A> ) |
|---|
| 242 | provided in <boost-root>/libs/regex/build - see that makefile for details |
|---|
| 243 | of environment variables that need to be set before use. |
|---|
| 244 | <HR> |
|---|
| 245 | <P></P> |
|---|
| 246 | <p>Revised |
|---|
| 247 | <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan --> |
|---|
| 248 | 09 Jan 2005 |
|---|
| 249 | <!--webbot bot="Timestamp" endspan i-checksum="39359" --></p> |
|---|
| 250 | <p><i>© Copyright John Maddock 1998- |
|---|
| 251 | <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%Y" startspan --> 2005<!--webbot bot="Timestamp" endspan i-checksum="39359" --></i></p> |
|---|
| 252 | <P><I>Use, modification and distribution are subject to the Boost Software License, |
|---|
| 253 | Version 1.0. (See accompanying file <A href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</A> |
|---|
| 254 | or copy at <A href="http://www.boost.org/LICENSE_1_0.txt">http://www.boost.org/LICENSE_1_0.txt</A>)</I></P> |
|---|
| 255 | </body> |
|---|
| 256 | </html> |
|---|
