[xsde-users] Bug?

[Laurent Michel]

Hi Boris,

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). And ... my application is working under android
since yesterday night, in the very way I told you I compiled everything,
which is also, in my opinion, the natural way to do it (when you know
nothing about cross-compiling).

When I have some time, I will try to follow the instructions of the INSTALL
file. But I checked the config.make and the Android.mk and I can't remember
having seen any command that would overwrite the ranlib and ar binaries.

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?

Cheers,
Laurent

On Mon, Feb 20, 2017 at 6:30 PM, Boris Kolpackov <boris at codesynthesis.com>
wrote:

> Hi Laurent,
>
> Laurent Michel <laurent1984 at gmail.com> writes:
>
> > It works, however, perfectly fine under my Ubuntu distro, it worked also
> > fine under Windows 10. What I don't really understand is, that I only
> link
> > against icu and xerces-c and I only include the xsd header files during
> > compilation, be it for windows 10, Ubuntu, or android.
>
> ICU and/or Xerces-C are probably not compatible with the Android runtime
> or you didn't compile them properly. We don't really support this
> configuration so I am not sure what's going on.
>
>
> > Here's how I cross-compile XSD/e [...]
>
> Can you try to download a pre-built binary (e.g., for Linux) and then
> cross-compile just libxsde/ as instructed in the accompanying INSTALL
> file?
>
> Boris
>