Re: Yocto with Initial RamFS

[Brian Smucker <bds@bsmucker.eu.org>]

Thanks Soren,

My followup question is: Can I mix toolchains in this situation?

Can I compile the initramfs binaries with the uclibc toolchain based on 
the poky-tiny distro and the regular file system binaries with the 
glibc-based toolchain (based on a different distro)?

If this is possible, how would I begin to do it?

Thanks,

Brian

On 5/29/2014 8:38 AM, Søren Holm wrote:
> Torsdag den 29. maj 2014 08:07:11 skrev Brian Smucker:
>> Hi,
>>
>> Was wondering why this has not been answered.  Maybe it is too dumb of a
>> question? If so, let me know or point me to some documentation.
>>
> I'm declaring an initramfs-image like this. As you can see the recipe is
> derived from core-image-minimal-initramfs. The package initramfs-vm provides
> the script /init executed on boot.
>
> The "assembling" of the actual bootable image with initramfs and rootfs (in my
> case a squashfs) is done in another script.
>
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> # initramfs for vm-image. Derived from core-image-minimal-initramfs
> DESCRIPTION = "Small image capable of booting a a squashfs+aufs filesystem"
>
> IMAGE_INSTALL = "initramfs-vm-boot busybox udev base-passwd"
>
> # Do not pollute the initrd image with rootfs features
> IMAGE_FEATURES = ""
> IMAGE_LINGUAS = ""
> #DISTRO_FEATURES = ""
>
> inherit core-image
>
> IMAGE_FSTYPES = "cpio"
>
> IMAGE_PREPROCESS_COMMAND = "cb16_remote_bloat;"
>
> cb16_remote_bloat() {
>          rm -r ${IMAGE_ROOTFS}/boot
> }
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>