[xsd-users] Building XSD

[Southworth Damon (AA/EOP1-PE)]

Thanks Boris for the quick response.

> Are you talking about these instructions or something else?

I was referring primarily to the build instructions within the READ.md of the xsd repository.
The output I referred to was after the  "b install: ../xsd-install/xsd/" stage.

> So I would suggest that you try to go with the new layout. If there are
> some specific issues that you run into, let me know and we can see how
> they can be addressed.

Thanks for the information. I will look to adopt the new  format.
I think the only question I would have in addition to adopting this format would be:
Why is the required cxx header tree not included within the include folder of the install location?
These need to be included as they are used by the code generated by the xsd compiler.

Regards,

Damon Southworth.

________________________________
From: Boris Kolpackov <boris at codesynthesis.com>
Sent: Monday, August 7, 2023 1:44 PM
To: Southworth Damon (AA/EOP1-PE) <damon.southworth at uk.bosch.com>
Cc: xsd-users at codesynthesis.com <xsd-users at codesynthesis.com>
Subject: Re: [xsd-users] Building XSD

Southworth Damon (AA/EOP1-PE) <damon.southworth at uk.bosch.com> writes:

> It has come to a point where I would also like to be able to build
> natively on our ARM platforms rather than cross compile. For this I
> wanted to get a version of xsd for this platform, so I decided to build
> the latest version from the xsd repository. This is done using build2
> as per the instructions.

Are you talking about these instructions or something else?

https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodesynthesis.com%2Fproducts%2Fxsd%2Fdoc%2Finstall-build2.xhtml&data=05%7C01%7Cdamon.southworth%40uk.bosch.com%7C19760d11324b43ba6d7c08db9743fea3%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C638270090504651462%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GDnP6eNNb8dEmj3yopBS7gry%2FOstIb3KN%2BydgUkeVhY%3D&reserved=0<https://codesynthesis.com/products/xsd/doc/install-build2.xhtml>


> I have managed to build it, but the result I achieve does not match
> the contents of the original tarballs that I have for the other
> platforms.
>
> The originals contained the following:
>     "bin  doc  examples  FLOSSE  GPLv2  libxsd  LICENSE  NEWS  README
>      version"
> With a self contained xsd in the bin folder and the header files in libxsd.
>
> After the build2 install has completed I end up with the following:
>     "bin  include  lib  share"
>
> This version of xsd is dependent on the libraries built in the lib
> folder and there is are no headers files.
>
> Is there a way to automatically get a build that is equivalent to the
> downloaded tarballs?

As a bit of background, the original layout was created half-manually,
which was a lot of effort to maintain and the switch to build2 was
partly motivated by that. With the build2-based build you by default
get the standard Linux filesystem layout (executables in bin/, headers
in include/, and libraries in lib/). While you can customize this quite
a bit[1], I don't think it will be easy to achieve the old layout without
some manual post-processing steps.

So I would suggest that you try to go with the new layout. If there are
some specific issues that you run into, let me know and we can see how
they can be addressed.

[1] https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuild2.org%2Fbuild2%2Fdoc%2Fbuild2-build-system-manual.xhtml%23intro-operations-install&data=05%7C01%7Cdamon.southworth%40uk.bosch.com%7C19760d11324b43ba6d7c08db9743fea3%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C638270090504651462%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zgG5J0tOifN%2FrUHhfxQm6%2BcE7dgBWae3rkark8p7lmc%3D&reserved=0<https://build2.org/build2/doc/build2-build-system-manual.xhtml#intro-operations-install>