From 9079cc8201c047c23844b63b9c91d9bc087cdbee Mon Sep 17 00:00:00 2001
From: John Maddock
You can build with gcc using the normal boost Jamfile in - <boost>/libs/regex/build, alternatively there is a conservative makefile - for the g++ compiler. From the command prompt change to the - <boost>/libs/regex/build directory and type: +
The best way to build with gcc is using the + normal boost Jamfile in <boost>/libs/regex/build, alternatively + there is a conservative makefile for the g++ compiler. From the command prompt + change to the <boost>/libs/regex/build directory and type:
make -fgcc.mak
At the end of the build process you should have a gcc sub-directory containing - release and debug versions of the library (libboost_regex.a and - libboost_regex_debug.a). When you build projects that use regex++, you will - need to add the boost install directory to your list of include paths and add - <boost>/libs/regex/build/gcc/libboost_regex.a to your list of library - files. + release and debug versions of the library (libboost_regex-gcc-1_32.a and + libboost_regex-gcc-d-1_32.a). When you build projects that use regex++, you + will need to add the boost install directory to your list of include paths and + add <boost>/libs/regex/build/gcc/libboost_regex-gcc-1_32.a to your list + of library files.
There is also a makefile to build the library as a shared library:
make -fgcc-shared.mak-
which will build libboost_regex.so and libboost_regex_debug.so.
+which will build libboost_regex-gcc-1_32.so and + libboost_regex-gcc-d-1_32.so.
Both of the these makefiles support the following environment variables:
CXXFLAGS: extra compiler options - note that this applies to both the debug and release builds.
@@ -181,8 +181,8 @@LDFLAGS: additional linker options.
LIBS: additional library files.
For the more adventurous there is a configure script in - <boost>/libs/config; see the config library - documentation.
+ <boost>/libs/config; see the config + library documentation.There is a makefile for the sun (6.1) compiler (C++ version 3.12). From the command prompt change to the <boost>/libs/regex/build directory and type: @@ -212,8 +212,8 @@ ) provided in <boost-root>/libs/regex/build - see that makefile for details of environment variables that need to be set before use.
- Alternatively you can using the Jam based - build system: cd into <boost>/libs/regex/build and run:
bjam -sTOOLS=mytoolset+ Alternatively you can using the Jam + based build system: cd into <boost>/libs/regex/build and run:
bjam -sTOOLS=mytoolset
If you need to configure the library for your platform, then refer to the config library documentation @@ -226,8 +226,7 @@ 24 Oct 2003
© Copyright John Maddock 1998- - - 2003
+ 2003Use, modification and distribution are subject to the Boost Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
diff --git a/doc/install.html b/doc/install.html index 54c3ddd5..92241e2b 100644 --- a/doc/install.html +++ b/doc/install.html @@ -132,25 +132,24 @@ Microsoft's Compiler:You can build with gcc using the normal boost Jamfile in - <boost>/libs/regex/build, alternatively there is a conservative makefile - for the g++ compiler. From the command prompt change to the - <boost>/libs/regex/build directory and type: +
The best way to build with gcc is using the + normal boost Jamfile in <boost>/libs/regex/build, alternatively + there is a conservative makefile for the g++ compiler. From the command prompt + change to the <boost>/libs/regex/build directory and type:
make -fgcc.mak
At the end of the build process you should have a gcc sub-directory containing - release and debug versions of the library (libboost_regex.a and - libboost_regex_debug.a). When you build projects that use regex++, you will - need to add the boost install directory to your list of include paths and add - <boost>/libs/regex/build/gcc/libboost_regex.a to your list of library - files. + release and debug versions of the library (libboost_regex-gcc-1_32.a and + libboost_regex-gcc-d-1_32.a). When you build projects that use regex++, you + will need to add the boost install directory to your list of include paths and + add <boost>/libs/regex/build/gcc/libboost_regex-gcc-1_32.a to your list + of library files.
There is also a makefile to build the library as a shared library:
make -fgcc-shared.mak-
which will build libboost_regex.so and libboost_regex_debug.so.
+which will build libboost_regex-gcc-1_32.so and + libboost_regex-gcc-d-1_32.so.
Both of the these makefiles support the following environment variables:
CXXFLAGS: extra compiler options - note that this applies to both the debug and release builds.
@@ -181,8 +181,8 @@LDFLAGS: additional linker options.
LIBS: additional library files.
For the more adventurous there is a configure script in - <boost>/libs/config; see the config library - documentation.
+ <boost>/libs/config; see the config + library documentation.There is a makefile for the sun (6.1) compiler (C++ version 3.12). From the command prompt change to the <boost>/libs/regex/build directory and type: @@ -212,8 +212,8 @@ ) provided in <boost-root>/libs/regex/build - see that makefile for details of environment variables that need to be set before use.
- Alternatively you can using the Jam based - build system: cd into <boost>/libs/regex/build and run:
bjam -sTOOLS=mytoolset+ Alternatively you can using the Jam + based build system: cd into <boost>/libs/regex/build and run:
bjam -sTOOLS=mytoolset
If you need to configure the library for your platform, then refer to the config library documentation @@ -226,8 +226,7 @@ 24 Oct 2003
© Copyright John Maddock 1998- - - 2003
+ 2003Use, modification and distribution are subject to the Boost Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)