I think it's best to check for both... something like this would be ideal
if pkg_config('libxml-2.0')
elsif find_executable('xml2-config')
$CFLAGS << " #{`xml2-config --cflags`.strip}"
$LIBS << " #{`xml2-config --libs`.strip}"
elsif !have_library('xml2') or !have_header('libxml/parser.h')
fa
find_executable
2008/12/12 Charlie Savage
>
>
> David Helder wrote:
>
>> It should just use the xml2-config that's in the path and the output just
>> requires a chop:
>> > xml2-config --cflags
>> -I/opt/local/include/libxml2
>> > xml2-config --libs
>> -L/opt/local/lib -lxml2 -lz -lpthread -lic
Hi Charlie,
I guess what I'm wondering is how can the data from ruby be fed
into libxml-ruby SaxParser - when I only see 2 methods for passing
data, parser.string= and parser.filename= . I must be missing
understanding.
Thanks,
Todd
2008/7/10 Charlie Savage <[EMAIL PROTECTED]>:
> Hi Todd,
>
>
I'm wondering if there are any plans to support reading from a socket
to send data through the SaxParser. If I'm not mistaken it currently
has a .string= and .filename = method.
Thanks,
Todd
___
libxml-devel mailing list
libxml-devel@rubyforge.org
http
I believe the options to extconf.rb. Expect a directory not an exact
file... Hope this helps
On 1/12/08, Nick Black <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm trying to build libxml-ruby on Fedora Core 6, but get the following
> errors:
>
> bash-3.1# ruby extconf.rb --with-zlib-dir=/usr/lib64/
On 1/10/08, Marc Munro <[EMAIL PROTECTED]> wrote:
> This is with libxml and libxsl built from SVN 3 days ago
You might try running with valgrind.
>
> If I run with gdb, my program runs normally.
>
> Any suggestions on how I can further track this down?
>
> __
> Marc
>
>
> *** glibc detected *** r
It doesn't look like it's supported. It could be we'd have to use
xmlParseChunk. It shouldn't be too hard the tricky part would be how to
expose that feature in a easy to use ruby API...
On Dec 7, 2007 4:30 AM, Jochen Topf <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I have some rather large XML files