On Fri, Sep 24, 2010 at 20:00, Jean-Yves Avenard <jyavenard_at_gmail.com> wrote:
> On 25 September 2010 06:09, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
>> Well, you did the easy part.
>> I now spent the whole evening trying to build kerberos myself. I can't
>> get it to work. And I don't plan on fixing their build system: seems
>> they can't handle anything if it's installed in 'c:\program files'
>> because that path has a space in it.
> Why are you trying to build Kerberos yourself?
> The MIT SDK provides the binaries directly.
> You don't even need to install their exe
>> So if you really need TSVN to build with GSSAPI support, you have to
>> provide a build script so that our build can also build the kerberos source.
> can't we use the provided MIT SDK? TSVN already has dependencied on a
> few binaries to built, it's just another one.
Stefan already addressed this:
"I guess the linking error is because the libs are not built for x64.
Also I never use precompiled libs in TSVN. I always compile the libs
myself and create a build script. Only that way I can guarantee that the
libs don't use an incompatible c-runtime and are always compiled for
both win32 and x64."
If there are no x64 MIT Kerberos libs, then the precompiled libs are
useless for TSVN - they can't be integrated into the 64-bit version.
If the MIT libs need a different C-runtime than TSVN, that's yet
another layer of headaches & support trouble.
You're free to roll your own version of TSVN, but Stefan has a
specific way he builds the packages he ships (and supports), and this
far it's not working with MIT Kerberos.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-09-25 02:16:25 CEST