README.md
1regex project
2-----------
3
4Build 20:11 2017-08-07 - forked github.com/garyhouston/regex
5
6Needed a stable WIN32 source and build of regex, to include in other projects.
7
8Added a CMake - CMakeLists.txt - build. Depending on the MSVC version installed, should be able to use the build-me.bat in the `build` folder. But if not the command line steps are simple -
9
10```
11> cd build
12> cmake .. [options]
13> cmake --build . --config Release
14```
15
16This should get the static `regex.lib`, and a `re-test.exe` built. Note, the `re-test` app has not been tested in Windows...
17
18The previous Makefile instructions are left below, but are unlikely to work in a native Windows MSVC build environment...
19
20Previous OLD README:
21--------
22
23Was alpha3.8 release. Tue Aug 10 15:51:48 EDT 1999 henry@spsystems.net (formerly henry@zoo.toronto.edu)
24
25See WHATSNEW for change listing.
26
27Read the comments at the beginning of Makefile before running.
28
29Utils.h contains some things that just might have to be modified on
30some systems, as well as a nested include (ugh) of <assert.h>.
31
32The "fake" directory contains quick-and-dirty fakes for some header
33files and routines that old systems may not have. Note also that
34-DUSEBCOPY will make utils.h substitute bcopy() for memmove().
35
36After that, "make r" will build regcomp.o, regexec.o, regfree.o,
37and regerror.o (the actual routines), bundle them together into a test
38program, and run regression tests on them. No output is good output.
39
40"make lib" builds just the .o files for the actual routines (when
41you're happy with testing and have adjusted CFLAGS for production),
42and puts them together into libregex.a. You can pick up either the
43library or *.o ("make lib" makes sure there are no other .o files left
44around to confuse things).
45
46Main.c, debug.c, split.c are used for regression testing but are not part
47of the RE routines themselves.
48
49Regex.h goes in /usr/include. All other .h files are internal only.
50
51; eof
52