You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "William A. Rowe, Jr." <wr...@rowe-clan.net> on 2000/12/12 22:17:34 UTC

Win32 completed

> From: William A. Rowe, Jr. [mailto:wrowe@rowe-clan.net]
> Sent: Tuesday, December 12, 2000 12:53 PM
> 
> The mpm_winnt.c problem is resolved...
> 
> Clean checkout and build looks good, install is incomplete but
> should work for a user that knows the usual s/@@ServerRoot@@/foo/
> and can put the right conf files in place (I blew it... forgot
> mime.types, and pointed my ServerRoot in the wrong directory
> so I paniced that we didn't have error logging right!)
> 
> However, it brings up an issue... Alpha downloaders won't 
> instinctively know to look for the default conf files buried
> over in docs ... any solutions?  I'll have a simple perl solution
> cooked up asap to do the install as part of Makefile.win.

Using a bit of make+perl magic, Makefile.win now installs the correct
conf/httpd.conf-default, conf/mime.types-default, conf/magic-default
and the htdocs/manual tree.  If they do not exist, it also installs 
the conf/httpd.conf, conf/mime.types, conf/magic and htdocs/index.html.*
files into the user's tree.

I guess this is as good a time as any to implement and begin debate.
If you don't like this solution, speak up.

Re: Win32 completed

Posted by Bill Stoddard <bi...@wstoddard.com>.
> >
> > However, it brings up an issue... Alpha downloaders won't
> > instinctively know to look for the default conf files buried
> > over in docs ... any solutions?  I'll have a simple perl solution
> > cooked up asap to do the install as part of Makefile.win.
>
> Using a bit of make+perl magic, Makefile.win now installs the correct
> conf/httpd.conf-default, conf/mime.types-default, conf/magic-default
> and the htdocs/manual tree.  If they do not exist, it also installs
> the conf/httpd.conf, conf/mime.types, conf/magic and htdocs/index.html.*
> files into the user's tree.
>
> I guess this is as good a time as any to implement and begin debate.
> If you don't like this solution, speak up.
>
The big issue here is whether we want to require perl to do Apache builds on
Windows.  Are perl interpreters for Windows freely available -for commercial
use-?

Bill