Lines Matching +full:cmake +full:- +full:3
2 --------------------------------------
12 Building PCRE2 on Windows with CMake
25 configure/make (autotools) build system, as found in many Unix-like
29 There is also support for CMake, which some users prefer, especially in Windows
30 environments, though it can also be run in Unix-like environments. See the
31 section entitled "Building PCRE2 on Windows with CMake" below.
35 provided for those who build PCRE2 without using "configure" or CMake. If you
36 use "configure" or CMake, the .generic versions are not used.
42 hand". If you are going to use CMake, this section does not apply to you; you
43 can skip ahead to the CMake section.
52 -DHAVE_CONFIG_H to your compiler so that src/config.h is included in the
55 An alternative approach is not to edit src/config.h, but to use -D on the
57 configuration options. In this case -DHAVE_CONFIG_H must not be set.
63 before re-using what you had previously.
67 (3) EITHER:
72 Compile src/dftables.c as a stand-alone program (using -DHAVE_CONFIG_H
77 that is specified by LC_xxx environment variables, add the -L option to
84 (4) For an 8-bit library, compile the following source files from the src
85 directory, setting -DPCRE2_CODE_UNIT_WIDTH=8 as a compiler option. Also
86 set -DHAVE_CONFIG_H if you have set up src/config.h with your
87 configuration, or else use other -D settings to change the configuration
117 Make sure that you include -I. in the compiler command (or equivalent for
120 the risk of picking up a previously-installed file from somewhere else.
135 your system keeps such libraries. This is the basic PCRE2 C 8-bit library.
139 (6) If you want to build a 16-bit library or 32-bit library (as well as, or
140 instead of the 8-bit library) just supply 16 or 32 as the value of
141 -DPCRE2_CODE_UNIT_WIDTH when you are compiling.
144 8-bit library), ensure that you have the src/pcre2posix.h file and then
148 (8) The pcre2test program can be linked with any combination of the 8-bit,
149 16-bit and 32-bit libraries (depending on what you selected in
150 src/config.h). Compile src/pcre2test.c; don't forget -DHAVE_CONFIG_H if
152 appropriate library/ies. If you compiled an 8-bit library, pcre2test also
158 in the README file. If you compiled more than one of the 8-bit, 16-bit and
159 32-bit libraries, you need to run pcre2test with the -16 option to do
160 16-bit tests and with the -32 option to do 32-bit tests.
162 Some tests are relevant only when certain build-time options are selected.
165 file. If you have a suitable Unix-like shell, the RunTest script will run
174 by running pcre2test with the -jit option. This is done automatically by
179 src/pcre2grep.c; it uses only the basic 8-bit PCRE2 library (it does not
183 it is run with --no-jit). If you define SUPPORT_PCRE2GREP_JIT without
197 a non-dll .a file, you must define PCRE2_STATIC before including src/pcre2.h.
211 COMMENTS ABOUT WIN32 BUILDS (see also "BUILDING PCRE2 ON WINDOWS WITH CMAKE")
216 support for building using CMake, which some users find a more straightforward
224 3rd-party C runtime DLLs.
228 Cygwin is a Linux-like environment for Windows. It consists of two parts:
239 This should create two libraries called libpcre2-8 and libpcre2-posix. These
240 are independent libraries: when you link with libpcre2-posix you must also link
241 with libpcre2-8, which contains the basic functions.
256 If a Cygwin user uses the -mno-cygwin Cygwin gcc flag, what that really does is
262 -mno-cygwin.
273 BUILDING PCRE2 ON WINDOWS WITH CMAKE
275 CMake is an alternative configuration facility that can be used instead of
276 "configure". CMake creates project files (make files, solution files, etc.)
279 spaces in the names for your CMake installation and your PCRE2 source and build
284 event that errors do occur, it is recommended that you delete the CMake cache
285 before attempting to repeat the CMake build process. In the CMake GUI, the
288 1. Install the latest CMake version available from http://www.cmake.org/, and
289 ensure that cmake\bin is on your path.
296 3. Create a new, empty build directory, preferably a subdirectory of the
297 source dir. For example, C:\pcre2\pcre2-xx\build.
299 4. Run cmake-gui from the Shell envirornment of your build tool, for example,
301 to start Cmake from the Windows Start menu, as this can lead to errors.
303 5. Enter C:\pcre2\pcre2-xx and C:\pcre2\pcre2-xx\build for the source and
321 cmake-gui and use the generated build system with your compiler or IDE.
326 12. If during configuration with cmake-gui you've elected to build the test
338 portable and permissively-licensed implementation of the header worked without
348 If configured with CMake, building the test project ("make test" or building
369 set srcdir=C:\pcre2\pcre2-10.00
371 3. In a Windows command environment, chdir to the location of your bat and
377 To independently test the just-in-time compiler, run pcre2_jit_test.exe.