.\" Process this file with .\" groff -man -Tascii xsde.1 .\" .TH XSD/e 1 "September 2011" "XSD/e 3.3.0" .SH NAME xsde \- W3C XML Schema to C++ Compiler for Embedded Systems .\" .\" .\" .\"-------------------------------------------------------------------- .SH SYNOPSIS .\"-------------------------------------------------------------------- .B xsde .I command .B [ .I options .B ] .I file .B [ .I file .B ...] .in .B xsde help .B [ .I command .B ] .in .B xsde version .\" .\" .\" .\"-------------------------------------------------------------------- .SH DESCRIPTION .\"-------------------------------------------------------------------- .B xsde generates vocabulary-specific, statically-typed C++ mapping from W3C XML Schema definitions. Particular mapping to produce is selected by a .IR command . Each mapping has a number of mapping-specific .I options that should appear, if any, after the .IR command . Input files should be W3C XML Schema definitions. The exact set of the generated files depends on the selected mapping and options. .\" .\" .\" .\"-------------------------------------------------------------------- .SH COMMANDS .\"-------------------------------------------------------------------- .IP \fBcxx-hybrid\fR Generate the Embedded C++/Hybrid mapping. For each input file in the form .B name.xsd the following C++ files are generated: .B name.hxx (object model header file), .B name.ixx (object model inline file, generated only if the .B --generate-inline option is specified), .B name.cxx (object model source file), and .B name-fwd.hxx (object model forward declaration file, generated only if the .B --generate-forward option is specified). If the .B --generate-parser option is specified, the Embedded C++/Parser mapping is invoked and the .BR name-pskel.hxx , .BR name-pskel.ixx , and .B name-pskel.cxx parser skeleton files are generated, as described below. Additionally, the following parser implementation files are generated: .B name-pimpl.hxx (parser implementation header file) and .B name-pimpl.cxx (parser implementation source file). If the .B --generate-serializer option is specified, the Embedded C++/Serializer mapping is invoked and the .BR name-sskel.hxx , .BR name-sskel.ixx , and .B name-sskel.cxx serializer skeleton files are generated, as described below. Additionally, the following serializer implementation files are generated: .B name-simpl.hxx (serializer implementation header file) and .B name-simpl.cxx (serializer implementation source file). .IP \fBcxx-parser\fR Generate the Embedded C++/Parser mapping. For each input file in the form .B name.xsd the following C++ files are generated: .B name-pskel.hxx (parser skeleton header file), .B name-pskel.ixx (parser skeleton inline file, generated only if the .B --generate-inline option is specified), and .B name-pskel.cxx (parser skeleton source file). If the .B --generate-noop-impl or .B --generate-print-impl option is specified, the following additional sample implementation files are generated: .B name-pimpl.hxx (parser implementation header file) and .B name-pimpl.cxx (parser implementation source file). If the .B --generate-test-driver option is specified, the additional .B name-pdriver.cxx test driver file is generated. .IP \fBcxx-parser\fR Generate the Embedded C++/Serializer mapping. For each input file in the form .B name.xsd the following C++ files are generated: .B name-sskel.hxx (serializer skeleton header file), .B name-sskel.ixx (serializer skeleton inline file, generated only if the .B --generate-inline option is specified), and .B name-sskel.cxx (serializer skeleton source file). If the .B --generate-empty-impl option is specified, the following additional sample implementation files are generated: .B name-simpl.hxx (serializer implementation header file) and .B name-simpl.cxx (serializer implementation source file). If the .B --generate-test-driver option is specified, the additional .B name-sdriver.cxx test driver file is generated. .IP \fBhelp\fR Print usage information and exit. Use .PP .RS .RS 3 .B xsde help .I command .RE .PP for command-specific help. .RE .IP \fBversion\fR Print version and exit. .\"-------------------------------------------------------------------- .SH OPTIONS .\"-------------------------------------------------------------------- Command-specific .IR options , if any, should appear after the corresponding .IR command . .\" .\" Common options. .\" .SS common options