On Tuesday 24 April 2012 15:54:17 Samuel Stirtzel wrote: > For this .bbappend it is no problem, over time the machine specific > stuff will disappear (it is only there for testing). > > But I see a problem with kde-workspace [1]. > If it should build kwin_gles then it depends on libgles, but not every > machine has libgles. > It would be no problem if virtual/libgl is used but that don't work > for machines that use virtual/egl. > > Or is there a way to build time recommend something instead of depending on > it?
You can add an RRECOMMENDS, however if the library is already dynamically linked to some other library then there will be a hard dependency on that library which via the shlibdeps code in package.bbclass will become an RDEPENDS; nothing in our system can really work around that if it's integrated into a single binary (or indivisible group of binaries). It seems to me that either the functionality needs to be split out into its own separate package which can be pulled in optionally (if possible), or more likely in this case the recipe needs to become machine-specific and be dependent on some item in MACHINE_FEATURES. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
