Justin Erenkrantz wrote:
> On 1/1/07, D.J. Heap <djheap@gmail.com> wrote:
>> It's not the tests that can't find the dll's, though...it is Apache
>> which is a service. Service working directories all default to
>> %WINDIR%\System32, I believe, unless they change it themselves and it
>> doesn't seem likely that Apache would change it to that directory
>> unless there is some config option to do it.
>
> Copying it to Apache's bin\ directory should work though.
>
> I thought that this whole mess is sort of why we've avoided DLLs in
> the past
"We" have? First I've heard of it.
> - it's moderately okay to do that for us, but it's just a
> PITA for people who extend Subversion on Windows. For example, this
> might also wreck TortoiseSVN in similar ways. -- justin
Well here's a paradox -- on the one hand, we've had people clamouring
for DLLs on Windows so that they'd have an easier time of extending SVN;
now you're saying that makes it /harder/ to extend SVN.
Well, nonsense.
* We still have the static libs, which people can continue using if
they want to.
* TortoiseSVN does its own build, so they can either build their own
DLLs (as side-by-side assemblies, which are quite safe), or link
statically.
* We could even link mod_dav_svn statically -- although Subversion's
installer by default points Apache at the mod_dav_svn.so in
Subversion's bin/ directory where all the DLLs will be.
As for the tests -- the buildbots should stop copying the Apache modules
to the Apache install; instead; win-tests.py should copy all the DLLs
and httpd .so's to the top of the test tree, and construct an httpd.conf
that points at the modules there.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 2 10:17:15 2007