Wednesday, 30 March 2022

[gccsdk] Libraries

Hi all

As you might've guessed from my earlier messages, I've been updating Python to build with GCC10. I now have Python 3.10.4 built with GCC10, along with the stabdard library extensions that work on RISC OS (which is most but not all of them).

To allow me to do this, I've had to keep a separate tree of development libraries for both GCC10 and GCC4. I've not installed any of the -dev packages I've made via packman as I think the GCC10 versions would clash with the GCC4 ones - same package, different files.

I believe the shared libs used at runtime are okay as they live within a different directory within !SharedLibs, but is there a similar thing that can be done for the dev libs? I guess this is only an issue for native building.

A "not thought about it much" idea is something like this - taking LibBZ2 as an example

LibBZ2$abi2/0$Path would be <LIbBZ2$Dir>,<LibBZ2$Dir>.abi2/0.
LibBZ2$armeabihf$Path would be <LIbBZ2$Dir>,<LibBZ2$Dir>.armeabifh.

LibBZ2$Path need to mirror LibBZ2$abi2/0$Path to keep existing things working.

where <LibBZ2$Dir> contains directories h (for the headers) abi2/0 and armeabihf, each of which has a libbz2/a in it for the abi in question.

I'm sure someone will now point out why it won't work :)

Cheers

Chris


No comments:

Post a Comment