03:32 <wens> :(

13:16 <warpme_> Hi *

13:17 <warpme_> Can anybody fluent in Yocto point me where are Yocto sources used to buid ‚part’ tool?

13:23 <narmstrong> warpme_: what do you mean by 'part' ?

14:28 <warpme_> I mean command used to prepare partitions on SD like here: https://github.com/superna9999/meta-meson/blob/sumo/wic/sdimage-bootpart-meson.wks

14:28 <warpme_> Isn’t it here: http://git.yoctoproject.org/clean/cgit.cgi/poky/tree/scripts/lib/wic?id=yocto-2.6 ?

14:35 <narmstrong> warpme_: it’s not a command, the .wks is a description for the wic tool

14:36 <narmstrong> See https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#ref-kickstart

14:37 <narmstrong> It’s based on the fedora kickstart file format

14:37 <warpme_> oh I mean command in .wks file like this: part /boot --source bootimg-partition --ondisk mmcblk --fstype=vfat --label BOOTFS --active --align 4096 --size 64

14:49 <warpme_> I’m looking on decription now. I see --ondisk or --ondrive: Forces the partition to be created on a particular disk. In standard procedure is it mean that this particular disk should be connected to system (i.e. SD card inserted so we have /dev/mmcblk) or it might be image file as well? I’m asking as I want to extend my build system with ability to create SD images remotelly (build is on remote server with access via ssh)

15:39 <narmstrong> It's only on an image file

15:39 <narmstrong> you can create sdcard image remotely then transfer them back to flash them locally

15:40 <narmstrong> I usually create wic.xz images that are very small and flash them using :

15:40 <narmstrong> `ssh server cat /path/to/image.wic.zx | xzcat | sudo dd of=/dev/mmcblk0 bs=16M`