Schemas/COLLADA

From Code Synthesis Wiki

< Schemas(Difference between revisions)
Jump to: navigation, search
Revision as of 14:13, 2 August 2007
Boris (Talk | contribs)
(Remove deprecated options)
← Previous diff
Current revision
Boris (Talk | contribs)
(Note that Xerces-C++ 2.8.0 can handle COLLADA schemas out of the box)
Line 11: Line 11:
and compiling each part separately. and compiling each part separately.
-The COLLADA schema triggers the [http://issues.apache.org/jira/browse/XERCESC-1546 XERCESC-1546] bug in Xerces-C++ 2.7.0. If you are planning to have validation enabled when parsing COLLADA instance documents, then you will need to apply the [[Media:Xerces-c-2.7.0-1546.patch|xerces-c-2.7.0-1546.patch]] patch to fix this bug.+The COLLADA schema triggers the [http://issues.apache.org/jira/browse/XERCESC-1546 XERCESC-1546] bug in Xerces-C++ 2.7.0 and earlier. If you are planning to have validation enabled when parsing COLLADA instance documents, then you will need to apply the [[Media:Xerces-c-2.7.0-1546.patch|xerces-c-2.7.0-1546.patch]] patch to fix this bug. Xerces-C++ 2.8.0 and later have this bug fixed.

Current revision

This page contains information on using the COLLADA schema with XSD.

The following C++/Tree mapping options are recommended to compile the COLLADA schema:

--generate-polymorphic --root-element COLLADA

If your C++ compiler runs out of memory while compiling the generated COLLADASchema_VVV.cxx, then you can overcome this by splitting the generated source code into several parts with the --parts option, e.g.,

--parts 3

and compiling each part separately.

The COLLADA schema triggers the XERCESC-1546 bug in Xerces-C++ 2.7.0 and earlier. If you are planning to have validation enabled when parsing COLLADA instance documents, then you will need to apply the xerces-c-2.7.0-1546.patch patch to fix this bug. Xerces-C++ 2.8.0 and later have this bug fixed.

Personal tools