On 12/16/05, Stefan Küng <tortoisesvn@gmail.com> wrote:
[snip]
>
> What still bothers me (no big deal, but annoying) are the hundreds of
> warnings VS.NET2005 produces while building Subversion. Attached is a
> patch which will simply silence those warnings by setting the
> corresponding preprocessor define in the project files.
The Subversion project files already get these defines through the
generator, but the apr ones will be nice, thanks! Of course, we
really shouldn't be embedding apr project files at all...
>
> Also attached is a modified file to build the zlib. I copy that file to
> zlib\contrib\masmx86 (and zlib/, because the nmake script doesn't
> overwrite an old version of that file if it's already there). Maybe you
> want to include that in your own build process too?
> It won't interfere with VS.NET2003.
Yes, I've got a tweaked one too, thanks...hopefully zlib will release
a new version soon.
>
> The third file attached is a patched makefile for the apr-iconv modules.
> It silences the warnings generated for each linked *.so module and also
> embeds the manifest file needed if built with the CRT80 (which comes
> with VS.NET2005). It's not really necessary, but I'd rather have the
> manifest inside the modules than to ship a separate *.manifest file for
> each *.so module.
> This should of course only be used if compiled with VS.NET2005 -
> VS.NET2003 doesn't have the mt tool required for this.
Why is the manifest file useful at all (embedded or not)?
>
> I also had to patch neon.mak (enclose the paths to the tools in quotes),
> otherwise VS.NET2005 doesn't find them if the path has spaces in them
> (which is usually the case, because it installs to "program
> files\Microsoft Visual Studio 8").
You should send that to the neon folks (www.webdav.org/neon).
Thanks!
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 16 20:36:45 2005