On Thu, Oct 11, 2012 at 12:53:21PM +0200, Enrico wrote: > On Thu, Oct 11, 2012 at 10:17 AM, Nicolas Dechesne <[email protected]> wrote: > > On Thu, Oct 11, 2012 at 1:40 AM, Enrico Butera <[email protected]> > > wrote: > > libdce tree contains both the linux side lib, and the ducati side DCE > > code for now (which can't be rebuild completely for now, as we aren't > > releasing all the bits/pieces for ducati side). > > > > we have been discussing about spliting this tree into 2 for better > > clarity, so that might happen at some point.. > > I learned it the hard way some time ago, at my first attempt to add > gst-ducati!
Enrico, You'd be surprised, but I still keep your first attempt patches in my queue, waiting for a better moment to integrate them! :) Now, that we have the corresponding TI team assisting us, we should be able to get it done quickly! > >> +require ../includes/ti-paths.inc > >> +require ../includes/ti-staging.inc > > > > what is this for? > > some copy/paste leftovers :D > will delete them Yeah, those are kind of specific to the way other teams package their components and are not really needed here. > >> +inherit autotools > >> + > >> +DEPENDS = "libdrm" > >> +RDEPENDS = "libdrm ti-firmware-ipu-dce" > > > > i would hope that libdrm is not needed in RDEPENDS, as it should be > > handled automagically by shlibdeps. > > I really don't know, if you are sure about that i will just remove it. Yes, he is correct here - if you have a build dependency in DEPENDS which links against a library, you automatically get that run-time dependency in RDEPENDS, so no need to list it explicitly. -- Denys _______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
