To go with the new libxml-ruby release, I've pushed up a libxslt-ruby release.

It includes two big changes.

* Windows support (both lots of memory fixes and binaries)

* New libxslt.rb ruby wrapper, so programs can simply say:

require 'libxslt'

* For all other platforms, I updated extconf.rb to tell gcc that libxslt-ruby depends on libxml-ruby being present. To do this trick, I made a big assumption - that libxml-ruby is installed as a gem. I did this because I couldn't figure out any other way to reliably determine where the libxml-ruby header files were on disk. What do people think o of this?


Last, the project name on rubyforge is libxsl which is incorrect. It should be libxslt since its wrapping the libxslt library (http://xmlsoft.org/XSLT/). Is it possible to change names?

Charlie

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel

Reply via email to