-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 17-06-10 10:18, Robert Schuster wrote: > Hi, > I am trying to make the OpenJDK recipes 'OE ready'. One hard issue I am > facing has to do with the shlibs mechanism in OE. > > In order to get OpenJDKs dependencies right its libraries and binaries > are checked for library dependencies. That is all fine and I would love > to activate that. > > Actually we have three kinds of OpenJDK builds atm: > - zero (interpreter only; but with enhancements on ARM to make it fly) > - shark (zero interpreter plus JIT based on LLVM) > - cacao (completely different runtime) > > The binary version of those recipes all bring a libjvm.so. Theoretically > a user could install all three packages (you can do that in > Debian/Ubuntu for example). However when the shlibs mechanism is > activated it puts the first built openjdk variant into a registry and > all subsequent variants get a hard runtime dependency on that package > (e.g. openjdk-shark will depend on openjdk-zero if I built zero first) > although there is no technical reason for this. > > So my question is: How can I solve this issue without resorting to: > > EXCLUDE_FROM_SHLIBS = "1" > > which I currently use and which has the bad side-effect of not having > openjdk's own dependencies. :(
Try: PRIVATE_LIBS = "libjvm.so" That will mark any libjvm.so in PACKAGES for that recipe as private and it won't show up as a shlib provider. We use this in mozilla recipes. regards, Koen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFMGe6oMkyGM64RGpERAseXAKCZvjVHnmWXiZZki2uUZ5NFtpUeAQCgkxzj e+36yRWm1gOSgT1epqOBlbM= =Cg4e -----END PGP SIGNATURE----- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
