Hi,
I'm happy to help, however I found SWIG very hard to figure out.
I have had some luck using the Ruby/DL stuff though, I have made a small
wrapper that wraps the status command using the DL methods, however even
though it was easier to do than figuring out SWIG, it would be tedious
to expose all the API's that way, especially as the SWIG bindings are
still being worked on, and much further along.
I'll post the work I have done so far for interest, especially as the DL
stuff is still not well documented.
Erik Huelsmann wrote:
>On 6/2/05, Jim Morris <morris@wolfman.com> wrote:
>
>
>>Hi,
>>
>>I have been playing with the Swig/Ruby bindings on 1.2.0 and finally got
>>them to build and the tests run ok.
>>
>>I am wondering if this project is actively being maintained or has it
>>been abandoned?
>>
>>
>
>They are actively being developed, but are a recent addition to the
>project. If you can help out by providing patches, that would be
>great!
>
>
>
>>I found that there is no binding for the svn_client_status call, and
>>after a few hours of looking over the Swig code I could not figure out
>>how to implement it, as it has a call back and the Swig generated
>>wrapper for the svn_client_status api does not seem to be correct.
>>Comparing it to the perl binding for swig it looks like there was some
>>hand coding done to the swig to make it work for perl.
>>
>>Is it worth my time to try to figure out how to implement this in
>>Swig/Ruby or continue to use the command line with backticks as I am
>>currently doing?
>>
>>
>
>It's absolutely worth the time of your investment as others will be
>using the bindings too.
>
>
>bye,
>
>
>Erik.
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 3 21:16:51 2005