You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
(157) |
Dec
(87) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(78) |
Feb
(246) |
Mar
(83) |
Apr
(32) |
May
(99) |
Jun
(85) |
Jul
(34) |
Aug
(24) |
Sep
(65) |
Oct
(60) |
Nov
(45) |
Dec
(90) |
2004 |
Jan
(8) |
Feb
(40) |
Mar
(12) |
Apr
(17) |
May
(56) |
Jun
(13) |
Jul
(5) |
Aug
(30) |
Sep
(51) |
Oct
(17) |
Nov
(9) |
Dec
(20) |
2005 |
Jan
(16) |
Feb
(22) |
Mar
(14) |
Apr
(6) |
May
(12) |
Jun
(41) |
Jul
(21) |
Aug
(26) |
Sep
(7) |
Oct
(42) |
Nov
(10) |
Dec
(7) |
2006 |
Jan
(6) |
Feb
(9) |
Mar
(19) |
Apr
(7) |
May
(1) |
Jun
(10) |
Jul
(5) |
Aug
|
Sep
|
Oct
(8) |
Nov
(9) |
Dec
(3) |
2007 |
Jan
(1) |
Feb
|
Mar
(7) |
Apr
(5) |
May
(10) |
Jun
(32) |
Jul
(6) |
Aug
(8) |
Sep
(10) |
Oct
(3) |
Nov
(11) |
Dec
(2) |
2008 |
Jan
(3) |
Feb
|
Mar
(11) |
Apr
|
May
(6) |
Jun
(4) |
Jul
|
Aug
(3) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
2009 |
Jan
(6) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
|
Sep
|
Oct
(1) |
Nov
(4) |
Dec
(3) |
2010 |
Jan
(3) |
Feb
(6) |
Mar
(16) |
Apr
(2) |
May
|
Jun
|
Jul
(7) |
Aug
(3) |
Sep
(4) |
Oct
(3) |
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Christophe de V. <cde...@al...> - 2004-03-12 16:11:23
|
Christophe de VIENNE a =E9crit : > I'll add the 2.5 API too, and make the indications on the front page=20 > more clear. It's done. Murray, there is still some old directories belonging to you in the=20 sourceforge project home (html.old and reference.old), and I don't have=20 permissions to delete them. Could you, if you have 5 minutes, log in and=20 do it ? Thanks. Christophe |
From: Christophe de V. <cde...@al...> - 2004-03-12 15:57:40
|
Joe Laughlin a =E9crit : > Is the reference documentation for libxml++ at sourceforge for=20 > libxml++-1.0 or libxml++-2.5? (It doesn't seem to say.) It's for libxml++-1.0 as indicated on the "Main page" reference page. I'll add the 2.5 API too, and make the indications on the front page=20 more clear. Regards, Christophe |
From: Joe L. <jo...@ta...> - 2004-03-12 11:19:54
|
Is the reference documentation for libxml++ at sourceforge for libxml++-1.0 or libxml++-2.5? (It doesn't seem to say.) Thanks, Joe Laughlin |
From: Christophe de V. <cde...@al...> - 2004-03-03 11:02:28
|
Hi Laurent, This looks interesting, I'll have a closer look on it a bit later. However the integration into libxml++ will not occur in 2.6, since we=20 froze the API on monday. We'll soon discuss the start of a new unstable branch, in which the=20 HtmlParser should probably have its place. Thanks, Christophe Laurent Hoss a =E9crit : > Hi all, > > I discovered the cool libxml++ yesterday on my quest for the best C++=20 > XML Parser (bindings, coz libxml2 seems to be the best C parser anyway=20 > ;). Libxml is not new to me though, I used it extensively in Perl=20 > thanx to the very complete XML::LibXML CPAN Module. > Now one of my main motivations is to parse HTML Files into a DOM tree=20 > where I can extract nodes with XPATH. > In perl that was easy , it has the html parser included. > Therefore after a thorough search in the API I was a bit disappointed=20 > that there was no HTML Parser support in libxml++... > but thanks to the clean API's of libxml(++) and after a little=20 > reading , I had no difficulties at all building my own subclass (based=20 > on domparser.cc) except some little quirks (like extra encoding=20 > parameter in some html parser functions) :) > > In fact libxml2 has a really tolerant html parser (I used it in perl=20 > for mirroring/parsing whole dynamic websites :D ), it even returns a=20 > good XML Document when it had parser Errors, but to get a Doc returned=20 > in such a case one has to turn off the 'wellformedness' check, which I=20 > did in my temporary htmlparser Implementation. > ( Unfort. there's always a segfault at the end of a run of my edited=20 > 'dom_xpath/main.cc' html parsing example app , when ignoring=20 > '!context_->wellFormed' ?! experimenting done in=20 > 'HtmlParser::parse_context' method ) > > I hope HTML Parsing can be included in the main distr. ( maybe better=20 > with wellFormed check on )... > To compile the whole library with my htmlparser class, I added the=20 > class in all the files (Makefile.am files, libxml++.h...) containing=20 > 'domparser'. > > Included are the c++ and include files of htmlparser class (or should=20 > I've taken diffs from the domparser.cc/h originals ?) plus my html=20 > parsing example, which shows all the //a[@href] links with their=20 > attribute contents. > > Hopefully the segfault can be easily solved with the knowledge of the=20 > lead developpers ( I don't have yet ;). > I guess its just something I'm missing, else I'll try to find the=20 > mem.leak using a debugger (or is there a better way ??) > > Thanx, > Laurent > |
From: Christophe de V. <cde...@al...> - 2004-03-02 17:38:00
|
*** libxml++ libxml++ is a C++ wrapper for the libxml XML parser library. It has SAX and DOM-like APIs, but does not attempt to conform exactly to the DOM specifications because they are not aimed at C++. Its API is much simpler than the underlying libxml C API. *** Homepage http://libxmlplusplus.sourceforge.net/ *** Notes Following the gnome bindings release schedule, here is the first beta version of future 2.6 version. The API is now frozen. *** Changes * Fixed bug #134390: "SEGFAULT in Element::get_attribute" (John Coyle) * Code cleaning. *** Download You can download libxml++ 2.5.2 from gnome servers : http://ftp.gnome.org/pub/GNOME/sources/libxml++/2.5/ Best Regards, Christophe de Vienne |
From: Laurent H. <lau...@gm...> - 2004-03-02 02:10:46
|
Hi all, I discovered the cool libxml++ yesterday on my quest for the best C++ XML Parser (bindings, coz libxml2 seems to be the best C parser anyway ;). Libxml is not new to me though, I used it extensively in Perl thanx to the very complete XML::LibXML CPAN Module. Now one of my main motivations is to parse HTML Files into a DOM tree where I can extract nodes with XPATH. In perl that was easy , it has the html parser included. Therefore after a thorough search in the API I was a bit disappointed that there was no HTML Parser support in libxml++... but thanks to the clean API's of libxml(++) and after a little reading , I had no difficulties at all building my own subclass (based on domparser.cc) except some little quirks (like extra encoding parameter in some html parser functions) :) In fact libxml2 has a really tolerant html parser (I used it in perl for mirroring/parsing whole dynamic websites :D ), it even returns a good XML Document when it had parser Errors, but to get a Doc returned in such a case one has to turn off the 'wellformedness' check, which I did in my temporary htmlparser Implementation. ( Unfort. there's always a segfault at the end of a run of my edited 'dom_xpath/main.cc' html parsing example app , when ignoring '!context_->wellFormed' ?! experimenting done in 'HtmlParser::parse_context' method ) I hope HTML Parsing can be included in the main distr. ( maybe better with wellFormed check on )... To compile the whole library with my htmlparser class, I added the class in all the files (Makefile.am files, libxml++.h...) containing 'domparser'. Included are the c++ and include files of htmlparser class (or should I've taken diffs from the domparser.cc/h originals ?) plus my html parsing example, which shows all the //a[@href] links with their attribute contents. Hopefully the segfault can be easily solved with the knowledge of the lead developpers ( I don't have yet ;). I guess its just something I'm missing, else I'll try to find the mem.leak using a debugger (or is there a better way ??) Thanx, Laurent |
From: Laurent H. <lau...@al...> - 2004-03-02 01:47:18
|
Hi all, I discovered the cool libxml++ yesterday on my quest for the best C++ XML Parser (bindings, coz libxml2 seems to be the best C parser anyway ;). Libxml is not new to me though, I used it extensively in Perl thanx to the very complete XML::LibXML CPAN Module. Now one of my main motivations is to parse HTML Files into a DOM tree where I can extract nodes with XPATH. In perl that was easy , it has the html parser included. Therefore after a thorough search in the API I was a bit disappointed that there was no HTML Parser support in libxml++... but thanks to the clean API's of libxml(++) and after a little reading , I had no difficulties at all building my own subclass (based on domparser.cc) except some little quirks (like extra encoding parameter in some html parser functions) :) In fact libxml2 has a really tolerant html parser (I used it in perl for mirroring/parsing whole dynamic websites :D ), it even returns a good XML Document when it had parser Errors, but to get a Doc returned in such a case one has to turn off the 'wellformedness' check, which I did in my temporary htmlparser Implementation. ( Unfort. there's always a segfault at the end of a run of my edited 'dom_xpath/main.cc' html parsing example app , when ignoring '!context_->wellFormed' ?! experimenting done in 'HtmlParser::parse_context' method ) I hope HTML Parsing can be included in the main distr. ( maybe better with wellFormed check on )... To compile the whole library with my htmlparser class, I added the class in all the files (Makefile.am files, libxml++.h...) containing 'domparser'. Included are the c++ and include files of htmlparser class (or should I've taken diffs from the domparser.cc/h originals ?) plus my html parsing example, which shows all the //a[@href] links with their attribute contents. Hopefully the segfault can be easily solved with the knowledge of the lead developpers ( I don't have yet ;). I guess its just something I'm missing, else I'll try to find the mem.leak using a debugger (or is there a better way ??) Thanx, Laurent |
From: Kurt M. B. <kur...@ya...> - 2004-03-01 05:24:48
|
The basic problem I'm trying to solve is to not need glib and the C++ encapsulations by just using std::string. Only OS core libraries are needed for libxml2 and libxml++-1.0.2, which I really like: $ ldd libxml++-1.0.so.1.0.2 libxml2.so.2 => /opt/xml/libxml2-2.6.6/lib/libxml2.so.2 (0x009ed000) libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00ca0000) libz.so.1 => /usr/lib/libz.so.1 (0x008d2000) libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x00632000) libm.so.6 => /lib/tls/libm.so.6 (0x00111000) libc.so.6 => /lib/tls/libc.so.6 (0x00774000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x001c1000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x004cd000) $ ldd libxml2.so.2.6.6 libpthread.so.0 => /lib/tls/libpthread.so.0 (0x003cf000) libz.so.1 => /usr/lib/libz.so.1 (0x001f4000) libm.so.6 => /lib/tls/libm.so.6 (0x00734000) libc.so.6 => /lib/tls/libc.so.6 (0x00205000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x004cd000) For my application, I do not require UTF-8. I am also using a very lean version of Linux that has no GUI. Other than the basic OS, I build all the libraries that are needed. I am also patching libxml++ in various ways so rebuilding for me is required. I offered the string typedef idea because it would not require templates and therefore require little change to the current libxml++ code base. I may be misunderstanding the function of libxml++: maybe you mean for it to be used only where the full gnome gui library is available. If so, then maybe I should think about creating an offshoot library of some sort. |
From: lrnz <mxl...@ya...> - 2004-03-01 05:15:25
|
hi all, i'm using testing one of the libxml++ example programs under /opt/tools/libxml++/libxml++-1.0.2/examples/dom_parser . i created note.xml file: -- <?xml version="1.0"?> <note xmlns="http://www.w3schools.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation='note.xsd'> <to>Tove</to> <from>Jani</from> <heading>Reminder</heading> <body>Don't forget me this weekend!</body> </note> -- and schema file note.xsd: -- <?xml version="1.0"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.w3schools.com" xmlns="http://www.w3schools.com" elementFormDefault="qualified"> <xs:element name="note"> <xs:complexType> <xs:sequence> <xs:element name="to" type="xs:string"/> <xs:element name="from" type="xs:string"/> <xs:element name="heading" type="xs:string"/> <xs:element name="body" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> -- when i run the program "./example note.xml" i get the following error message: Exception caught: Validity error: Validation failed: no DTD found ! even if i change the note.xsd so that xsi:schemaLocation="http://www.w3schools.com note.xsd" i get the same error. any idea how to proceed ? i'm running on fedora linux. btw, the example program works if i use the example.xml or if i change the note.xsd to note.dtd. appreciate your help.. Thanks ! *lrnz* __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ |
From: Kurt M. B. <kur...@ya...> - 2004-02-28 18:57:32
|
I would like to suggest the use of a typedef for the string class used in libxml++. A new file, string_type.h, could be added: ------------------------------------- // $Id: $ #ifndef __LIBXMLPP_STRING_TYPE_H #define __LIBXMLPP_STRING_TYPE_H #if defined(LIBXMLPP_STRING_TYPE_STD) #include <string> namespace xmlpp { typedef std::string string; } #elif defined(LIBXMLPP_STRING_TYPE_STDW) #include <string> namespace xmlpp { typedef std::wstring string; } #elif defined(LIBXMLPP_STRING_TYPE_GLIB) #include <glibmm/ustring.h> namespace xmlpp { typedef Glib::ustring string; } #else #error "unsupported string type" #endif #endif // __LIBXMLPP_STRING_TYPE_H ------------------------------------- The macro, LIBXMLPP_STRING_TYPE_XXX, could be set by the configuration process. So, instead of including <string> or <glibmm/ustring.h>, one would include <libxml++/string_type.h>. Inside the xmlpp namespace, the class would be just "string". To avoid problems with when: ------------------------------- using namespace std; using namespace xmlpp; string s; // which one? ------------------------------- the typedef could be changed from making a "string" in xmlpp to "xstring", "DOMString", etc.. For example, in string_type.h: ------------------------------- namespace xmlpp { typedef std::string xstring; } ------------------------------- Also, if anyone ever did want to use std::wstring, there would be issues with stream classes (which could be resolved by adding more typedefs). |
From: Gabe H. <gj...@co...> - 2004-02-27 18:46:34
|
>>Howdy. I apologize for the mailing-list-wide e-mail for the sheer reason >>of compilation problems, but I figured I might get a faster response this >>way as opposed to making a posting at >>http://mail.gnome.org/archives/xml/2004-February/thread.html#00085 ... >> >>I downloaded libxml++, and as the instructions in the README.win32 file >>say, I also downloaded libxml and iconv and installed them at the >>appropriate levels. However, in VC6, I get compilation errors whenever I >>try to build any of the sample VC6 projects. It seems as though VC6 >>can't find the file glibmm/ustring.h : >> >>fatal error C1083: Cannot open include file: 'glibmm/ustring.h': No such >>file or directory > > >This file is part of the c++ binding of GLib, glibmm. You can download it >here : http://sourceforge.net/project/showfiles.php?group_id=1161 > >Please tell me if you successfully use libxml++ 2.5 with msvc. > >Thanks, > >Christophe Christophe: The only version of glibmm on that sourceforge page is "unstable". Should I download that, or should I download gtkmm 2.2? Merci, Gabe |
From: Kurt M. B. <kur...@ya...> - 2004-02-27 17:19:46
|
I have an example of the changes I am thinking about below. They amount to adding a few inline methods to some of the classes. Here are some changes to element.h: <kurt@dirac>$ cvs diff element.h Index: element.h =================================================================== RCS file: /cvsroot/libxmlplusplus/libxml++/libxml++/nodes/element.h,v retrieving revision 1.16 diff -r1.16 element.h 103a104,127 > std::string getAttributeNS(const std::string& namespaceURI, > const std::string& localName) const { > Attribute* a(get_attribute(localName, namespaceURI)); > return a ? a->get_value() : ""; > } > std::string getAttribute(const std::string& name) const { > return getAttributeNS(std::string(), name); > } > void setAttributeNS(const std::string& namespaceURI, > const std::string& localName, > const std::string& value) { > set_attribute(localName, value, namespaceURI); > } > void setAttribute(const std::string& name, const std::string& value) { > setAttributeNS(std::string(), name, value); > } > bool hasAttributeNS(const std::string& namespaceURI, > const std::string& localName) const { > return get_attribute(localName, namespaceURI) != 0; > } > bool hasAttribute(const std::string& name) { > return hasAttributeNS(std::string(), name); > } > On Thu, 2004-02-26 at 22:49, Kurt M. Brown wrote: > I often use w3c DOM interface implementations in several languages > (e.g., C++, javascript, perl, and php) all in the same day. So > commonality in method names is wonderful. > > The C++ implementation I use is home-grown and I want to start using > libxml++. > > Well, I am wondering what you think of adding a few simple inline > methods to match *some* of the w3c DOM interface? > > I would be happy to supply patch files or help in any way. > |
From: Christophe de V. <cde...@al...> - 2004-02-27 09:23:18
|
Hi, Actually the current unstable API will be frozen in a few days=20 (following the gnome bindings schedule), so I don't think we'll change=20 it much. (This API is quite the same as the 1.0.x version, but use=20 glib::ustring for strings, and it has a TextReader interface.) After that we can consider changing it, and any suggestion is welcome. What methods do you have in mind ? Regards, Christophe Kurt M. Brown a =E9crit : >I often use w3c DOM interface implementations in several languages >(e.g., C++, javascript, perl, and php) all in the same day. So >commonality in method names is wonderful. > >The C++ implementation I use is home-grown and I want to start using >libxml++. > >Well, I am wondering what you think of adding a few simple inline >methods to match *some* of the w3c DOM interface? > >I would be happy to supply patch files or help in any way. > =20 > |
From: Christophe de V. <cde...@al...> - 2004-02-27 09:07:31
|
Gabe Heafitz a =E9crit : > > Howdy. I apologize for the mailing-list-wide e-mail for the sheer=20 > reason of compilation problems, but I figured I might get a faster=20 > response this way as opposed to making a posting at=20 > http://mail.gnome.org/archives/xml/2004-February/thread.html#00085 ... > > I downloaded libxml++, and as the instructions in the README.win32=20 > file say, I also downloaded libxml and iconv and installed them at the=20 > appropriate levels. However, in VC6, I get compilation errors=20 > whenever I try to build any of the sample VC6 projects. It seems as=20 > though VC6 can't find the file glibmm/ustring.h : > > fatal error C1083: Cannot open include file: 'glibmm/ustring.h': No=20 > such file or directory This file is part of the c++ binding of GLib, glibmm. You can download=20 it here : http://sourceforge.net/project/showfiles.php?group_id=3D1161 Please tell me if you successfully use libxml++ 2.5 with msvc. Thanks, Christophe |
From: Christophe de V. <cde...@al...> - 2004-02-27 08:58:59
|
Hi, I'm not (yet) a specialist of cross-compile, but it seems that the link=20 is done using your system ld instead of the arm one. You may need to=20 install the binutils for your target platform. A look at configure=20 output may help understanding what's wrong. Anyway I don't think it's a libxml++ problem. Also, you should use libxml++ 1.0.2, not 0.27. Cheers, Christophe Jim Hodapp a =E9crit : >I'm currently trying to cross compile libxml++-0.27.0 to work on my >iPaq PDA running the Familiar Linux distribution (for a project at >school). I've gone ahead and changed all of the CC, CCX, lines to point >to the specific versions of gcc and g++ for the arm architecture, but I >keep getting errors when the build process tries to link. Example >output: >=20 >make >Making all in parsers >make[1]: Entering directory >`/home/jhodapp/Projects/libxml++-0.27.0/libxml++/parsers' >make[1]: Nothing to be done for `all'. >make[1]: Leaving directory >`/home/jhodapp/Projects/libxml++-0.27.0/libxml++/parsers' >Making all in exceptions >make[1]: Entering directory >`/home/jhodapp/Projects/libxml++-0.27.0/libxml++/exceptions' >make[1]: Nothing to be done for `all'. >make[1]: Leaving directory >`/home/jhodapp/Projects/libxml++-0.27.0/libxml++/exceptions' >Making all in nodes >make[1]: Entering directory >`/home/jhodapp/Projects/libxml++-0.27.0/libxml++/nodes' >make[1]: Nothing to be done for `all'. >make[1]: Leaving directory >`/home/jhodapp/Projects/libxml++-0.27.0/libxml++/nodes' >Making all in io >make[1]: Entering directory >`/home/jhodapp/Projects/libxml++-0.27.0/libxml++/io'make[1]: Nothing to >be done for `all'. >make[1]: Leaving directory >`/home/jhodapp/Projects/libxml++-0.27.0/libxml++/io' >make[1]: Entering directory >`/home/jhodapp/Projects/libxml++-0.27.0/libxml++' >/bin/sh ../libtool --mode=3Dlink /usr/local/arm/3.3.2/arm-linux/bin/g++=20 >-g -O2 -o libxml++-0.1.la -rpath /usr/local/lib -version-info 13:0:0 >attribute.lo dtd.lo document.lo noncopyable.lo keepblanks.lo =20 >-L/usr/lib -lxml2 -lz -lpthread -lm parsers/libparsers.la >exceptions/libexceptions.la nodes/libnodes.la io/libio.la >rm -fr .libs/libxml++-0.1.la .libs/libxml++-0.1.* .libs/libxml++-0.1.* >gcc -shared attribute.lo dtd.lo document.lo noncopyable.lo >keepblanks.lo -Wl,--whole-archive parsers/.libs/libparsers.al >exceptions/.libs/libexceptions.al nodes/.libs/libnodes.al >-Wl,--no-whole-archive -Wl,--rpath >-Wl,/home/jhodapp/Projects/libxml++-0.27.0/libxml++/io/.libs -Wl,--rpath >-Wl,/usr/local/lib -L/usr/lib /usr/lib/libxml2.so -lz -lpthread -lm >io/.libs/libio.so -Wl,-soname -Wl,libxml++-0.1.so.13 -o >.libs/libxml++-0.1.so.13.0.0 > >/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/../../../../i686-pc-linux-gnu/b= in/ld: attribute.lo: Relocations in generic ELF (EM: 40) >attribute.lo: could not read symbols: File in wrong format >collect2: ld returned 1 exit status >make[1]: *** [libxml++-0.1.la] Error 1 >make[1]: Leaving directory >`/home/jhodapp/Projects/libxml++-0.27.0/libxml++' >make: *** [all-recursive] Error 1 >=20 >I can't seem to get past this stage. Anyone have any thoughts on this?=20 >This app is an absolute must for my project so any thoughts would be >greatly appreciated. >=20 >Thanks, >=20 >Jim Hodapp > =20 > |
From: Kurt M. B. <kur...@ya...> - 2004-02-27 04:00:06
|
I often use w3c DOM interface implementations in several languages (e.g., C++, javascript, perl, and php) all in the same day. So commonality in method names is wonderful. The C++ implementation I use is home-grown and I want to start using libxml++. Well, I am wondering what you think of adding a few simple inline methods to match *some* of the w3c DOM interface? I would be happy to supply patch files or help in any way. |
From: Gabe H. <gj...@co...> - 2004-02-26 20:55:34
|
Howdy. I apologize for the mailing-list-wide e-mail for the sheer reason of compilation problems, but I figured I might get a faster response this way as opposed to making a posting at http://mail.gnome.org/archives/xml/2004-February/thread.html#00085 ... I downloaded libxml++, and as the instructions in the README.win32 file say, I also downloaded libxml and iconv and installed them at the appropriate levels. However, in VC6, I get compilation errors whenever I try to build any of the sample VC6 projects. It seems as though VC6 can't find the file glibmm/ustring.h : fatal error C1083: Cannot open include file: 'glibmm/ustring.h': No such file or directory So, I did a search on Glib, and that led me to GIMP, so I tried downloading the Glib source (from http://www.gimp.org/~tml/gimp/win32/glib-src-2.2.3-20040116.zip ), but it doesn't have the ustring.h header file, either. Can someone please tell me what package I need to download in order to get the header files necessary for compiling libxml++ in VC6? libxml2 and iconv don't seem to be enough. Thanks very much for your time! - Gabe Heafitz |
From: Jim H. <jh...@iu...> - 2004-02-26 20:06:39
|
I'm currently trying to cross compile libxml++-0.27.0 to work on my iPaq PDA running the Familiar Linux distribution (for a project at school). I've gone ahead and changed all of the CC, CCX, lines to point to the specific versions of gcc and g++ for the arm architecture, but I keep getting errors when the build process tries to link. Example output: make Making all in parsers make[1]: Entering directory `/home/jhodapp/Projects/libxml++-0.27.0/libxml++/parsers' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/jhodapp/Projects/libxml++-0.27.0/libxml++/parsers' Making all in exceptions make[1]: Entering directory `/home/jhodapp/Projects/libxml++-0.27.0/libxml++/exceptions' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/jhodapp/Projects/libxml++-0.27.0/libxml++/exceptions' Making all in nodes make[1]: Entering directory `/home/jhodapp/Projects/libxml++-0.27.0/libxml++/nodes' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/jhodapp/Projects/libxml++-0.27.0/libxml++/nodes' Making all in io make[1]: Entering directory `/home/jhodapp/Projects/libxml++-0.27.0/libxml++/io'make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/jhodapp/Projects/libxml++-0.27.0/libxml++/io' make[1]: Entering directory `/home/jhodapp/Projects/libxml++-0.27.0/libxml++' /bin/sh ../libtool --mode=link /usr/local/arm/3.3.2/arm-linux/bin/g++ -g -O2 -o libxml++-0.1.la -rpath /usr/local/lib -version-info 13:0:0 attribute.lo dtd.lo document.lo noncopyable.lo keepblanks.lo -L/usr/lib -lxml2 -lz -lpthread -lm parsers/libparsers.la exceptions/libexceptions.la nodes/libnodes.la io/libio.la rm -fr .libs/libxml++-0.1.la .libs/libxml++-0.1.* .libs/libxml++-0.1.* gcc -shared attribute.lo dtd.lo document.lo noncopyable.lo keepblanks.lo -Wl,--whole-archive parsers/.libs/libparsers.al exceptions/.libs/libexceptions.al nodes/.libs/libnodes.al -Wl,--no-whole-archive -Wl,--rpath -Wl,/home/jhodapp/Projects/libxml++-0.27.0/libxml++/io/.libs -Wl,--rpath -Wl,/usr/local/lib -L/usr/lib /usr/lib/libxml2.so -lz -lpthread -lm io/.libs/libio.so -Wl,-soname -Wl,libxml++-0.1.so.13 -o .libs/libxml++-0.1.so.13.0.0 /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/../../../../i686-pc-linux-gnu/bin/ld: attribute.lo: Relocations in generic ELF (EM: 40) attribute.lo: could not read symbols: File in wrong format collect2: ld returned 1 exit status make[1]: *** [libxml++-0.1.la] Error 1 make[1]: Leaving directory `/home/jhodapp/Projects/libxml++-0.27.0/libxml++' make: *** [all-recursive] Error 1 I can't seem to get past this stage. Anyone have any thoughts on this? This app is an absolute must for my project so any thoughts would be greatly appreciated. Thanks, Jim Hodapp -- Full-time student of Electrical Engineering Purdue School of Engineering @ Indiana University Purdue University Indianapolis |
From: Niklas G. <ngr...@am...> - 2004-02-23 21:12:24
|
I will be out of the office starting 23.02.2004 and will not return until 08.03.2004. I will respond to your message when I return. |
From: Niklas G. <ngr...@am...> - 2004-02-23 18:11:27
|
I will be out of the office starting 23.02.2004 and will not return until 08.03.2004. I will respond to your message when I return. |
From: Niklas G. <ngr...@am...> - 2004-02-23 15:10:24
|
I will be out of the office starting 23.02.2004 and will not return until 08.03.2004. I will respond to your message when I return. |
From: Christophe de V. <cde...@al...> - 2004-02-23 15:01:01
|
Philippe Raoult a =E9crit : >Hello all, > >It seems that the class diagrams in the reference documentation=20 >are broken, they have no labels. I use mozilla 1.4 but i had=20 >some friends check it out too and they found the same issue. > > =20 > My graphviz installation was broken. It's fixed and updated on the=20 website... Thanks, Christophe |
From: Philippe R. <ph...@gc...> - 2004-02-23 13:03:49
|
Hello all, It seems that the class diagrams in the reference documentation are broken, they have no labels. I use mozilla 1.4 but i had some friends check it out too and they found the same issue. ps: please cc to me im not on the list... Philippe |
From: Christophe de V. <cde...@al...> - 2004-02-18 17:27:21
|
*** libxml++ libxml++ is a C++ wrapper for the libxml XML parser library. It has SAX and DOM-like APIs, but does not attempt to conform exactly to the DOM specifications because they are not aimed at C++. Its API is much simpler than the underlying libxml C API. *** Homepage http://libxmlplusplus.sourceforge.net/ *** Notes This is a bugfix release. *** Changes * Fixed issue #132014: "Memory leak in throwing exception". * Fixed issue #134390: "SEGFAULT in Element::get_attribute" (John Coyle). * Made libxml++ build using the Sun, HP, SGI, and AIX C++ compilers (Albert Chin). *** Download You can download libxml++ 1.0.2 from gnome servers : http://ftp.gnome.org/pub/GNOME/sources/libxml++/1.0/ ftp://ftp.gnome.org/pub/GNOME/sources/libxml++/1.0/ Best Regards, Christophe de Vienne |
From: Christophe de V. <cde...@al...> - 2004-02-16 17:10:59
|
Hi all, The API freeze, following gnome bindings schedule, has been fixed to the 1st of March (instead of today). This will give us time to test the 2.5 API more seriously. Please give us some feedback, especially on the new TextReader interface. Best regards, Christophe |