Personally, i haven't found this on meego-sdk probably due to some nice mail 
traffic optimization in between us...

== Sysroots.

The number of sysroot packages corresponds to the whole number of targets 
(incluging variations like NEON, SSSE3?..). (TBD: the extended targets list). 

a) Having all these targets supported by the ebmedded/trunk gcc we can build 
all sysroots inside the OBS (from glibc + glibc ports +  linux headers) 
whenever something changes, so only when needed and quickly. Specs/dscs should 
be based on those existing specs/dscs from the corresponding packages, but 
nobody can guarantee that they will always reflect 100% the original ones, so 
we'd get diffs between actual Meego images and sysroots. These minor gaps 
probably may be ignored, however.

b) Having an external (to the OBS) process of creating Meego images we may 
cherry-pick a huge number of files and create/publish all sysroot tarballs 
externally, and still build packages inside the OBS (on the same time basis as 
for the images, so lags are expected).

c) With tools like mic2 we can perform some other build cycle for sysroot 
tarballs, not depending on that of images. Root access would be required and a 
lot of garbage would be expected if something goes wrong, so this part of 
scenario isn't probably possible/welcome inside the OBS (FIXME). Still, all 
further packaging can be done inside.

== Toolchains.

A single (extended?) target toolchain may be something like (cross-)gcc 
depending on [ target sysroot, (cross-)binutils, (cross-)gdb ]. Multiple 
toolchains should coexist in a system (multitarget, multilib)

== Non-Linux hosts.

Even we can produce toolchains binaries for Windows (with mingw32/64) and 
probably can package stuff (with WiX to MSI), the OBS can't handle that 
(FIXME).

For MacOS all that had to be done on a real Apple machine at all (FIXME), 
using very proprietary software, apparently outside OBS.

Buildbot?

-- 
Best regards,
Al
_______________________________________________
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Reply via email to