boris at codesynthesis.com
Fri Jun 29 13:48:15 EDT 2007
Prather, Ryan C SSgt DMSG/WMTS <Ryan.Prather at afspc.af.mil> writes:
> Great. We are primarily deploying to Sun...is there going to be a 3.0
> release version for Sun? If not will the Linux version work on Solaris
The final release will be test on and have binaries for Solaris.
> Also I am getting the following compile time error
> Creating DataSet class using XSD ...
> error: unknown command '/nologo'
> info: try 'xsd help' for the list of commands
> 'cl' is not recognized as an internal or external command,
> operable program or batch file.
> xsd /nologo /d /l:"Microsoft.MCpp.MCppCodeProvider, MCppCodeDomProvider,
> Version=7.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a,
> Custom=null" /namespace:Data .\Data.xsd
> cl /nologo /TP /FU System.dll /FU System.XML.dll /FU System.Data.dll
> "Data.h" /clr /Fo"Debug" /link /dll /out:"Data.dll"
When you add a schema file to your project, Visual Studio assumes you
want it compiled with their .NET data binding tool and generates the
above command line. You will need to change this by right-clicking
on the schema file in Visual Studio, selecting properties, and
setting a custom build step for it. You will need to provide
the new command line which should look along these lines:
xsd cxx-parser your-schema.xsd
as well as the output files (for 3.0.0 they will be in the form:
your-schema-pskel.hxx and your-schema-pskel.cxx). You can look
into one of the examples in examples/cxx/parser/ for ideas.
Alternatively (or at the beginning) you can compile your schemas
manually from the command prompt without involving the IDE.
More information about the xsd-users