Apache module creation for Windows

I've been trying to use Cygwin and DJGPP, and I'm suspecting they're
completely the wrong tools. Both of them freak out with the Apache
header files. Do I need to pull out Visual Studio? The guide I've
been trying to follow assumes I'm on a Linux machine. On top of that,
it seems to be making my life entirely too complicated by using
automake and autoconf. So it's rather difficult to figure out where
I'm going wrong.

John Boozer

John Boozer wrote:
> I've been trying to use Cygwin and DJGPP, and I'm suspecting they're
> completely the wrong tools. Both of them freak out with the Apache
> header files. Do I need to pull out Visual Studio? The guide I've
> been trying to follow assumes I'm on a Linux machine. On top of that,
> it seems to be making my life entirely too complicated by using
> automake and autoconf. So it's rather difficult to figure out where
> I'm going wrong.

If you have access to Visual Studio, that's definitely your best option
since that's what apache.org uses (see
http://httpd.apache.org/docs/win_compiling.html and
http://httpd.apache.org/docs-2.0/pla...compiling.html).

Cygwin is, apparently, a viable option for Apache 1.3 according to the
Apache site (http://httpd.apache.org/docs/cygwin.html), but I don't know
if anyone has Apache 2 building with Cygwin. Which version are you
looking to build modules for? In any case, you'll need to build
everything with Cygwin; don't expect Cygwin modules to work in a Visual
Studio build of Apache.

If you're using Cygwin, you should likely pull down the Unix source kit
(.tar.gz files) rather than the Windows one (.zip). The CR-LF
terminators in the Windows kit might be causing trouble (I'm not quite
sure but I seem to recall seeing that kind of thing when I tried
building on Unix from the .zip file).

As for DJGPP, I haven't heard of Apache being built in that environment.
Isn't it meant for building 32-bit code to run in protected mode DOS? It
would be an interesting test for DJGPP but it's hardly a mainstream
environment any more.

--
Jim Patterson
Ottawa, Ont
CANADA

Jim Patterson <jim-patterson@ncf.ca> wrote in message news:<QQ28d.8947$jj2.339607@news20.bellglobal.com> ...
> John Boozer wrote:
> > I've been trying to use Cygwin and DJGPP, and I'm suspecting they're
> > completely the wrong tools. Both of them freak out with the Apache
> > header files. Do I need to pull out Visual Studio? The guide I've
> > been trying to follow assumes I'm on a Linux machine. On top of that,
> > it seems to be making my life entirely too complicated by using
> > automake and autoconf. So it's rather difficult to figure out where
> > I'm going wrong.
>
> If you have access to Visual Studio, that's definitely your best option
> since that's what apache.org uses (see
> http://httpd.apache.org/docs/win_compiling.html and
> http://httpd.apache.org/docs-2.0/pla...compiling.html).
>
> Cygwin is, apparently, a viable option for Apache 1.3 according to the
> Apache site (http://httpd.apache.org/docs/cygwin.html), but I don't know
> if anyone has Apache 2 building with Cygwin. Which version are you
> looking to build modules for? In any case, you'll need to build
> everything with Cygwin; don't expect Cygwin modules to work in a Visual
> Studio build of Apache.
>
> If you're using Cygwin, you should likely pull down the Unix source kit
> (.tar.gz files) rather than the Windows one (.zip). The CR-LF
> terminators in the Windows kit might be causing trouble (I'm not quite
> sure but I seem to recall seeing that kind of thing when I tried
> building on Unix from the .zip file).
>
> As for DJGPP, I haven't heard of Apache being built in that environment.
> Isn't it meant for building 32-bit code to run in protected mode DOS? It
> would be an interesting test for DJGPP but it's hardly a mainstream
> environment any more.

Thanks. That's what I was suspecting. I dusted off my old copy of
Visual C++ and it compiled the module just fine.