On Wed, Oct 05, 2016 at 04:10:01PM +0000, Dinh Nguyen (dinhn) wrote:
> >>> I wonder why do we want to override default PACKAGES here. If we can 
> >>> leave that alone things would work out on its own.
> 
> I did remove the PACKAGES setting in my .bb — so all default packages were 
> built. But still having some other issue as stated in other emails.
> 
> Thanks Khem.
>   —Dinh
> 
> 
> 
> On 10/5/16, 8:34 AM, "Khem Raj" <raj.k...@gmail.com> wrote:
> 
> >I wonder why do we want to override default PACKAGES here. If we can leave
> >that alone things would work out on its own.
> >
> >On Tue, Oct 4, 2016 at 11:55 PM, Paul Eggleton
> ><paul.eggle...@linux.intel.com> wrote:
> >> On Wed, 05 Oct 2016 05:12:27 Dinh Nguyen wrote:
> >>> Thanks much Paul.
> >>>
> >>> >>>> PACKAGES = "${PN}" should work
> >>>
> >>> It solved the early error “ c-mlib listed in PACKAGES multiple times, this
> >>> leads to packaging errors” — Thanks again.
> >>>
> >>>
> >>> But running into other issue. Below is my do_install
> >>>
> >>> do_install () {
> >>>       oe_runmake all

Is that doing a compile in the install target?

-- 
Len Sorensen
-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to