D.J. Heap wrote:
> On 12/16/05, Stefan Küng <firstname.lastname@example.org> wrote:
>> 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...
Seems I missed some more changes :)
>> 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.
Considering how long it took to get a new release the last time with the
security fix (about two months), I really doubt that this will happen 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)?
If the manifest is missing, the CRT isn't loaded (try the dependency
viewer on those files, you'll get a "MSVCRT80.dll not found" error). So
basically without the manifest, the dll's won't load at all, and
therefore won't work at all.
You might not have noticed this with the iconv modules, because they're
only needed if you have non-ascii paths/urls to deal with...
>> 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).
Good idea :)
Another thing what would really, really help me a lot:
a dummy project in the Subversion solution file which only builds the
Subversion libs, *without* apr,apr-iconv,apr-util. Because building
apr-iconv takes really a very long time, and I have to build Subversion
twice (once with and once without file/DAV/svn support), and if I do a
rebuild on __ALL__, the apr libs get rebuilt too twice.
Since I don't know python at all, I hope someone else can hack the build
generator to produce such a project?
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Dec 16 20:48:35 2005