[xsd-users] xsd compiler question about the --file-per-type option

Schrader, Glenn - 1002 - MITLL gschrad at ll.mit.edu
Mon Apr 24 08:54:30 EDT 2017


Thanks, that  is what I was missing.
--glenn

-----Original Message-----
From: Boris Kolpackov [mailto:boris at codesynthesis.com] 
Sent: Thursday, April 20, 2017 12:19 PM
To: Schrader, Glenn - 1002 - MITLL
Cc: xsd-users at codesynthesis.com
Subject: Re: [xsd-users] xsd compiler question about the --file-per-type
option

Hi Glenn,

Schrader, Glenn - 1002 - MITLL <gschrad at ll.mit.edu> writes:

> The issue is that when I use -file-per-type the type definitions are 
> placed in separate header files as I expected but all of the parser 
> and serialization functions are placed into the <xxx>.hxx header (for 
> a schema file named "<xxx>.xsd"). I would have expected the parser and 
> serialization function prototypes to also be in the same header as the 
> type definition rather than in the common header that #includes
everything.
>  
> Is there some way to tell the compiler to include those definitions in 
> their corresponding type headers? I didn't seen an obvious compiler 
> parameter that looked relevant.

See the --fat-type-file option.

Boris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5471 bytes
Desc: not available
Url : http://codesynthesis.com/pipermail/xsd-users/attachments/20170424/da4d4071/smime.bin


More information about the xsd-users mailing list