[gccsdk] autobuilder and vfp

alan buckley alan_baa at hotmail.com
Thu Nov 26 05:41:32 PST 2015

There now seems to be a few programs in the autobuilder that
would benefit from VFP versions being made available for the
newer machines that can use it.

We still need the non-VFP versions for the large number of
people using old RISC OS kit or emulators.

Has anybody any ideas on what we can do to allow this?

My initial thought was a new AB_VFP flag to specify the build
would generate a VFP version. Then we would need to run the
autobuilder twice, once for each version.

I don’t know what’s involved to configure something for VFP to
know if that is a sensible suggestion.

The second way would be to have a separate item for the
VFP version in the autobuilder.

Once that has been determined it needs to be decided how it
is packaged for PackMan and the website.

I don’t think there is a problem with shared libraries here as
the are installed to different locations and can stand beside
the non VFP versions. But they may need a different package
name so they can be selected as well.

For the main programs, my initial thought would be to give
them a different zip name, but keep that package name the
same and add a flag to the package control record to say
it’s for VFP machines.

Then the flag can either be used to generate an autobuilder-vfp
list or (probably better) PackMan could use the flag and select
the VFP version on machines that have VFP.

Anyone have any thoughts or suggestions?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.riscos.info/pipermail/gcc/attachments/20151126/3a09c7d6/attachment.html>

More information about the gcc mailing list