I have made some progress, and found out that it's ` *virtual/fakeroot-native*` that had to be in `*ASSUME_PROVIDED`.* But now I find there are quite a few more assumptions of the path to native tools. I'll see what I can patch locally and send out an update if get something working. On Sat Jan 24 2015 at 11:00:47 PM Ilya Dmitrichenko < errordevelo...@gmail.com> wrote:
> Adding Robert to CC list... > > On Sat Jan 24 2015 at 9:53:32 PM Ilya Dmitrichenko < > errordevelo...@gmail.com> wrote: > >> Hi List, >> >> I have attempted to define a custom build appliance image, with some >> degree of success. The only problem is that I have noticed is there is >> still a whole lot of `*-native` packages being pulled in when trying to >> build something. So I have attempted adding all of those to my image and >> set `ASSUME_PROVIDED` accordingly, it was still trying to build >> pseudo-native and sqlite3-native for some reason... Ideally, I'd like to >> have all of the `*-native` deps pre-installed on my build appliance's base >> filesystem, I believe this should work and I shouldn't have to bootstrap >> `tmp/work/sysroots/` and use the sysroot in `/usr` instead. >> >> More specifically, I am trying to build a container image that would >> cover the purpose of the build appliance and SDKs/ADTs, I think container >> could simplify a lot for Yocto... I haven't fully figured it out yet, still >> exploring the options, so hope the idea makes sense overall. >> >> Cheers, >> Ilya >> >
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto