On Fri, Apr 28, 2017 at 11:35 AM, Jan Ehrhardt <php...@ehrhardt.nl> wrote:
> William A Rowe Jr in gmane.comp.apache.devel (Fri, 28 Apr 2017 10:30:03
>>You might have missed my thought here... suggesting that the CMake
>>not-so-experimental build become recommended for users who want to
>>build all the modules in one go including the new mod_brotli.
> People like Steffen, Gregg and me disagree with you on making CMake the
> only way for building Apache and all the modules in one go.
And until brotli (topic of current discussion) it was convenient to hide behind
the fact that CMake wasn't necessary. Now that the *majority* of httpd project
dependencies must all be configured using cmake (and build with one of a
number of actual toolchains, including your favored Visual Studio GUI view,
msbuild, nmake makefiles, even eclipse etc etc etc.) the most compelling
reason to ship .mak + .dsp has now evaporated.
I will never invoke devenv.exe "target" from the CMake output, I like the
simpler forms better, but I'm happy to help diagnose anything that CMake
is doing wrong in emitting the vcproj or makefile output for your consumption.
The lack of understanding of why these libs exist in the .mak and not in the
.dep files Gregg updated illustrates that the old .dsp files are no longer of
any substantive value. As I mentioned earlier, I haven't used the .dsw or
these resulting .mak files in a decade because my httpd.exe+++ build all
seeks an installed tree expat/pcre/apr/openssl/libxml2/zlib (ultimately, the
final install prefix for httpd), and I can fix everything by munging INCLUDE
and LIB envvars vs. a nightmare of unpacking sources into directories of
different names than their source distribution, keeping up with build tree
restructuring by the maintainers, or munging .dsp/.mak files.