According to Kevin P Lawton ([EMAIL PROTECTED]):
> The other issue that comes up, is how to ./configure the source
> so it can be compiled in Win32/MSVC++ land. There's enough variables
> that it kinda blows having to manage two build environments. One
> solution I had thought of for non-configure-capable systems was
> this. Have a web page (on a Unix machine) that would run configure
> for you and configure for a Win32/MSVC++. Then it offers you
> a *.zip file which is the source distro with all the Makefiles
> and config.h files generated for you.
Win32 is rather standardized (unlike UNIX, which is better in other
things... :)), so I guess it would be enough to supply a 'makefile.w32'.
You might also want to look at how the Apache guys did this, as they're also
maintaining both a UNIX and a Win32 version from the same source tree.
> Since there will likely be lot's of configure options, this would need to
> be dynamic; you could enter in configure options on the web page,
> and it would pass them all to configure, and custom build a
> *.zip source distro for you, on demand.
>
> If this idea is well received, it would make a great web project
> for someone willing.
I'd be willing to program this though (easy in PHP3), but I guess the server
running something like that will crash whenever we release a new version
(unless you use something like a 128 xeon 600 beowulf cluster... :^))
Wouter
--
* Wouter Coene * Linux/sed/PHP3/OS development *
* Mail: [EMAIL PROTECTED] * PGP key on request *
Daily crap:
It is much easier to suggest solutions when you know nothing about the problem.
