> On Jul 29, 2015, at 6:26 AM, Boszormenyi Zoltan <[email protected]> wrote: > > Hi, > > I have a customized Mesa 10.6.3 package recipe which depends on libva > to be able to build its mesa-va-driver subpackage, but libva also depends > on Mesa to support GLX. > > Previously, I simply created a libva-noglx package that builds libva > with --disable-glx that Mesa depend on and the "real" libva package can > depend on Mesa. > > But since I also have to produce an SDK image with all the *-dev packages, > creating such an initial image with bitbake fails because of a conflict > in the dependency chain: libva-dev -> mesa-dev -> libva-noglx-dev. >
since libva-noglx is sort of a bootstrap package, you could empty/delete out the content its puts into -dev packages and conflict will be gone. Other option is that you share the content of -dev package in exclusive manner between libva and libva-noglx such that they don’t package duplicate files > I have come up with the attached bbclass (based on Yocto 1.6) that > now Mesa can inherit and that patches the RDEPENDS / RRECOMMENDS > variables according to externally set variables. The comment at > the beginning of the file explains how to use it. > > This pushes the cyclic dependency to opkg which happily breaks it and > installs both libva* and *mesa* packages properly. Creating the initial > image via bitbake works now. > > Comments? > > Best regards, > Zoltán Böszörményi > > <cyclic-deps.bbclass>-- > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
