best practice for different projects on the same board

best practice for different projects on the same board

[Jaap de Jong]

Hi All,
I'm wondering what the best practice would be in the following situation.
We have a board that is going to be used in several projects.
The set of basic packages is the same but every project might have some 
minor and perhaps sometimes major differences in f.i. config files.
I don't want to make a copy of the base project for every upcoming new 
project. I would really like to handle with the differences only.
What is the best approach for this?
Thanks!
Jaap

Re: best practice for different projects on the same board

[Marcin Juszkiewicz]

W dniu 25.01.2013 12:19, Jaap de Jong pisze:
> Hi All,
> I'm wondering what the best practice would be in the following situation.
> We have a board that is going to be used in several projects.
> The set of basic packages is the same but every project might have some
> minor and perhaps sometimes major differences in f.i. config files.
> I don't want to make a copy of the base project for every upcoming new
> project. I would really like to handle with the differences only.
> What is the best approach for this?

Create conf/machine/board1.conf and describe everything there. Set
kernel etc. Then create conf/machine/board2.conf which will "require
conf/machine/board1.conf" and then change what is needed.

This way you have two values of MACHINE variable which you can use in
all recipes you need to modify for boards. And you are able to do builds
with one TMPDIR so most of builds will be reused.