Schemas/COLLADA
From Code Synthesis Wiki
(Difference between revisions)
| Revision as of 09:35, 26 January 2007 Boris (Talk | contribs) (Start the COLLADA schema page) ← Previous diff |
Revision as of 14:13, 2 August 2007 Boris (Talk | contribs) (Remove deprecated options) Next diff → |
||
| Line 3: | Line 3: | ||
| The following C++/Tree mapping options are recommended to compile the COLLADA schema: | The following C++/Tree mapping options are recommended to compile the COLLADA schema: | ||
| - | --morph-anonymous --generate-polymorphic --root-element COLLADA | + | --generate-polymorphic --root-element COLLADA |
| If your C++ compiler runs out of memory while compiling the generated <code>COLLADASchema_VVV.cxx</code>, then you can overcome this by splitting the generated source code into several parts with the <code>--parts</code> option, e.g., | If your C++ compiler runs out of memory while compiling the generated <code>COLLADASchema_VVV.cxx</code>, then you can overcome this by splitting the generated source code into several parts with the <code>--parts</code> option, e.g., | ||
Revision as of 14:13, 2 August 2007
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. 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.
