Brandon Ehle wrote:
>>
>>
>> I think that's fine... Oh, one possible nit: APR uses LibR and LibD as
>> the output directories for the static libraries; it uses Release and
>> Debug for the dynamic ones. I suggest we follow the same scheme, if only
>> because it makes a certain amount of sense.
>>
>>
> The reason for the top level directory at all is because when your
> generating shared libraries, the shared libraries and exes must be in
> the same path to run. Putting libs in LibR and apps in AppR or ExeR
> will not achieve this object. We could slap everything in the LibR
> and LibD dirs (exes, libs, & dlls), but that isn't as clear to long
> time MSVC users.
I didn't say anything about AppR or ExeR, did I? :-)
What I'm saying is that all statically linked things and static libs
should go into Lib[RD], while dynamically linked things and DLLs should
go into Release and Debug.
>> I have one interesting question, though: How do you generate the project
>> file for mod_dav_svn.so? If you're building static libraries, then that
>> dsp will have to rebuild mod_dav_svn's dependencies so that they link
>> with the APR DLLs, not static APR, because that's what Apache uses.
>> Notice what I did in the current handmade mod_dav_svn.dsp.
>>
>>
>>
> Haven't touched mod_dav_svn yet. This should be easy though, as I
> believe apr has static and non-static projects to link against.
No, you must _not_ link mod_dav_svn with static APR, because it won't
work. It must use the same DLLs that Apache uses. That's why the current
mod_dav_svn.dsp rebuilds the lins it depends on to link with the APR
DLL, too.
--
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 Dec 3 23:31:27 2002