You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by David James <ja...@gmail.com> on 2005/06/03 20:58:04 UTC
[PATCH] Document installation and testing process for Ruby bindings
This patch documents the installation and testing process for the Ruby
bindings. If one of the developers who are familiar with the Ruby
bindings could take a look at this, it would be much appreciated!
subversion/bindings/swig/INSTALL
(Step 3): Added section describing the Ruby installation process
to Step 3: Install Specific Language Bindings
(Testing and using SWIG bindings): Added section for ruby
bindings
Cheers,
David
P.S. I've documented that the "check-swig-rb" target checks the Ruby
bindings against the installed bindings, not against the bindings
you've just built in the build dir. This is probably a bug similar to
Issue #2040. Should I file an issue for this?
--
http://www.cs.toronto.edu/~james
Re: [PATCH] Document installation and testing process for Ruby
bindings (v2)
Posted by Kouhei Sutou <ko...@cozmixng.org>.
Hi,
In <df...@mail.gmail.com>
"Re: [PATCH] Document installation and testing process for Ruby bindings (v2)" on Sun, 5 Jun 2005 10:49:13 -0400,
David James <ja...@gmail.com> wrote:
> I have amended my documentation patch to take out the part where I
> mentioned that check-swig-rb tests "the bindings against your
> currently-installed Subversion libraries," since we now know that
> check-swig-rb tests the bindings against the libraries in your build
> dir. The amended patch and the log message are included below.
Thanks.
I applied the patch. (r14985)
--
kou
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Document installation and testing process for Ruby bindings (v2)
Posted by David James <ja...@gmail.com>.
> > P.S. I've documented that the "check-swig-rb" target checks the Ruby
> > bindings against the installed bindings, not against the bindings
> > you've just built in the build dir. This is probably a bug similar to
> > Issue #2040. Should I file an issue for this?
> I couldn't reproduce the problem. [...]
Thank you for your help. I have looked into the problem closely and it
turns out there is no problem here -- I was just confused by the test
failures.
I have amended my documentation patch to take out the part where I
mentioned that check-swig-rb tests "the bindings against your
currently-installed Subversion libraries," since we now know that
check-swig-rb tests the bindings against the libraries in your build
dir. The amended patch and the log message are included below.
--
This patch documents the installation and testing process for the Ruby
bindings.
subversion/bindings/swig/INSTALL
(Step 3): Added section describing the Ruby installation process
to Step 3: Install Specific Language Bindings
(Testing and using SWIG bindings): Added section for ruby
bindings
Cheers,
David
--
http://www.cs.toronto.edu/~james
Re: [PATCH] Document installation and testing process for Ruby
bindings
Posted by Kouhei Sutou <ko...@cozmixng.org>.
Hi,
In <df...@mail.gmail.com>
"[PATCH] Document installation and testing process for Ruby bindings" on Fri, 3 Jun 2005 16:58:04 -0400,
David James <ja...@gmail.com> wrote:
> This patch documents the installation and testing process for the Ruby
> bindings. If one of the developers who are familiar with the Ruby
> bindings could take a look at this, it would be much appreciated!
Great!
> P.S. I've documented that the "check-swig-rb" target checks the Ruby
> bindings against the installed bindings, not against the bindings
> you've just built in the build dir. This is probably a bug similar to
> Issue #2040. Should I file an issue for this?
I couldn't reproduce the problem. I tried the following
sequence on my FreeBSD box.
(1) % make swig-rb
(2) % make check-swig-rb # This worked. (but some tests failed)
(3) % make install-swig-rb
(4) add 'p :installed' to the head of installed svn/core.rb.
(5) add 'p :built' to the head of svn/core.rb in built directory.
(6) 'make check-swig-rb' shows ':built'.
I wonder that you got the problem. Because
subversion/bindings/swig/ruby/test/run-test.rb setup
$LOAD_PATH and so on to use built libraries.
Could you show me the way how to reproduce the problem and
judge the problem is occurred or not?
Thanks,
--
kou
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org