17-Nov-98 11:37 you wrote:
>> 2) in Makefile.nt you invoke mod_ssl's makefile with
>>
>> nmake /nologo CFG="mod_ssl - Win32 %LONG%" -f Makefile
>> nmake /nologo CFG="mod_ssl - Win32 %LONG%" -f Makefile clean
>> ...
>>
>> The define CFG="mod_ssl - Win32 %LONG%" has nothing to do here. The
>> other .mak need it, because they are generated by DevStudio, and it's
>> the way they do it. Our Makefile is hand written. Also nmake looks for
>> 'makefile' by default, so no need to use the -f option. You can just
>>
>> nmake /nologo all # or without 'all'
>> nmake /nologo clean
> I've removed the CFG=... and added the "all", but the "-f Makefile" I want to
> leave as "/f Makefile" just to make sure this "broken platform" tools do what
> they should do (perhaps "makefile vs. Makefile" or whatever next M$ break in
> new releases of their VC++ stuff :-( ).
Makefile and makefile (and MAKEFILE -- in fact this is name of "main file" for
nmake) is one file under Windows 9x/NT and nmake will find this file by default
(at least nmake from Microsoft C 5.0, Microsoft C 6.0, Microsoft C/C++ 7.0,
Microsoft C/C++ 8.0 AKA MS VC++ 1.0, MS VC++ 1.5x, MS VC++ 2.0, MS VC++ 4.x
(MS VC++ 3.x was skipped by MS, not by me :-), MS VC++ 5.0 and MS VC++ 6.0).
Since nmake was able to find MAKEFILE for last 15 years I bet this will be so
in the future as well and if not then Makefile will be not supported at all :-)
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
