The problem is that kivy is ignoring all of the attempts at telling it to build in a sysroot and *still* looking in /usr. This is a clear cut bug in the kivy build system, so you'll have to look at that and see how to fix it.
Ross On Mon, 24 Jun 2019 at 18:32, Mauro Ziliani <ma...@faresoftware.it> wrote: > > Hi all. > > I'm trying to compile kivy inside yocto for a 586 board. > > The compilation fails because the i586-cc uses /usr/include and > /usr/local/include paths as INCLUDEDIR (togheter with others paths) > > > How can avoid this? > > > I need /usr/include o /usr/local/include for other apps, but I don't > like the /usr/include is involved in yocto > > > MZ > > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
