Boost logo

Boost-Build :

From: greg_sylvain (gsylvain_at_[hidden])
Date: 2005-07-13 06:38:47

Thanks for the reply. Sorry for the mis-direct posting.

LEIF's xsd2cpp tool generates a C++ class for each xsd:complexType
in the XSD schema. Accordingly, you can get a lot of classes from a
single schema file. All of the class files have a respective '.h'
header file for a respective implentation file ('.cpp').

In addition, the tool can take a configuration file that can re-map
any complexType element names to the respective C++ class name you
desire. For instance, all of our complexTypes are spelled out in
lower case and underscores, while our C++ class names use Hungarian
notation of mixed case class names. That it, the XSD complexType
ruleset_directive is remaped to become the C++ class RulesetDirective.

There is an option to the xsd2cpp tool to have all class files put
into a seperate (sub)directory.

Thanks again for any assitance,

--- In jamboost_at_[hidden], Vladimir Prus <ghost_at_c...> wrote:
> Hi Gregory,
> > We are currently using boost_1_32_0 and I'm trying to write a
toolset file
> > to enable us to use Roguewave's LEIF xsd2cpp C++ class generator
> > within bjam. (The xsd2cpp command is just a C++ class generator
> > generates C++ class from a respective W3C XSD Schema).
> Please post Boost.Build related questions to the
> mailining list. You can also access it via newsgroups. See
> for the links.
> > I'm not having much luck, I've been through the boost build
> > samples, etc. and I'm still having problems.
> >
> > In the end, I would like to be able to write a library rule such
as :
> >
> > lib libclientxml
> > :
> > schemas.xsd
> > ;
> >
> >
> > And have boost run RW's xsd2cpp tool run on the file schemas.xsd
and all
> > of the resulting cpp files that are generated would be compiled
> > archived in libclientxml.
> The biggest question is whether the tool produces files with some
> names, or files with names depending on the content of source file.
> The first case is simple, and the second case can be nontrivial --
how can
> we know which files were produced, then?
> - Volodya


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at