> >> So anyway, here's the question: Does anyone know any links
> >> pertaining to building and linking interdependent ruby
> >> extensions? Or have any tips for me?
> >
> > During the dist-bzip2 phase of the makefile, *copy* a version of
> > ruby-libxml's headers into the libxslt tree. Then inst
On Mon, 27 Feb 2006 17:34:57 -, Sean Chittenden <[EMAIL PROTECTED]>
wrote:
>> So anyway, here's the question: Does anyone know any links
>> pertaining to building and linking interdependent ruby extensions?
>> Or have any tips for me?
>
> During the dist-bzip2 phase of the makefile, *copy* a
> So anyway, here's the question: Does anyone know any links
> pertaining to building and linking interdependent ruby extensions?
> Or have any tips for me?
During the dist-bzip2 phase of the makefile, *copy* a version of
ruby-libxml's headers into the libxslt tree. Then install a version
check a
Over the past couple of days I've started looking at bringing the libxslt
bindings up to date, but am having some 'fun' with the compile/linking and
trying to have it work as a Rubygem.
Mainly the problem is that it requires the libxml-ruby headers, but we
can't guarantee that they'll be pre
Attached is a feature patch left over from when I was collecting what was
out there. IMHO we should apply this.
--
Ross Bamford - [EMAIL PROTECTED]
registerErrorHandler.patch
Description: Binary data
___
libxml-devel mailing list
libxml-devel@rubyfor
On Mon, 27 Feb 2006 12:34:42 -, Daniel Harple
<[EMAIL PROTECTED]> wrote:
> Works for me. Using gcc4.0 on Mac OS X 10.4.
>
Thanks, now committed.
--
Ross Bamford - [EMAIL PROTECTED]
___
libxml-devel mailing list
[email protected]
http://
Works for me. Using gcc4.0 on Mac OS X 10.4.
-- Daniel
___
libxml-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/libxml-devel
