2 # run the configure script for a native Windows build
4 if [ -f ../configure.in ]; then
5 # we're in the windows directory, so we need to go up a level
9 if [ ! -f configure ]; then
16 ####### configure options:
17 # --help Show configure options and a short description
19 # --host=i686-w64-mingw32 Use the mingw cross-compiler to build a 'native' windows binary
20 # --enable-mingw32 Use mingw32 for a Windows GUI
21 # --enable-static-linking Use static linking instead of dynamic linking (and not have
22 # to put all the .DLLs in the path or the same dir as Privoxy)
23 # --disable-pthread Use native threads instead of POSIX pthreads library
24 # --disable-dynamic-pcre Use the built-in, static pcre, even if libpcre is available
25 # --with-docbook=yes Enable docbook documentation creation
29 # note: configure.in line 155
30 # if test "X$CFLAGS" = "X "; then # if CFLAGS were unset (see above)
31 # In other words, if you set CFLAGS you need to include -O2 if you want optimization
32 # assume I'll set cflags below, so set O2 now
35 # start with initially empty flags
38 # start with initially empty flags
41 CFLAGS="${CFLAGS} -fstack-protector-strong -D_FORTIFY_SOURCE=2"
42 LDFLAGS="${LDFLAGS} -fstack-protector-strong"
43 # -fstack-protector-strong: enable stack checking.
44 # NOTE: need to specify when compiling _and_ linking
45 # stack-protector-strong: better balance between security and performance.
46 # This flag protects more kinds of vulnerable functions than -fstack-protector does,
47 # but not every function, providing better performance than -fstack-protector-all.
48 # see : https://en.wikipedia.org/wiki/Buffer_overflow_protection
49 # NOTE: needs static linking or the following in the path:
50 # /usr/i686-w64-mingw32/sys-root/mingw/bin/libssp-0.dll
52 # -D_FORTIFY_SOURCE: detect some buffer overflow errors
53 # ***>> requires compiler optimization level 1 or above <<***
54 # see : https://gcc.gnu.org/legacy-ml/gcc-patches/2004-09/msg02055.html
55 # The diffence between -D_FORTIFY_SOURCE=1 and -D_FORTIFY_SOURCE=2 is e.g. for
56 # struct S { struct T { char buf[5]; int x; } t; char buf[20]; } var;
57 # With -D_FORTIFY_SOURCE=1,
58 # strcpy (&var.t.buf[1], "abcdefg");
59 # is not considered an overflow (object is whole VAR), while with -D_FORTIFY_SOURCE=2
60 # strcpy (&var.t.buf[1], "abcdefg");
61 # will be considered a buffer overflow.
63 ### CFLAGS="${CFLAGS} -march=native"
65 # Generate instructions for the machine type cpu-type. In contrast to -mtune=cpu-type, which merely tunes the
66 # generated code for the specified cpu-type, -march=cpu-type allows GCC to generate code that may not run at all on
67 # processors other than the one indicated.
68 # Specifying -march=cpu-type implies -mtune=cpu-type.
71 # This selects the CPU to generate code for at compilation time by determining the processor type of the compiling
72 # machine. Using -march=native enables all instruction subsets supported by the local machine (hence the result
73 # might not run on different machines). Using -mtune=native produces code optimized for the local machine under
74 # the constraints of the selected instruction set.
76 LDFLAGS="${LDFLAGS} -Wl,--nxcompat"
77 # https://en.wikipedia.org/wiki/Data_Execution_Prevention
78 # Enable DEP with -Wl,--nxcompat
80 LDFLAGS="${LDFLAGS} -Wl,--dynamicbase,--export-all-symbols"
81 # https://en.wikipedia.org/wiki/Address_space_layout_randomization
82 # https://stackoverflow.com/questions/24283918/how-can-i-enable-aslr-dep-and-safeseh-on-an-exe-in-codeblocks-using-mingw
83 # ASLR with gcc has a problem: -Wl,--dynamicbase doesn't emit the necessary relocation table.
84 # As a workaround, you can pass -Wl,--dynamicbase,--export-all-symbols
85 # NOTE: you can't have both this and profiling (cflags='-pg') enabled!
87 CFLAGS="${CFLAGS} -Wall"
88 # see: http://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html
89 # -Wall doesn't actually turn on all warnings, so add -Wextra
90 # but then plenty too many complaints by
91 # -Wimplicit-fallthrough=3
92 # too many warnings in pcre/study.c & pcre.c
93 # -Wmissing-field-initializers
96 # -Wunused-but-set-parameter
97 # -Wunused-but-set-variable
98 CFLAGS="${CFLAGS} -Wextra -Wno-missing-field-initializers -Wno-sign-compare -Wno-type-limits"
99 CFLAGS="${CFLAGS} -Wno-unused-parameter -Wno-unused-but-set-variable"
101 #-no-# CFLAGS="${CFLAGS} -Wconversion"
102 # way too many warnings for things that don't look like a problem
104 #-no-# CFLAGS="${CFLAGS} -Werror"
105 # Turn all warnings into errors.
106 # Privoxy still has a few warnings that are not a problem
108 CFLAGS="${CFLAGS} -Wformat=2"
109 # -Wformat is enabled by -Wall.
110 # -Wformat=2 is equivalent to -Wformat -Wformat-nonliteral -Wformat-security -Wformat-y2k
111 # -Wformat-security : also warn about uses of format functions that represent possible security problems.
113 CFLAGS="${CFLAGS} -Wlogical-op"
114 # Warn about suspicious uses of logical operators in expressions.
116 CFLAGS="${CFLAGS} -Wshadow"
117 # Warn whenever a local variable or type declaration shadows
118 # another variable or whenever a built-in function is shadowed.
120 #-no-# CFLAGS="${CFLAGS} -Wwrite-strings"
121 # These warnings help you find at compile time code that can try to write
122 # into a string constant, but only if you have been very careful about
123 # using const in declarations and prototypes.
124 # >>> Otherwise, it is just a nuisance. <<< -- this, very much this
126 echo "CFLAGS=${CFLAGS}"
127 echo "CPPFLAGS=${CPPFLAGS}"
128 echo "LDFLAGS=${LDFLAGS}"
130 # ./configure cross-compilation options:
131 # --build: the system on which the program will be built.
132 # --host: the system on which the generated program will run.
133 # --target: only used to build a cross-compiling toolchain.
135 ./configure --host=i686-w64-mingw32 --enable-mingw32 --enable-zlib \
136 --enable-static-linking \
137 --enable-strptime-sanity-checks \
139 --disable-dynamic-pcre \
140 --enable-extended-statistics \
141 --enable-pcre-host-patterns \