On Tue, Aug 07, 2012 at 08:51:59AM +0100, Alex Macfarlane Smith wrote:
> Could we not do what you suggest just above - add an additional tag
> to the RiscPkg info to indicate its compatibility?
>
> Compatibility: armv7, armv6, armv5
>
> (or whatever)
We can, potentially. It's slightly more complicated than that because of
things like FPA, soft FP, VFP2, VFP3 etc, but I'm sure there's some way to
express all the allowed combinations.
But the issue is slightly different, which is a wish to push out tested
software to a particular audience. Something might work on ARMv7 but not
actually be something we want to advertise to users... say it needs a piece
of hardware that isn't relevant, or is a tool which has a broken UI, it's a
library that's built as part of the build process but isn't of interest to
users, or is simply out of date (GCC 2.95 on the RiscPkg site, anyone?).
I'm sure there is a way to express all this in the packages file, but a
simple white/blacklist of packages would seem a simpler way to do it... the
full unedited packages file is always available should people want to use
that instead/in addition.
Theo
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
No comments:
Post a Comment