I’m looking at creating Raspberry Pi and VFP specific builds and package lists and have something working, but would just like to see if anyone has any objections before I check it in.
I’ve added a new Architecture field to the package control file and command line arguments and variables to support it in the GCCSDK build files. The new architecture field can be “rpi”, “vfp” or “arm” with “arm” being the default if nothing is specified. These will end up producing three package lists. autobuilt – the current list (architecture arm) autobuilt-vfp – vfp programs + any programs not in this list that are on the autobuilt list autobuilt-rpi – Raspberry Pi programs + any programs not in this list that are on the autobuilt-vfp list The website will produce a page for each architecture variant. I intend to follow Lee Noar’s established practice for the builds. This entails: - BUILD_NORMAL and BUILD_VFP variable in setvars to allow only one variant to be built, normally both will be set to “yes” to build both variants. - Shared libraries will ship with both arm and vfp versions of the libraries. - Static libraries include a vfp subdirectory with the VFP version of the static library. With applications, 2 or possibly 3 packages will be built, 1 for each architecture. Regards, Alan
_______________________________________________ GCCSDK mailing list [email protected] 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
