>> >> >> Dear all, >> >> two small questions: >> 1) the core images are in are tar.bz2 format. Like the ones located in >> http://repo.meego.com/MeeGo/builds/trunk/1.1.80.8.20101130.1/core/images/ >> How can I chroot these images ? mic-chroot wants .img file as input. >> (I didn't find an answer on wiki) > > See http://wiki.meego.com/SDK/Docs/1.1/Building_a_MeeGo_chroot_on_Linux > which covers unpacking and chrooting images. Thanks Elliot for the tips. Sorry for not being clear enough. I will try to rephrase. I can do mic-chroot to http://repo.meego.com/MeeGo/builds/trunk/1.1.80.8.20101130.1/ivi/images/meego-ivi-ia32/meego-ivi-ia32-1.1.80.8.20101130.1.img And compile source packages in this chroot'ed environment.
But what is the purpose of the following images: http://repo.meego.com/MeeGo/builds/trunk/1.1.80.8.20101130.1/core/images/meego-core-ia32-madde-sysroot/meego-core-ia32-madde-sysroot-1.1.80.8.20101130.1-fs.tar.bz2 http://repo.meego.com/MeeGo/builds/trunk/1.1.80.8.20101130.1/core/images/meego-core-armv7l-madde-sysroot/meego-core-armv7l-madde-sysroot-1.1.80.8.20101130.1-fs.tar.bz2 Can they be chrooted and used for compilation? Or these are just a runtime rootfs images for QEMU ? >> >> 2) are there devel images with cross-toolchain ? > > I'm not sure what you're asking for (MeeGo netbook images which have a > cross-toolchain for ARM?). > > But if you need a toolchain for cross-compiling, you could try > installing the SDK with MADDE: > > http://wiki.meego.com/SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Linux Many thanks for this advice. _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
