From anto.trande at gmail.com Sat Oct 10 05:33:04 2015 From: anto.trande at gmail.com (Antonio Trande) Date: Sat Oct 10 05:33:19 2015 Subject: [xsd-users] tree/default/general test failed Message-ID: <5618DB50.7050804@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all, a test from latest XSD-4.0.0 fails with this error: xsd /builddir/build/BUILD/xsd-4.0.0+dep/xsd/tests/cxx/tree/default/general/test.xsd /bin/sh: line 1: 2413 Segmentation fault (core dumped) /builddir/build/BUILD/xsd-4.0.0+dep/xsd/xsd/xsd cxx-tree - --generate-inline --generate-ostream --generate-serialization - --generate-default-ctor --generate-from-base-ctor --std c++98 - --output-dir /builddir/build/BUILD/xsd-4.0.0+dep/xsd/tests/cxx/tree/default/general/ /builddir/build/BUILD/xsd-4.0.0+dep/xsd/tests/cxx/tree/default/general/test.xsd make: *** [/builddir/build/BUILD/xsd-4.0.0+dep/xsd/tests/cxx/tree/default/general/test.hxx] Error 139 Please, does anyone know why happens? Full log of compilation: http://fpaste.org/276911/ Thanks. - -- Antonio Trande mailto: sagitter 'at' fedoraproject 'dot' org http://fedoraos.wordpress.com/ https://fedoraproject.org/wiki/User:Sagitter GPG Key: 0x565E653C Check on https://keys.fedoraproject.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWGNtMAAoJEF5tK7VWXmU8nzIH/2DShEFJVdNVp+nrtuoMcnBH RyDN/3/NsAWiSododo1ASHSvU0mJ2snQoaX2EpuL8P6yGr80PQWfqvWubNG2GROj owM432plnTZcGg6hiL0TNs07FC6HdgHgt7eDdD3+0tpQH6qAnMmN9Anw89q6y78O CqQCbYk7tzvbza8erng4hxj0P+r3tvRgu2ygVcEHTSfIYidGGES2Fv7J9Xqt64Bv YXQW7eOFK01YCpizQnpKU5AP5AWQXfCIcZ7aaRKbO6ab/B9xYfn1FHX68rbZVzc4 msalC3ZLLxFC2t32D57rJJBszWYBODAa0cHdaeZ5xmy9WkEWXtiDWqL+ZQ/DsnQ= =qxSo -----END PGP SIGNATURE----- From boris at codesynthesis.com Sat Oct 10 05:42:57 2015 From: boris at codesynthesis.com (Boris Kolpackov) Date: Sat Oct 10 05:43:07 2015 Subject: [xsd-users] tree/default/general test failed In-Reply-To: <5618DB50.7050804@gmail.com> References: <5618DB50.7050804@gmail.com> Message-ID: Hi Antonio, Antonio Trande writes: > Please, does anyone know why happens? Any chance of getting the stack trace from the core? Also, knowing a bit more about the environment would help, especially, the GCC version that is being used. Boris From anto.trande at gmail.com Sat Oct 10 06:12:44 2015 From: anto.trande at gmail.com (Antonio Trande) Date: Sat Oct 10 06:12:54 2015 Subject: [xsd-users] tree/default/general test failed In-Reply-To: References: <5618DB50.7050804@gmail.com> Message-ID: <5618E49C.4030202@gmail.com> On 10/10/2015 11:42 AM, Boris Kolpackov wrote: > Hi Antonio, > > Antonio Trande writes: > > > Please, does anyone know why happens? > > Any chance of getting the stack trace from the core? Unfortunately, i can't in this moment. >Also, knowing a bit more about the environment would help, especially, the GCC version that is being used. XSD is rebuilt locally in a CentOS6 chroot build-system (on a Fedora 22) with GCC-4.4.7 (as you can see from log). The tests do not fail in Fedora with GCC-5.1.1 [1] and in a CentOS7 chroot with GCC-4.8.3 [2]. [1]https://kojipkgs.fedoraproject.org//work/tasks/7081/11397081/build.log [2]https://kojipkgs.fedoraproject.org//work/tasks/7187/11397187/build.log > > Boris > -- Antonio Trande mailto: sagitter 'at' fedoraproject 'dot' org http://fedoraos.wordpress.com/ https://fedoraproject.org/wiki/User:Sagitter GPG Key: 0x565E653C Check on https://keys.fedoraproject.org/ From anto.trande at gmail.com Sun Oct 11 10:53:25 2015 From: anto.trande at gmail.com (Antonio Trande) Date: Sun Oct 11 10:53:32 2015 Subject: [xsd-users] tree/default/general test failed In-Reply-To: <5618E49C.4030202@gmail.com> References: <5618DB50.7050804@gmail.com> <5618E49C.4030202@gmail.com> Message-ID: I tried to debug this error (note that XSD has been patched and renamed to 'xsdcxx' because of conflicts with other 'xsd' executables): > gdb xsdcxx > (gdb) run cxx-tree --generate-inline --generate-ostream --generate-serialization --generate-default-ctor --generate-from-base-ctor --std c++98 --output-dir home/Anto.Trande/Downloads /home/Anto.Trande/Downloads/xsd-4.0.0-7.el6.src/xsd-4.0.0+dep/xsd/tests/cxx/tree/default/general/test.xsd Starting program: /usr/bin/xsdcxx cxx-tree --generate-inline --generate-ostream --generate-serialization --generate-default-ctor --generate-from-base-ctor --std c++98 --output-dir home/Anto.Trande/Downloads /home/Anto.Trande/Downloads/xsd-4.0.0-7.el6.src/xsd-4.0.0+dep/xsd/tests/cxx/tree/default/general/test.xsd warning: the debug information found in "/usr/lib/debug//usr/lib64/libxerces-c-3.0.so.debug" does not match "/usr/lib64/libxerces-c-3.0.so" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/usr/lib64/libxerces-c-3.0.so.debug" does not match "/usr/lib64/libxerces-c-3.0.so" (CRC mismatch). [Thread debugging using libthread_db enabled] warning: "/usr/lib/debug/usr/lib64/libicudata.so.42.1.debug": separate debug info file has no debug info Program received signal SIGSEGV, Segmentation fault. 0x00007ffff79c54b5 in xercesc_3_0::ElemStack::mapPrefixToURI(unsigned short const*, xercesc_3_0::ElemStack::MapModes, bool&) const () from /usr/lib64/libxerces-c-3.0.so Note: xerces-c version 3.0.1 (CentOS-6): test failed xerces-c version 3.1.1 (Fedora and CentOS-7): test works On Sat, Oct 10, 2015 at 12:12 PM, Antonio Trande wrote: > On 10/10/2015 11:42 AM, Boris Kolpackov wrote: > > Hi Antonio, > > > > Antonio Trande writes: > > > > > Please, does anyone know why happens? > > > > Any chance of getting the stack trace from the core? > Unfortunately, i can't in this moment. > > >Also, knowing a bit more about the environment would help, especially, > the GCC version that is being used. > > XSD is rebuilt locally in a CentOS6 chroot build-system (on a Fedora 22) > with GCC-4.4.7 (as you can see from log). > > The tests do not fail in Fedora with GCC-5.1.1 [1] and in a CentOS7 chroot > with GCC-4.8.3 [2]. > > [1]https://kojipkgs.fedoraproject.org//work/tasks/7081/11397081/build.log > [2]https://kojipkgs.fedoraproject.org//work/tasks/7187/11397187/build.log > > > > Boris > > > > -- > Antonio Trande > > mailto: sagitter 'at' fedoraproject 'dot' org > http://fedoraos.wordpress.com/ > https://fedoraproject.org/wiki/User:Sagitter > GPG Key: 0x565E653C > Check on https://keys.fedoraproject.org/ > -- *Antonio Trande"Fedora Ambassador"* *"Fedora italian translation group"* *"Blogger"**mail*: mailto:sagitter@fedoraproject.org *Homepage*: http://www.fedora-os.org *Sip Address* : sip:sagitter AT ekiga.net *Jabber * :sagitter AT jabber.org *GPG Key: **D400D6C4* From anto.trande at gmail.com Sun Oct 11 12:30:46 2015 From: anto.trande at gmail.com (Antonio Trande) Date: Sun Oct 11 12:30:53 2015 Subject: [xsd-users] tree/default/general test failed In-Reply-To: References: <5618DB50.7050804@gmail.com> <5618E49C.4030202@gmail.com> Message-ID: Sorry, xerces-c debuginfo was not installed correctly; this is the new log on CentOS-6: > (gdb) run cxx-tree --generate-inline --generate-ostream --generate-serialization --generate-default-ctor --generate-from-base-ctor --std c++98 --output-dir home/Anto.Trande/Downloads /home/Anto.Trande/Downloads/xsd-4.0.0-7.el6.src/xsd-4.0.0+dep/xsd/tests/cxx/tree/default/general/test.xsd Starting program: /usr/bin/xsdcxx cxx-tree --generate-inline --generate-ostream --generate-serialization --generate-default-ctor --generate-from-base-ctor --std c++98 --output-dir home/Anto.Trande/Downloads /home/Anto.Trande/Downloads/xsd-4.0.0-7.el6.src/xsd-4.0.0+dep/xsd/tests/cxx/tree/default/general/test.xsd [Thread debugging using libthread_db enabled] warning: "/usr/lib/debug/usr/lib64/libicudata.so.42.1.debug": separate debug info file has no debug info Program received signal SIGSEGV, Segmentation fault. getId (this=0x0, prefixToMap=0xadf7f0, mode=, unknown=@0x7fffffffb21f) at xercesc/util/StringPool.hpp:141 141 PoolElem* elemToFind = fHashTable->get(toFind); (gdb) run The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /usr/bin/xsdcxx cxx-tree --generate-inline --generate-ostream --generate-serialization --generate-default-ctor --generate-from-base-ctor --std c++98 --output-dir home/Anto.Trande/Downloads /home/Anto.Trande/Downloads/xsd-4.0.0-7.el6.src/xsd-4.0.0+dep/xsd/tests/cxx/tree/default/general/test.xsd [Thread debugging using libthread_db enabled] warning: "/usr/lib/debug/usr/lib64/libicudata.so.42.1.debug": separate debug info file has no debug info Program received signal SIGSEGV, Segmentation fault. getId (this=0x0, prefixToMap=0xadf7f0, mode=, unknown=@0x7fffffffb21f) at xercesc/util/StringPool.hpp:141 141 PoolElem* elemToFind = fHashTable->get(toFind); On Sun, Oct 11, 2015 at 4:53 PM, Antonio Trande wrote: > I tried to debug this error (note that XSD has been patched and renamed to > 'xsdcxx' because of conflicts with other 'xsd' executables): > > > gdb xsdcxx > > (gdb) run cxx-tree --generate-inline --generate-ostream > --generate-serialization --generate-default-ctor --generate-from-base-ctor > --std c++98 --output-dir home/Anto.Trande/Downloads > /home/Anto.Trande/Downloads/xsd-4.0.0-7.el6.src/xsd-4.0.0+dep/xsd/tests/cxx/tree/default/general/test.xsd > Starting program: /usr/bin/xsdcxx cxx-tree --generate-inline > --generate-ostream --generate-serialization --generate-default-ctor > --generate-from-base-ctor --std c++98 --output-dir > home/Anto.Trande/Downloads > /home/Anto.Trande/Downloads/xsd-4.0.0-7.el6.src/xsd-4.0.0+dep/xsd/tests/cxx/tree/default/general/test.xsd > warning: the debug information found in > "/usr/lib/debug//usr/lib64/libxerces-c-3.0.so.debug" does not match > "/usr/lib64/libxerces-c-3.0.so" (CRC mismatch). > > warning: the debug information found in > "/usr/lib/debug/usr/lib64/libxerces-c-3.0.so.debug" does not match > "/usr/lib64/libxerces-c-3.0.so" (CRC mismatch). > > [Thread debugging using libthread_db enabled] > warning: "/usr/lib/debug/usr/lib64/libicudata.so.42.1.debug": separate > debug info file has no debug info > > Program received signal SIGSEGV, Segmentation fault. > 0x00007ffff79c54b5 in xercesc_3_0::ElemStack::mapPrefixToURI(unsigned > short const*, xercesc_3_0::ElemStack::MapModes, bool&) const () > from /usr/lib64/libxerces-c-3.0.so > > Note: > xerces-c version 3.0.1 (CentOS-6): test failed > xerces-c version 3.1.1 (Fedora and CentOS-7): test works > > > > On Sat, Oct 10, 2015 at 12:12 PM, Antonio Trande > wrote: > >> On 10/10/2015 11:42 AM, Boris Kolpackov wrote: >> > Hi Antonio, >> > >> > Antonio Trande writes: >> > >> > > Please, does anyone know why happens? >> > >> > Any chance of getting the stack trace from the core? >> Unfortunately, i can't in this moment. >> >> >Also, knowing a bit more about the environment would help, especially, >> the GCC version that is being used. >> >> XSD is rebuilt locally in a CentOS6 chroot build-system (on a Fedora 22) >> with GCC-4.4.7 (as you can see from log). >> >> The tests do not fail in Fedora with GCC-5.1.1 [1] and in a CentOS7 >> chroot with GCC-4.8.3 [2]. >> >> [1]https://kojipkgs.fedoraproject.org//work/tasks/7081/11397081/build.log >> [2]https://kojipkgs.fedoraproject.org//work/tasks/7187/11397187/build.log >> > >> > Boris >> > >> >> -- >> Antonio Trande >> >> mailto: sagitter 'at' fedoraproject 'dot' org >> http://fedoraos.wordpress.com/ >> https://fedoraproject.org/wiki/User:Sagitter >> GPG Key: 0x565E653C >> Check on https://keys.fedoraproject.org/ >> > > > > -- > > *Antonio Trande"Fedora Ambassador"* > *"Fedora italian translation group"* > > > *"Blogger"**mail*: mailto:sagitter@fedoraproject.org > > *Homepage*: http://www.fedora-os.org > *Sip Address* : sip:sagitter AT ekiga.net > *Jabber * :sagitter AT jabber.org > *GPG Key: **D400D6C4* > -- *Antonio Trande"Fedora Ambassador"* *"Fedora italian translation group"* *"Blogger"**mail*: mailto:sagitter@fedoraproject.org *Homepage*: http://www.fedora-os.org *Sip Address* : sip:sagitter AT ekiga.net *Jabber * :sagitter AT jabber.org *GPG Key: **D400D6C4* From boris at codesynthesis.com Mon Oct 12 09:42:09 2015 From: boris at codesynthesis.com (Boris Kolpackov) Date: Mon Oct 12 09:42:56 2015 Subject: [xsd-users] tree/default/general test failed In-Reply-To: References: <5618DB50.7050804@gmail.com> <5618E49C.4030202@gmail.com> Message-ID: Hi Antonio, Antonio Trande writes: > xerces-c version 3.0.1 (CentOS-6): test failed > xerces-c version 3.1.1 (Fedora and CentOS-7): test works Well, that's your answer. There were a whole bunch of really nasty bugs fixed since Xerces-C++ 3.0.x. In fact, ideally, your should be using the 3.1.2 bugfix release. Boris From me at ryanlewis.net Tue Oct 13 01:08:31 2015 From: me at ryanlewis.net (Ryan Lewis) Date: Tue Oct 13 01:08:57 2015 Subject: [xsd-users] versioned xsd files Message-ID: Hi, I am wondering what the best way is to handle versioned xml files? Does XSD do this? Take as an example PMML. Also, I am curious if the maintainers of XSD (or anyone in this community) have seen a C++ PMML Parser used out there? Best, -rhl From yadykin_a at mail.ru Tue Oct 13 02:31:49 2015 From: yadykin_a at mail.ru (=?UTF-8?B?QWxleGFuZGVyIFlhZHlraW4=?=) Date: Tue Oct 13 09:21:05 2015 Subject: [xsd-users] Problem with OGC GML - anyType values Message-ID: <1444717909.741284721@f394.i.mail.ru> Dear All, I have a problem with using of Code Synthesis XSD in my project, I hope that you will not refuse to help me a little bit. I tries to create a simple XML reader\writer for RapidEye remote sensing data products ( http://blackbridge.com/rapideye/all-products/images.htm ). I checked product specification guide ( http://blackbridge.com/rapideye/upload/RE_Product_Specifications_ENG.pdf , stage 8.1) and found that the XML metadata file based on OGC GML specification. I downloaded product sample (see product_sample.tar.gz in attachment) and appropriate XSD files (see schema.tar.gz in attachment) from official site. I created C++\Tree mapping code using Code Synthesis XSD with the following command line parameters: cxx-tree --generate-serialization --generate-polymorphic --polymorphic-type-all --generate-comparison --generate-ostream --generate-doxygen --generate-any-type Generated C++ code was successfully compiled. So, the substance of my problem. RapidEye XSD expands OGC XSD according to OGC recommendations and replaces some OGC anyType fields to specific RapidEye types. For example ogc::metadataProperty can contain any type values, but it contains re::EarthObservationMetadata in our case. As a result I have a problems with interpretation of anyType values as a specific type during reading & writing XML files. I successfully solved this problem for XML reading using Code Synthesis examples & FAQ, but I can't solve the problem for XML creation. I created and filled child element "products::productMetadataSensor::EarthObservationMetaDataType". But I don't understand how to push it to parent element "gml::MetaDataPropertyType". I tried various methods but without success - program crashes during execution. You will find my small code listing in attachment (see source.tar.gz). Could you please clarify how I can generate & write XML metadata file using code which was generated by Code Synthesis XSD? Could you please be so kind as to check my method of XML reading - I suppose that it is not optimal solution. Thanks in advance.? -- Best regards, Alexander Yadykin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/x-gzip Size: 30698 bytes Desc: not available Url : http://codesynthesis.com/pipermail/xsd-users/attachments/20151013/a5fa28ac/attachment-0003.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/x-gzip Size: 3983 bytes Desc: not available Url : http://codesynthesis.com/pipermail/xsd-users/attachments/20151013/a5fa28ac/attachment-0004.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/x-gzip Size: 1769 bytes Desc: not available Url : http://codesynthesis.com/pipermail/xsd-users/attachments/20151013/a5fa28ac/attachment-0005.bin From boris at codesynthesis.com Wed Oct 14 09:38:27 2015 From: boris at codesynthesis.com (Boris Kolpackov) Date: Wed Oct 14 09:38:29 2015 Subject: [xsd-users] versioned xsd files In-Reply-To: References: Message-ID: Hi Ryan, Ryan Lewis writes: > I am wondering what the best way is to handle versioned xml files? Does XSD > do this? XML Schema itself doesn't provide any mechanisms for schema evolution. So the commonly used approach is to generate mapping code for different versions of your vocabulary into different C++ namespaces, detect which version is being parsed (e.g., by doing XML-to-DOM parsing stage yourself and examining the root element namespace or some such; see the 'multiroot' example for details), and dispatching to the corresponding generated code. Boris From boris at codesynthesis.com Wed Oct 14 09:42:45 2015 From: boris at codesynthesis.com (Boris Kolpackov) Date: Wed Oct 14 09:42:47 2015 Subject: [xsd-users] Problem with OGC GML - anyType values In-Reply-To: <1444717909.741284721@f394.i.mail.ru> References: <1444717909.741284721@f394.i.mail.ru> Message-ID: Hi Alexander, Alexander Yadykin writes: > But I don't understand how to push it to parent element > "gml::MetaDataPropertyType". Have you studied the 'wildcard' example? It does exactly this: creates a fragment of the object model and then serializes it to the wildcard element. Boris From viktor at ppnet.ee Wed Oct 14 12:49:35 2015 From: viktor at ppnet.ee (Viktor Kutuzov) Date: Thu Oct 15 05:57:55 2015 Subject: [xsd-users] XSD-4.0.0: build-time dependcy of cli-1.2.0 not satisfied Message-ID: <561E879F.9070708@ppnet.ee> Hello, I try to compile xsd-4.0.0 on Gentoo 64-bit. In compiler dependencies there is specified the cli-1.2.0. But last version of cli libriry is cli-1.1.0. Can you, please, clarify whether is it possible to compile xsd-4.0.0 with last cli version or not? Best regards, Viktor Kutuzov From yadykin_a at mail.ru Thu Oct 15 07:59:55 2015 From: yadykin_a at mail.ru (=?UTF-8?B?QWxleGFuZGVyIFlhZHlraW4=?=) Date: Thu Oct 15 10:23:07 2015 Subject: =?UTF-8?B?UmVbMl06IFt4c2QtdXNlcnNdIFByb2JsZW0gd2l0aCBPR0MgR01MIC0gYW55?= =?UTF-8?B?VHlwZSB2YWx1ZXM=?= In-Reply-To: References: <1444717909.741284721@f394.i.mail.ru> Message-ID: <1444910395.308909175@f347.i.mail.ru> Dear Boris, Thanks for you response! It helps to solve my problem completely. Actually I lost 'wildcard' example from my field of view. Best regards, Alexander From boris at codesynthesis.com Thu Oct 15 10:56:38 2015 From: boris at codesynthesis.com (Boris Kolpackov) Date: Thu Oct 15 10:56:39 2015 Subject: [xsd-users] XSD-4.0.0: build-time dependcy of cli-1.2.0 not satisfied In-Reply-To: <561E879F.9070708@ppnet.ee> References: <561E879F.9070708@ppnet.ee> Message-ID: Hi Viktor, Viktor Kutuzov writes: > I try to compile xsd-4.0.0 on Gentoo 64-bit. In compiler > dependencies there is specified the cli-1.2.0. But last version of > cli libriry is cli-1.1.0. > > Can you, please, clarify whether is it possible to compile xsd-4.0.0 > with last cli version or not? Ok, this is not a simply yes/no answer: 1. The packaged source code distribution of xsd comes with pre-generated command line interface handling code (that's what this 'cli' is for). So it should be possible to compile xsd-4.0.0 without installing any cli, 1.1.0 or 1.2.0. 2. If you want to re-generate the command line interface handling code, then cli-1.1.0 won't do. But 1.2.0 hasn't been released yet. 3. If you would like to go the #2 route, I would be happy to package a pre-release of cli-1.2.0 for you. The final release is going to happen soon but we still need to finish a few things before this can happen. Boris From hhusp at outlook.com Tue Oct 20 06:26:07 2015 From: hhusp at outlook.com (hhusp house) Date: Tue Oct 20 06:26:14 2015 Subject: [xsd-users] expat parser and elements.txx error Message-ID: I changed parser-rules.make to use the expat parser. XML_PARSER := expat When I try to build the hello example in (xsd-4.0/examples/cxx/parser/hello)I get the error:../../../../libxsd/xsd/cxx/parser/expat/elements.txx:282: error: no match for ?operator==? in ?parser == 0? Linux distribution: CentOS release 6.7 (Final)xsd 4.0.0g++ version (-v)gcc version 4.4.7 20120313 (Red Hat 4.4.7-16) (GCC) Complete output:../../../../bin/xsd cxx-parser --xml-parser expat hello.xsdg++ -I../../../../libxsd -W -Wall -O3 -c driver.cxx -o driver.oIn file included from ../../../../libxsd/xsd/cxx/parser/expat/elements.hxx:360, from hello-pskel.hxx:70, from driver.cxx:7:../../../../libxsd/xsd/cxx/parser/expat/elements.txx: In member function ?bool xsd::cxx::parser::expat::document::parse(std::istream&, const std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> >*, const std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> >*, xsd::cxx::xml::error_handler&)?:../../../../libxsd/xsd/cxx/parser/expat/elements.txx:282: error: no match for ?operator==? in ?parser == 0? From boris at codesynthesis.com Tue Oct 20 10:26:13 2015 From: boris at codesynthesis.com (Boris Kolpackov) Date: Tue Oct 20 10:26:09 2015 Subject: [xsd-users] expat parser and elements.txx error In-Reply-To: References: Message-ID: hhusp house writes: > When I try to build the hello example in (xsd-4.0/examples/cxx/parser/hello) > I get the error:../../../../libxsd/xsd/cxx/parser/expat/elements.txx:282: > error: no match for ?operator==? in ?parser == 0? Yes, this is a known bug that has been fixed for the next release: http://scm.codesynthesis.com/?p=xsd/xsd.git;a=commit;h=94cba986108a0e0f42295572ca42c356d59328d7 You can also fix it in 4.0.0 by applying the patch from the above commit. Boris From hhusp at outlook.com Tue Oct 20 15:18:58 2015 From: hhusp at outlook.com (hhusp house) Date: Tue Oct 20 15:19:05 2015 Subject: [xsd-users] expat parser and elements.txx error In-Reply-To: References: , Message-ID: thanks for the quick reply and the fix. Rob > Date: Tue, 20 Oct 2015 16:26:13 +0200 > From: boris@codesynthesis.com > To: hhusp@outlook.com > CC: xsd-users@codesynthesis.com > Subject: Re: [xsd-users] expat parser and elements.txx error > > hhusp house writes: > > > When I try to build the hello example in (xsd-4.0/examples/cxx/parser/hello) > > I get the error:../../../../libxsd/xsd/cxx/parser/expat/elements.txx:282: > > error: no match for ?operator==? in ?parser == 0? > > Yes, this is a known bug that has been fixed for the next release: > > http://scm.codesynthesis.com/?p=xsd/xsd.git;a=commit;h=94cba986108a0e0f42295572ca42c356d59328d7 > > You can also fix it in 4.0.0 by applying the patch from the above > commit. > > Boris From zhorvath at vrvis.at Wed Oct 21 03:23:04 2015 From: zhorvath at vrvis.at (=?UTF-8?Q?Zsolt_Horv=c3=a1th?=) Date: Wed Oct 21 03:31:34 2015 Subject: [xsd-users] Visual studio 2015 support Message-ID: <56273D58.6050906@vrvis.at> Hello, I would like to know if xsd is working with msvc 14 explicitly, since it is not listed in the supported compilers section? If it is not, when will the support added? Thanks for the asnwer. Best regards, Zsolt Horv?th From hhusp at outlook.com Wed Oct 21 03:34:13 2015 From: hhusp at outlook.com (hhusp house) Date: Wed Oct 21 03:34:21 2015 Subject: [xsd-users] expat parser and elements.txx error In-Reply-To: References: , , , Message-ID: Hi Boris, I've copied both files to ./xsd-4.0/libxsd/xsd/cxx/parser/expat/Got the same error. I've include the difference of elements.hxx and elements.txx and the original files below. regards Rob make cleanmake../../../../bin/xsd cxx-parser --xml-parser expat hello.xsdg++ -I../../../../libxsd -W -Wall -O3 -c driver.cxx -o driver.oIn file included from ../../../../libxsd/xsd/cxx/parser/expat/elements.hxx:362, from hello-pskel.hxx:70, from driver.cxx:7:../../../../libxsd/xsd/cxx/parser/expat/elements.txx: In member function ?bool xsd::cxx::parser::expat::document::parse(std::istream&, const std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> >*, const std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> >*, xsd::cxx::xml::error_handler&)?:../../../../libxsd/xsd/cxx/parser/expat/elements.txx:282: error: no match for ?operator==? in ?parser == 0?../../../../libxsd/xsd/cxx/parser/xml-schema.ixx:338: note: candidates are: diff elements.txx elements.txx.org286,287c286< parse_begin (< parser.get (), system_id ? *system_id : *public_id, eh);---> parse_begin (parser, system_id ? *system_id : *public_id, eh);289c288< parse_begin (parser.get (), eh);---> parse_begin (parser, eh);314,317c313,314< if (XML_Parse (parser.get (),< buf,< is.gcount (),< is.eof ()) == XML_STATUS_ERROR)---> if (XML_Parse (> parser, buf, is.gcount (), is.eof ()) == XML_STATUS_ERROR)825d821< diff elements.hxx elements.hxx.org54,56c54< typedef< std::unique_ptr< parser_auto_ptr;---> typedef std::unique_ptr parser_auto_ptr;365d362< > From: hhusp@outlook.com > To: xsd-users@codesynthesis.com > Subject: RE: [xsd-users] expat parser and elements.txx error > Date: Tue, 20 Oct 2015 21:18:58 +0200 > > thanks for the quick reply and the fix. > Rob > > > Date: Tue, 20 Oct 2015 16:26:13 +0200 > > From: boris@codesynthesis.com > > To: hhusp@outlook.com > > CC: xsd-users@codesynthesis.com > > Subject: Re: [xsd-users] expat parser and elements.txx error > > > > hhusp house writes: > > > > > When I try to build the hello example in (xsd-4.0/examples/cxx/parser/hello) > > > I get the error:../../../../libxsd/xsd/cxx/parser/expat/elements.txx:282: > > > error: no match for ?operator==? in ?parser == 0? > > > > Yes, this is a known bug that has been fixed for the next release: > > > > http://scm.codesynthesis.com/?p=xsd/xsd.git;a=commit;h=94cba986108a0e0f42295572ca42c356d59328d7 > > > > You can also fix it in 4.0.0 by applying the patch from the above > > commit. > > > > Boris > From hhusp at outlook.com Wed Oct 21 05:42:28 2015 From: hhusp at outlook.com (hhusp house) Date: Wed Oct 21 05:42:36 2015 Subject: [xsd-users] expat parser and elements.txx error In-Reply-To: References: , , , , , , Message-ID: Hi I noticed that the message is missing CR's. Retry: Hi Boris, I've copied both files to ./xsd-4.0/libxsd/xsd/cxx/parser/expat/Got the same error. I've include the difference of elements.hxx and elements.txx and the original files below. regards Rob make cleanmake../../../../bin/xsd cxx-parser --xml-parser expat hello.xsdg++ -I../../../../libxsd -W -Wall -O3 -c driver.cxx -o driver.oIn file included from ../../../../libxsd/xsd/cxx/parser/expat/elements.hxx:362, from hello-pskel.hxx:70, from driver.cxx:7:../../../../libxsd/xsd/cxx/parser/expat/elements.txx: In member function ?bool xsd::cxx::parser::expat::document::parse(std::istream&, const std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> >*, const std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> >*, xsd::cxx::xml::error_handler&)?:../../../../libxsd/xsd/cxx/parser/expat/elements.txx:282: error: no match for ?operator==? in ?parser == 0?../../../../libxsd/xsd/cxx/parser/xml-schema.ixx:338: note: candidates are: diff elements.txx elements.txx.org286,287c286< parse_begin (< parser.get (), system_id ? *system_id : *public_id, eh);---> parse_begin (parser, system_id ? *system_id : *public_id, eh);289c288< parse_begin (parser.get (), eh);---> parse_begin (parser, eh);314,317c313,314< if (XML_Parse (parser.get (),< buf,< is.gcount (),< is.eof ()) == XML_STATUS_ERROR)---> if (XML_Parse (> parser, buf, is.gcount (), is.eof ()) == XML_STATUS_ERROR)825d821< diff elements.hxx elements.hxx.org54,56c54< typedef< std::unique_ptr< parser_auto_ptr;---> typedef std::unique_ptr parser_auto_ptr;365d362< > From: hhusp@outlook.com > To: xsd-users@codesynthesis.com > Subject: RE: [xsd-users] expat parser and elements.txx error > Date: Wed, 21 Oct 2015 09:34:13 +0200 > > > > > Hi Boris, > I've copied both files to ./xsd-4.0/libxsd/xsd/cxx/parser/expat/Got the same error. I've include the difference of elements.hxx and elements.txx and the original files below. > regards Rob > make cleanmake../../../../bin/xsd cxx-parser --xml-parser expat hello.xsdg++ -I../../../../libxsd -W -Wall -O3 -c driver.cxx -o driver.oIn file included from ../../../../libxsd/xsd/cxx/parser/expat/elements.hxx:362, from hello-pskel.hxx:70, from driver.cxx:7:../../../../libxsd/xsd/cxx/parser/expat/elements.txx: In member function ?bool xsd::cxx::parser::expat::document::parse(std::istream&, const std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> >*, const std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> >*, xsd::cxx::xml::error_handler&)?:../../../../libxsd/xsd/cxx/parser/expat/elements.txx:282: error: no match for ?operator==? in ?parser == 0?../../../../libxsd/xsd/cxx/parser/xml-schema.ixx:338: note: candidates are: > diff elements.txx elements.txx.org286,287c286< parse_begin (< parser.get (), system_id ? *system_id : *public_id, eh);---> parse_begin (parser, system_id ? *system_id : *public_id, eh);289c288< parse_begin (parser.get (), eh);---> parse_begin (parser, eh);314,317c313,314< if (XML_Parse (parser.get (),< buf,< is.gcount (),< is.eof ()) == XML_STATUS_ERROR)---> if (XML_Parse (> parser, buf, is.gcount (), is.eof ()) == XML_STATUS_ERROR)825d821< > diff elements.hxx elements.hxx.org54,56c54< typedef< std::unique_ptr< parser_auto_ptr;---> typedef std::unique_ptr parser_auto_ptr;365d362< > > From: hhusp@outlook.com > > To: xsd-users@codesynthesis.com > > Subject: RE: [xsd-users] expat parser and elements.txx error > > Date: Tue, 20 Oct 2015 21:18:58 +0200 > > > > thanks for the quick reply and the fix. > > Rob > > > > > Date: Tue, 20 Oct 2015 16:26:13 +0200 > > > From: boris@codesynthesis.com > > > To: hhusp@outlook.com > > > CC: xsd-users@codesynthesis.com > > > Subject: Re: [xsd-users] expat parser and elements.txx error > > > > > > hhusp house writes: > > > > > > > When I try to build the hello example in (xsd-4.0/examples/cxx/parser/hello) > > > > I get the error:../../../../libxsd/xsd/cxx/parser/expat/elements.txx:282: > > > > error: no match for ?operator==? in ?parser == 0? > > > > > > Yes, this is a known bug that has been fixed for the next release: > > > > > > http://scm.codesynthesis.com/?p=xsd/xsd.git;a=commit;h=94cba986108a0e0f42295572ca42c356d59328d7 > > > > > > You can also fix it in 4.0.0 by applying the patch from the above > > > commit. > > > > > > Boris > > > > From boris at codesynthesis.com Wed Oct 21 06:16:42 2015 From: boris at codesynthesis.com (Boris Kolpackov) Date: Wed Oct 21 06:16:37 2015 Subject: [xsd-users] expat parser and elements.txx error In-Reply-To: References: Message-ID: Hi, hhusp house writes: > Hi I noticed that the message is missing CR's. Retry: Still a mess. > I've copied both files to ./xsd-4.0/libxsd/xsd/cxx/parser/expat/ Got the > same error. Ok, looks like that's a new one: http://scm.codesynthesis.com/?p=xsd/xsd.git;a=commit;h=0e5fab0664fb36c6253dfd7bb86d8985d1b349ef Thanks, Boris From hhusp at outlook.com Wed Oct 21 07:39:10 2015 From: hhusp at outlook.com (hhusp house) Date: Wed Oct 21 07:39:18 2015 Subject: [xsd-users] expat parser and elements.txx error In-Reply-To: References: , , , , , Message-ID: Hi Boris, yep its fixed. thanksRob > Date: Wed, 21 Oct 2015 12:16:42 +0200 > From: boris@codesynthesis.com > To: hhusp@outlook.com > CC: xsd-users@codesynthesis.com > Subject: Re: [xsd-users] expat parser and elements.txx error > > Hi, > > hhusp house writes: > > > Hi I noticed that the message is missing CR's. Retry: > > Still a mess. > > > > I've copied both files to ./xsd-4.0/libxsd/xsd/cxx/parser/expat/ Got the > > same error. > > Ok, looks like that's a new one: > > http://scm.codesynthesis.com/?p=xsd/xsd.git;a=commit;h=0e5fab0664fb36c6253dfd7bb86d8985d1b349ef > > Thanks, > Boris From boris at codesynthesis.com Wed Oct 21 09:54:33 2015 From: boris at codesynthesis.com (Boris Kolpackov) Date: Wed Oct 21 09:54:28 2015 Subject: [xsd-users] Visual studio 2015 support In-Reply-To: <56273D58.6050906@vrvis.at> References: <56273D58.6050906@vrvis.at> Message-ID: Hi Zsolt, Zsolt Horv?th writes: > I would like to know if xsd is working with msvc 14 explicitly, > since it is not listed in the supported compilers section? Yes, quite a few people are using it with VC++ 2015/14.0 without any problems. We will be adding project/solution files for the examples in the next release. Boris