The nmake files are all exported from Visual Studio 98... Last flavor which
allowed exporting, and effectively impossible to provision without ancient
MSDN CDs, because the product distribution ended to comply with the
I still have this tool chain in an ancient Windows 2003 VM if something
more is needed. But aside from vcproj consumers who want
rebuild-restart-debug functionality, the only sane path to 'makefiles'
these days is cmake, IMO.
+1 to mod_md progress you noted :) CMakeFiles.txt may need to be caught up.
I've noticed 2.5.0-alpha is out of sync with 2.4.x branch w.r.t. win32
makefile.win. another holiday weekend project, heh.
On Nov 16, 2017 05:17, "Michal Karm" <michal.baba...@gmail.com> wrote:
On 11/16/2017 10:58 AM, Stefan Eissing wrote:
> A big thanks to Steffen and Gregg for their inhuman efforts to get mod_md
building on Windows. I think they are pretty close now, afaik, but if you
build Apache on Windows, they sure can need another tester.
> Also many thanks to Rainer for cleaning up my .o/.slo mess. He fixed what
I could not get working properly.
I have APR and a few modules in a small public Windows CI,
so I thought I would give mod_md a shot there.
Although, I cannot see any CMakeLists.txt to start with  (no intention to
re-start CMake vs. "native" .vcproj flame)
Or do you guys hand-craft NMake files?
Any hints? Have I missed anything obvious on the list?
Michal Karm Babacek
Sent from my Hosaka Ono-Sendai Cyberspace 7