On 4/1/07, Joe Swatosh <joe.swatosh@gmail.com> wrote:
[snip]
>
> Sorry my formatting is off for the patch notes. But, I'm not sure
> this is the best way to handle these issues anyway. But this works
> with VC6 and SWIG 1.3.24 and 1.3.31.
>
> [[[
> trying to get versions of SWIG later than 1.3.24 working on windows.
>
> * build.conf
> added ruby and perl fragments files to the SWIG "check-out" list.
> * build/generator/swig/checkout_swig_header.py
> dink the fragments files to so "long long" won't be used by SWIG
> * subversion/bindings/swig/include/svn_global.swg
> added typemaps for ruby and perl
> ]]]
Thanks -- I'll let the swig experts look this over and hopefully get
it applied soon.
>
> I tried out the zip this morning. I was able to run all the tests
> except the client tests with nothing but the windows directories and
> ruby on my path after I copied
>
> sqlite3.dll
> intl3_svn.dll
> libdb44.dll
>
> into the ext directory. After I put my current subversion on the
> path, I was able to run the client tests too. I'm not completely sure
> how the bindings are supposed to opperate. Should they be completely
> stand-alone, or should we assume a installation of SVN on the path? I
> think the only reason I needed to add SVN to the path to get the
> client tests working was for the tests (needs a svnserve).
I'm not exactly sure either -- I think the python bindings setup
program for Windows does include all dll's independent of any other
Subversion install. Whether that's a good idea or not, I don't really
know. It seems reasonable to me, though.
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 1 20:28:33 2007