[xsde-users] Bug?

[Boris Kolpackov]

Hi Laurent,

Laurent Michel <laurent1984 at gmail.com> writes:

> Regarding ICU and Xerces-c, I think you are wrong, because in order to
> compile XSD/e, I needed to link against xerces-c. In order compile
> xerces-c, I needed to link against icu (because for some reason linking
> against iconv didn't work).

I may very well be wrong, though, normally, we don't compile the XSD/e
compiler (the only part in XSD/e that depends on Xerces-C++) for a mobile
target. Instead we compile it for a "host development platform", such as
Linux or Windows. We then use that compiler binary to generate C++ source
code which you then cross-compile to your mobile target.

It may be possible to run the XSD/e compiler natively on your phone.
However, we don't test it and don't support it -- life is too short ;-).


> Other question: I have noticed that sometimes the c++ code generated by
> XSD/e contains classes with private copy constructors. In what cases do you
> generate such classes? In my case, I don't think it's making any sense. The
> class is only containing strings and sequences of strings and still, copy
> is disabled. Why?

Because they are variable-length (i.e., own dynamically-allocated memory).
XSD/e, being very minimal, does not support automatic copying of such
objects.

Boris