Some beginners problems

Some beginners problems

[Sledz, Steffen]

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?
* 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 ... ?

-------------------------------------------------

It would be nice to separate the changes not mentioned to become upstreamed from the org.openembedded.dev git tree.

Thanx for hints on this,
Steffen

Re: Some beginners problems

[Javi Roman]

On Fri, Sep 12, 2008 at 12:26 PM, Sledz, Steffen <sledz@dresearch.de> wrote:
>
> It would be nice to separate the changes not mentioned to become upstreamed from the org.openembedded.dev git tree.
>


Bitbake collections:

http://www.kernel-labs.org/files/openembedded-guide/openembedded-guide-6.html

-- 
Javi Roman

Re: Some beginners problems

[Thomas Kunze]

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

Re: Some beginners problems

[Sledz, Steffen]

> > 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.

The change is not a bug fix or something like this. It's just a variant and not mentioned to become committed. So if i increase PR and someone else fixes a bug and increases PR too and I pull this fixes from git I have a conflict.  :(

Regards,
Steffen

Re: Some beginners problems

[Thomas Kunze]

Sledz, Steffen wrote:
>>> 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.
>>     
>
> The change is not a bug fix or something like this. It's just a variant and not mentioned to become committed. So if i increase PR and someone else fixes a bug and increases PR too and I pull this fixes from git I have a conflict.  :(
>   
Yes but you will always have this problem with local changes and it 
shouldn't be too hard to resolve such conflicts.

Regards,
Thomas

Re: Some beginners problems

[Sledz, Steffen]

> >>> 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.
> >>     
> >
> > The change is not a bug fix or something like this. It's 
> > just a variant and not mentioned to become committed. So if i 
> > increase PR and someone else fixes a bug and increases PR too 
> > and I pull this fixes from git I have a conflict.  :(
> >   
> Yes but you will always have this problem with local changes and it 
> shouldn't be too hard to resolve such conflicts.

Is it possible (and is it a good idea) to create a new distro (or a new machine) for such a purpose?

Or is it possible to set parameters in local.conf which are available in the package bbfile for evaluation?

Steffen

Re: Some beginners problems

[Thomas Kunze]

Sledz, Steffen wrote:
>>>>> 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.
>>>>     
>>>>         
>>> The change is not a bug fix or something like this. It's 
>>> just a variant and not mentioned to become committed. So if i 
>>> increase PR and someone else fixes a bug and increases PR too 
>>> and I pull this fixes from git I have a conflict.  :(
>>>   
>>>       
>> Yes but you will always have this problem with local changes and it 
>> shouldn't be too hard to resolve such conflicts.
>>     
>
> Is it possible (and is it a good idea) to create a new distro (or a new machine) for such a purpose?
>
>   
In oe a distro decides which versions of packages to use or which 
providers to use (qtopia-x11 vs. qtopia-framebuffer for example.)
A machine decides which architecture/kernel etc you have. I don't see 
how you could abuse that to guard against conflicts between
local changes and upstream changes.
> Or is it possible to set parameters in local.conf which are available in the package bbfile for evaluation?
>   
This is possible but doesn't solve the problem imo.
You may want to look at bitbake-collections:
http://bec-systems.com/oe/html/special_bitbake_collections.html
http://www.pokylinux.org/doc/poky-handbook.html#usingpoky-changes-collections
as Javi Roman suggested. Maybe this is what you want. But I would push 
everything upstream
that is pushable and fix conflicts for all other stuff as necessary.

Re: Some beginners problems

[Rich Pixley]

Sledz, Steffen wrote:
>>> 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.
>>     
>
> The change is not a bug fix or something like this. It's just a variant and not mentioned to become committed. So if i increase PR and someone else fixes a bug and increases PR too and I pull this fixes from git I have a conflict.  :(
Try using the  debian name branching approach.

"r6" -> "r6palm1"

That way "r7" will take precedence and yet "r6palm1" is different and 
lexically later than "r6".

--rich