Petalinux 2017.2 GIT versioned and relocatable flow
I am trying to create a reproducable petalinux project flow with 2017.2 . The petalinux project is checked into a GIT repository and one should be able to check out a clean project, update the hardware description from the latest PL bitstream build and generate BOOT.bin, rootfs.cpio and image.ub automatically. This should happen in a somewhat flexible way, that it can be done by developers and in an automated build environment. This seemed to me the most natural way to use petalinux, but apparently this is not the intended usage scenario.