Did anybody experience this error: ERROR: Nothing PROVIDES 'python-pyyaml-native'. Close matches: python-rpm-native python-pycurl-native python-numpy-native ERROR: Required build target 'core-image-minimal' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-minimal', 'virtual/fsbl', 'python-pyyaml-native']
I am following the short guides: http://www.wiki.xilinx.com/Using+meta-xilinx-tools+layer https://github.com/Xilinx/meta-xilinx-tool but I ended up in the above error. On Wed, Apr 19, 2017 at 3:00 PM, Jean-Francois Dagenais < [email protected]> wrote: > > On Apr 19, 2017, at 14:49, Giuseppe Di Guglielmo < > [email protected]> wrote: > > I do not know yet if I want to go to that extent. For sure, I have my own > PL devices and their device drivers. I was wondering if there is a stardar > way in Yocto to patch: > build/tmp/work/zc702_zynq7-poky-linux-gnueabi/u-boot- > xlnx/v2016.07-xilinx-v2016.3+gitAUTOINC+95e11f6eb4-r0/git/ > arch/arm/dts/zynq-zc702.dts > (for example) with my own DTS node for a specific PL device. > > > I find patches a bit hacky to generate and maintain over time IMHO. Their > a good way to quickly get away with a small change which doesn't change > until it is merged upstream for example. > > If you do "bitbake -c configure virtual/kernel" then go in the directory > where the git clone of the kernel is (tmp/work-shared/... or where you > point to (older yocto)), you can change the dts once in there, then use the > in-place git to generate a patch from the changes you just made... > > git add your_dts_file > git commit -m"Add my PL nodes to zynq-ac702's dts" > git format-patch HEAD^ > > Copy this patch over to your layer where you'll add a .bbappend for the > linux-xlnx recipe (linux-xlnx_%.bbappend), add your patch file to the > SRC_URI. This is pretty yocto standard way of doing things, look at other > bbappends. > > I find the mega-manual to be a continuously helpful reference: > > http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html > > There are other patching workflows explained there. > > >
-- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
