All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Kunze <thommycheck@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Some beginners problems
Date: Fri, 12 Sep 2008 12:47:20 +0200	[thread overview]
Message-ID: <48CA48B8.4060708@gmx.de> (raw)
In-Reply-To: <69E6C70090A0A14498CC98FAE5E06B6E2B3B01@hiob.intern.dresearch.de>

Sledz, Steffen wrote:
> I'm new to the OpenEmbedded system so please forgive me if my questions are FAQ or this is the wrong list.
>
> OE ist set up and I'm able to build images running on the target machines. But I'm looking for some guidance for the following problems.
>
> -------------------------------------------------
> 1. Problem
>
> I wan't to make an image (e.g. minimal-image) for atngw100 but with different linux kernel configuration (e.g. CONFIG_EXT2_FS=y). What's th right way to do this?
>
> * Just edit packages/linux/linux-2.6.24/atngw100/defconfig?
>   
Yes. But don't forget to increase the PR. Otherwise bitbake doesn't know 
that the recipe was changed and doesn't rebuild it.
> * Create an additional patch and a new bbfile (or modify existing one)?
> * Change something in local.conf?
> * Something else ... ?
>
> -------------------------------------------------
> 2. Problem
>
> I want't make a special patched dbus (in addition to the standard installation). What's the best way here?
>
> * Create an own package just using the same source archives?
> * Add a patch file to the existing package and modify the bbfile?
> * Something else ... ?
>   
Depends if you need the original dbus package too or not. If you need it 
create a new package and if not just add a patch to the old one
(and don't forget to increase PR).
> -------------------------------------------------
>
> It would be nice to separate the changes not mentioned to become upstreamed from the org.openembedded.dev git tree.
>   
The most effective way is to open a bug report for your patches. (and 
poke people on irc if nobody reacts)

Regards,
Thomas




  parent reply	other threads:[~2008-09-12 10:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12 10:26 Some beginners problems Sledz, Steffen
2008-09-12 10:46 ` Javi Roman
2008-09-12 10:47 ` Thomas Kunze [this message]
2008-09-12 11:05   ` Sledz, Steffen
2008-09-12 11:26     ` Thomas Kunze
2008-09-12 13:07       ` Sledz, Steffen
2008-09-12 13:56         ` Thomas Kunze
2008-09-12 19:01     ` Rich Pixley

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=48CA48B8.4060708@gmx.de \
    --to=thommycheck@gmx.de \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.