I was going to take a look at this too (although I barely know what I am
doing). The first thing I have noticed is that the toolkit only comes
with the compiler and linker (CL and LINK) it does not come with the NMAKE
or MSDEV programs, both of which are used by the current build process. So
you would have to find a suitable make tool to replace NMAKE and then
probably wrapper it all in a batch file that runs all of the makes. Also,
it is possible the existing make files might have to be tweaked to handle
differences between nmake and whatever make tool you used.
Does anyone know if there are settings that can be passed to gen-make.py
to generate "standard" make files that might work for this?
Finally to do a full build, something would have to be done to the Apache
build process to accomodate all of this. Maybe someone in the Apache
world is already working on this. Correct me if I am wrong, but I believe
you can build the complete Subversion client without building Apache. The
latter is only needed to be build the Apache server modules.
It would be nice if this could work with this compiler. I know I have
seen messages on this list in the past from some Subversion developers
that run on Linux that have said they have never messed around with the
Windows code simply because they did not have a Visual Studio license.
Personally, I am in MSDN so I have access to all of the tools.
Mark
Jani Averbach <jaa@jaa.iki.fi> wrote on 04/28/2004 12:35:40 PM:
> On 2004-04-28 13:32+0100, Martin Tomes wrote:
> >
> > Sorry, this really is the last version of this file.
>
> First of, thank you for doing this, and secondly, do you like to mention
> following information in your document?
>
> http://msdn.microsoft.com/visualc/vctoolkit2003/
>
> ---8<---
>
> Visual C++ Toolkit 2003 Q&A
>
> What is the Visual C++ Toolkit 2003?
>
> The Visual C++ Toolkit is a free edition of Microsoft.s
> professional Visual C++ optimizing compiler and standard libraries
> . the same optimizing compiler and standard libraries that ship in
> Visual Studio .NET 2003 Professional!
>
> Are there any restrictions on how I use the Visual C++ Toolkit?
>
> In general, no. You may use the Toolkit to build C++ -based
> applications, and you may redistribute those applications. Please
> read the End User License Agreement (EULA), included with the
> Toolkit, for complete details.
>
> ---8<---
>
> However, I haven't tried your instructions with VCToolKit2003, so I
> don't know if they work or not.
>
>
> > + * Visual Studio 6 and service pack. It can be built with
> Visual Studio
> > + 7 but these instructions assumes VS6.
> > + * A recent Windows SDK, the one provided with Visual Studio 6
is
> > + too old. You only need the 'Core SDK'. You can get it from
MSDN
> > + if you have it or from
> > + http://www.microsoft.com/msdownload/platformsdk/sdkupdate/ if
you
> > + don't.
>
> ...
>
> Br, Jani
>
> --
> Jani Averbach
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
Received on Wed Apr 28 18:49:56 2004