Topic: VC15 builds 2.4.26-dev with OpenSSL 1.1.0e :: Updated

[Steffen]

Made a VC15 build available.

Apachelounge is running it now, and chrome is now picking strong cipher CHACHA20_POLY1305.
Using the recommended at https://wiki.mozilla.org/Security/Server_Side_TLS#Intermediate_compatibility_.28default.29


26 April 2017 : mod_brotli added, more info and configuration see https://www.apachelounge.com/viewtopic.php?p=35265

24 April 2017 : updated mod_http2 to 1.10.3, Change log mod_http2: https://github.com/icing/mod_h2/releases


Changes over current 2.4.25:
httpd 2.4.26-dev
apr 1.6.1-dev
apr-util 1.6.1-dev
openssl 1.1.0e
nghttp2 1.21.1
mod_http2 1.10.3
Datailed httpd, apr and apr-util changelog is in the .zip.

We are going only ship OpenSSL 1.1 with VC15.

Also the next PHP 7.2 will be shipped with VC15 and OpenSSL 1.1, on windows.php.net is already a master snapshot which is becoming 7.2. The PHP team has already tested with our VC15 build. Policy is/was to keep in sync with PHP.

VC15 is backward compatible with VC14 modules, so VC14 users can easy upgrade to VC15.

See the notes on the VC15 download page.

See also https://www.apachelounge.com/viewtopic.php?p=35294#35294

[Steffen]

Updated mod_http2 to 1.10.3

Change log mod_http2: https://github.com/icing/mod_h2/releases

[Steffen]

Most used modules mod_fcgid and mod_security now available for VC15.

The rest Vc14 is coming later.

You can use VC14 modules.

With VS2017 (VC15) the runtime binary is backward compatible with VS2015 (VC14)

Only Be sure !! that you have installed the latest C++ Redistributable Visual Studio 2017. After you install it, the C++ Redistributable VS2015 is removed

Note form MS:
There are a lot of improvements in the C++ compilers and libraries in this release of Visual Studio that will entice you to move to Visual Studio 2017's latest toolset (v141) - new standard conformance features, improved codegen, faster build throughput. You may be worried however that your third-party library dependencies are not ready for such a jump. We often hear from customers that this is the number one migration blocker to a new C++ toolset (whether they consume dependencies as binaries or even directly as source).

With the latest MSVC toolset however, you don't need to worry about this at all. That's simply because the latest VC Runtime is binary compatible with the VS 2015's VC Runtime. In other words, if you have a library built with the v140 platform toolset, that binary and your code consuming it will continue to work even if you built your code with the v141 MSVC toolset.

[Steffen]

Added mod_brotli, with help of Gregg.

For more info and configuration see https://www.apachelounge.com/viewtopic.php?p=35265

[kermit]

Hi,
I downloaded httpd-2.4.26-Dev-Win64-VC15 and its 32bit equivalent yesterday. I notice that the apr-1.lib and aprutil-1.lib files distributed in the 64bit package are the files from the 32bit package. This is a bit of a problem, since the 64bit linker won't link to them (warning LNK4272: library machine type 'X86' conflicts with target machine type 'x64'). I wonder if you could rebuild them targeted to X64?

Regards,
Ty

[Steffen]

Oops, wrong copy of that two files for building, the rest is ok.

Updated the two files in the .zip.

Ps.
For running Apache you do not have to download again, only when you build third party modules.

[kermit]

Excellent, thanks so much! Everything works fine!