Lines Matching +full:cmake +full:- +full:3
2 --------------------------------------
16 Building PCRE2 on Windows with CMake
28 configure/make (autotools) build system, as found in many Unix-like
32 There is also support for CMake, which some users prefer, especially in Windows
33 environments, though it can also be run in Unix-like environments. See the
34 section entitled "Building PCRE2 on Windows with CMake" below.
38 provided for those who build PCRE2 without using "configure" or CMake. If you
39 use "configure" or CMake, the .generic versions are not used.
45 hand". If you are going to use CMake, this section does not apply to you; you
46 can skip ahead to the CMake section.
55 -DHAVE_CONFIG_H to your compiler so that src/config.h is included in the
58 An alternative approach is not to edit src/config.h, but to use -D on the
60 configuration options. In this case -DHAVE_CONFIG_H must not be set.
66 before re-using what you had previously.
70 (3) EITHER:
75 Compile src/dftables.c as a stand-alone program (using -DHAVE_CONFIG_H
80 that is specified by LC_xxx environment variables, add the -L option to
87 (4) For an 8-bit library, compile the following source files from the src
88 directory, setting -DPCRE2_CODE_UNIT_WIDTH=8 as a compiler option. Also
89 set -DHAVE_CONFIG_H if you have set up src/config.h with your
90 configuration, or else use other -D settings to change the configuration
118 Make sure that you include -I. in the compiler command (or equivalent for
121 the risk of picking up a previously-installed file from somewhere else.
132 your system keeps such libraries. This is the basic PCRE2 C 8-bit library.
136 (6) If you want to build a 16-bit library or 32-bit library (as well as, or
137 instead of the 8-bit library) just supply 16 or 32 as the value of
138 -DPCRE2_CODE_UNIT_WIDTH when you are compiling.
141 8-bit library), ensure that you have the src/pcre2posix.h file and then
145 (8) The pcre2test program can be linked with any combination of the 8-bit,
146 16-bit and 32-bit libraries (depending on what you selected in
147 src/config.h). Compile src/pcre2test.c; don't forget -DHAVE_CONFIG_H if
149 appropriate library/ies. If you compiled an 8-bit library, pcre2test also
155 in the README file. If you compiled more than one of the 8-bit, 16-bit and
156 32-bit libraries, you need to run pcre2test with the -16 option to do
157 16-bit tests and with the -32 option to do 32-bit tests.
159 Some tests are relevant only when certain build-time options are selected.
162 file. If you have a suitable Unix-like shell, the RunTest script will run
171 by running pcre2test with the -jit option. This is done automatically by
176 src/pcre2grep.c; it uses only the basic 8-bit PCRE2 library (it does not
187 are using CMake (see "BUILDING PCRE2 ON WINDOWS WITH CMAKE" below) and the gcc
189 setting the CMAKE_EXE_LINKER_FLAGS variable to "-Wl,--stack,8388608" (for
202 a non-dll .a file, you must define PCRE2_STATIC before including src/pcre2.h.
216 COMMENTS ABOUT WIN32 BUILDS (see also "BUILDING PCRE2 ON WINDOWS WITH CMAKE")
221 support for building using CMake, which some users find a more straightforward
229 3rd-party C runtime DLLs.
233 Cygwin is a Linux-like environment for Windows. It consists of two parts:
244 This should create two libraries called libpcre2-8 and libpcre2-posix. These
245 are independent libraries: when you link with libpcre2-posix you must also link
246 with libpcre2-8, which contains the basic functions.
261 If a Cygwin user uses the -mno-cygwin Cygwin gcc flag, what that really does is
267 -mno-cygwin.
278 BUILDING PCRE2 ON WINDOWS WITH CMAKE
280 CMake is an alternative configuration facility that can be used instead of
281 "configure". CMake creates project files (make files, solution files, etc.)
284 spaces in the names for your CMake installation and your PCRE2 source and build
289 event that errors do occur, it is recommended that you delete the CMake cache
290 before attempting to repeat the CMake build process. In the CMake GUI, the
293 1. Install the latest CMake version available from http://www.cmake.org/, and
294 ensure that cmake\bin is on your path.
301 3. Create a new, empty build directory, preferably a subdirectory of the
302 source dir. For example, C:\pcre2\pcre2-xx\build.
304 4. Run cmake-gui from the Shell envirornment of your build tool, for example,
306 to start Cmake from the Windows Start menu, as this can lead to errors.
308 5. Enter C:\pcre2\pcre2-xx and C:\pcre2\pcre2-xx\build for the source and
326 cmake-gui and use the generated build system with your compiler or IDE.
331 12. If during configuration with cmake-gui you've elected to build the test
341 If configured with CMake, building the test project ("make test" or building
362 set srcdir=C:\pcre2\pcre2-10.00
364 3. In a Windows command environment, chdir to the location of your bat and
370 To independently test the just-in-time compiler, run pcre2_jit_test.exe.