Jostein Chr. Andersen wrote:
>On Monday 05 April 2004 17.46, Branko Cibej wrote:
>
>
>>Quoting "Jostein Chr. Andersen" <jostein@josander.net>:
>>
>>
>[...]
>
>
>>>My questions is:
>>>
>>>Where shall the installer look for the APR DLL(s)?
>>>Is it build\win32\{Debug|Release} from the WC?
>>>
>>>
>>No, they'll never be there. The binary package will include them in
>>the bin/ directory, _but_ if you're installing with Apache, SVN should
>>just use Apache's DLLs and iconv .so files.
>>
>>
>
>What if you or someone else who builds the binaries are rolling out the
>installer directly from the newly builded binaries (the installer system
>are made for this), where will the installer look for the APR DLLs?
>
>
I'd suggest not to do it this way. We need (or rather, I have to write)
a script that creates the canonical Windows binary tree anyway. By the
way, there's a file called gen-make.opts that's generated by gen-make.py
which contains all the (implicitly generated) options passed in, and
incidentally points BDB, httpd, apr-*, etc. You can find the locations
of the APR DLLs there.
>So, is it right that the modules are using Apache's DLLs and iconv .so
>files if the modules is instlalled and Subversion itself are using
>Subversion ones anyway?
>
>
I think it would be a big mistake to try to use two different versions
of the DLLs on the same system. Of course, that's assuming the installed
Apache is compatible with the installed Subversion.
Actually, I think bot APR and SVN DLLs (when there _are_ SVN DLLs) have
to include the major and minor versions in the name...
--
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 Tue Apr 6 02:40:35 2004