As I already wrote, the most important issue is not having the same
steps for building, but to have the same tree for both Windows and
UNIX. It is easy to do, and has a lot of benefits.
In your tree, you achieved this purpose, and I think it is possible
to add support for UNIX, so build/installation of Apache plus so
many modules and patches under UNIX will be as easy as Windows. And
don't forget; Originally, it was Windows where the build was so
hard...
Daniel S. Reichenbach wrote:
>
> > > ....
> > > Just run a single "nmake" in Apache_1.3.x\src and then "nmake
> > > install" and that`s it.
> >
> > Although it is a very positive progress, it is not what I meant. I
> > want a shared distribution for all the platforms, which can be built
> > simply (1-2 steps rather than dozens of steps and packages to load
> > from the net), under ALL of the platforms. Similar steps are not the
> > important thing (though they may help; BTW: Why don't you create a
> > batch file "make.bat" which will call nmake and translate its
> > parameters to nmake's syntax?). The important thing is that the ease
> > of build and installation that you achieved for Windows users, will
> > be shared by the UNIX users too.
> Hmm, little batch file could be done. If we do this, anyone could
> type "make" on both Unix and Win32 and get the compiled Apache ? So
> our "make.bat" would have to mimic the behaviour of a Unix makefile
> and you could do things like "make install" or in the case of mod_ssl
> "make certificate TYPE=..."? We would still have seperated builds.
> In that case we need the .sh files from mod_ssl as batches, too.
>
> I`m not sure, if this is the right way. Would`t it seperate the build
> process a bit more? Sounds like having the same things to do on all
> plattforms, but all on different ways.
>
> How about Cygwin32? This sounds cleaner to me. We could change the
> makefiles to detect Cygwin32 and then do the same things for Win32
> as under Unix. ?
--
Eli Marmor
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
