Re: TortoiseSVN 1.6.2 build with MIT Kerberos

Stefan Küng wrote:
>
> But your patch doesn't set any defines or macros for neon?
> It only sets the include paths and links to the lib, but I don't think
> that's enough for neon to really use it.
>

You're right, my mistake. I've added the macros into neon sources
(config.hw.in), so I modified also neon, but these modifications could be
moved to ext/build/neon.build (content of config.hw.in is anyway read into a
property). For now, I attach here the patch for ext/neon:
http://www.nabble.com/file/p23568615/neon.patch neon.patch
I will later correct it on my webpage. Probably I will try to move the
modifications into TortoiseSVN sources, into ext/build/neon.build, as
mentioned.

Stefan Küng wrote:
>
> I don't quite get what you did with your build. On your web page, you
> mention that the saslGSSAPI.dll is needed, but SASL is used with the
> svn:// protocol and neon is used with the http(s):// protocol.
> I'm confused...
>
That's what I tried to explain on my webpage, maybe not in the best way.
I've tried to make the distribution as much GSSAPI aware as possible. So
I've build (externally, not within the build of TortoiseSVN) saslGSSAPI.dll
against MIT Kerberos and I just modified the installer project of
TortoiseSVN to include it. This enables GSSAPI auth over svn://, no other
modifications should be necessary (according to some discussion), just drop
it on PATH and that's it. Second thing is Neon, for http, which is being
built differently in my build (hopefully it's clearer now with the second
patch included here). So technically, saslGSSAPI.dll is not needed if you
want to do Kerberos auth over http. And vice versa with Neon modifications
and svn://.

Stefan Küng wrote:
>
> Also, I've checked out the source from
> svn://anonsvn.mit.edu/krb5/tags/kfw-3_2_2-final - but I haven't found
> the build instructions yet...
>

I downloaded just the sdk, did not try to build kerberos from sources on my
own, sorry. But if you are able to build kerberos dlls within the build
environment of TortoiseSVN and include them in the release, that would be
great.

Second thing is saslGSSAPI.dll. In order to build it, it is required to have
Kerberos (official instructions require CyberSafe kerberos, however it went
ok with MIT, eventhough I did not test it...) and also headers of SleepyCat,
which is now officially called Oracle Berkeley DB. I did not try to make
that part of the scripts in TortoiseSVN, eventhough the sources for
cyrus-sasl are already there.

-- 
View this message in context: http://www.nabble.com/TortoiseSVN-1.6.2-build-with-MIT-Kerberos-tp23560729p23568615.html
Sent from the tortoisesvn - users mailing list archive at Nabble.com.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2275615
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].