Mark Phippard wrote:
>I am testing building the latest trunk on Win32. I am using the
>instructions found in the file INSTALL, and am using the batch file
>included in ..\build\win32 to run the build.
>
>Problem #1: zlib
>
>There is a zlib version 1.2.1 that has been available for quite a while.
>It is packaged quite different from 1.1.4 and the instructions, as is,
>will not work with 1.2.1. I think the instructions should either be
>updated to use 1.2.1, or should be modified to acknowledge that 1.2.1
>exists but that you should still use 1.1.4.
>
>I was able to use 1.2.1 by copying the file SVN\zlib\lib\zdll.lib
>
That's the wrong library. You should be using the static build, or
building your own.
> to
>SVN\zlib\zlibstat.lib (note the rename). And also by copying the header
>files in SVN\zlib\include to SVN\zlib.
>
>
Not if you use the zlib source distro instead of the prebuilt zlib.dll.
>It also appears that this causes zlib to be dynamically linked to
>zlib1.dll so that file has to be copied to the Subversion bin folder with
>the other executables prior to running the tests.
>
>
Again, not if you use the static library.
Anyway, this is not a Subversion issue, it's a Neon issue.
>Problem #2: intl.dll (libintl)
>
>This appears to be linked with msvcr70.dll so none of the Subversion
>executables, including the Apache modules, will run unless you have this
>DLL on your system and in the PATH.
>
>
And where did you get that intl.dll?
>I am not sure where I got this DLL, but perhaps I downloaded too new a
>version? If that is the case the docs should steer you away from that. I
>believe I got this DLL from one of the following:
>
>gettext-runtime-0.13.bin.woe32.zip
>gettext-tools-0.13.bin.woe32.zip
>libiconv-1.9.1.bin.woe32.zip
>
>
Use the libintl from the downloads area on subversion.tigris.org.
>Manually correcting these two issues appears to gets me past the problems
>and allows everything to build and test.
>
>
"Manually correcting..." duh. There are a zillion different ways to
build on Windows. Obviously the INSTALL instructions describe only one.
It's also a bit of a pain that Unixy packages all behave differently on
Windows. So you need to use a bit of imagination, which I see you have.
If we changed the build instructions every time someone found a
different way to build, we'd never get anything done. I regularly build
with static zlib 1.2.1, for example, but I see no reason to require that
version -- 1.1.4 is quite good enough.
>PS - Personally, I see little benefit from using DLL's on Windows. I
>think it is only going to lead to problems and Subversion would be better
>off if it stuck with statically linking as much as it can.
>
>
Indeed? Why is that? Or rather, why would shared libs be useful
elsewhere, but not on Windows?
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 14 19:47:58 2004