Hi, Background: If you use OE to build software which includes e.g. a closed source library, but still want to others to be able to build software based on that library in a OE environment you would have to create recipes that contains a binary version of your library + headers manually. This would have to be done manually for each package, and as the development of the library continues the binary recipes will have to be manually updated to keep in sync.
Idea: Create a new bbclass that handles this automatically as much as possible. The basic idea is to: - Create a tarball of ${WORKDIR}/image/ alternatively ${WORKDIR}/packages-split/ - By parsing the "source recipe", create a "binary recipe" that uses that tarball The binary recipe should work as a drop in replacement of the source recipe. This means that the other recipes depending on the closed source software shouldn't need to be adapted to work with one or the other. I'd like feedback on whether you think the idea is feasible, and if you think it could be useful for others. And anything else you think of. Cheers, Erik Botö _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core