From: Joe MacDonald <joe@deserted.net>
To: Himanshu Pandey <pandey_himanshu80@rediffmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: Reagrding meta-networking
Date: Wed, 16 Jul 2014 10:09:40 -0400 [thread overview]
Message-ID: <20140716140937.GC13248@deserted.net> (raw)
In-Reply-To: <53b21c10.2677420a.3f91.4ec8SMTPIN_ADDED_BROKEN@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 1792 bytes --]
[Re: [OE-core] Reagrding meta-networking] On 14.07.01 (Tue 02:24) Himanshu Pandey wrote:
> So, do I have to set IMAGE_INSTALL variable in local.conf and packagename_XXXXX
> is what to be followed for the addition of each package.
That is certainly an option, though I tend to prefer
IMAGE_INSTALL_append for local.conf tweaks.
If you expect this to be a longer-term thing, you may want to consider
defining an image type for your project that includes specifically what
you want in it.
-J.
>
> Regards,
> Himanshu
>
> From: Henning Heinold <henning@itconsulting-heinold.de>
> Sent: Tue, 01 Jul 2014 01:01:52
> To: "openembedded-core@lists.openembedded.org"
> <openembedded-core@lists.openembedded.org>
> Subject: Re: [OE-core] Reagrding meta-networking
> On Mon, Jun 30, 2014 at 01:29:26PM -0000, Himanshu Pandey wrote:
> > Hi,
> >
> > Since I want dhcp and pppoe, so I downloaded the same from git and included
> meta-networking layer in bblayers.conf. This layer is getting compiled but
> somehow dhcp and pppoe are not getting included in the final image. So what I
> have to do inorder to add dhcp and pppoe in the final image.
> >
> > Please help.
> >
> > Regards,
> > Himanshu
>
> IMAGE_INSTALL += "packagename_dhcp packagname_pppoe"
>
> Be aware that recipe(bb)-name is mostly not the resulting packagename.
>
> Bye Henning
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
> [signaturel]
> Get your own FREE website, FREE domain & FREE mobile app with Know More
> Company email. >
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next parent reply other threads:[~2014-07-16 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53b21c10.2677420a.3f91.4ec8SMTPIN_ADDED_BROKEN@mx.google.com>
2014-07-16 14:09 ` Joe MacDonald [this message]
2014-07-01 2:24 Reagrding meta-networking Himanshu Pandey
-- strict thread matches above, loose matches on Subject: below --
2014-06-30 13:29 Himanshu Pandey
2014-06-30 19:31 ` Henning Heinold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140716140937.GC13248@deserted.net \
--to=joe@deserted.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=pandey_himanshu80@rediffmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox