Re: [Ltib] Same build env for different processors

[Stuart Hughes]

Hi Bizhan,

If they're different boards physically then I think it's best to create
2 separate directorys:

config/platform/xxx8378
config/platform/xxx8541

If your kernel sources are different, then you just need 2 kernel
specfiles.  If it's just the configuration of the kernel, then you just
need 2 different kernel config files.

The kernel spec files can go into dist/lfs-5.1/kernel if they could be
common, or otherwise placed them in config/platform/<target>

The config files should go into config/platform/<target>

It is also possible to have a single config/platform/<target> serving
more than one board, but generally I prefer to reserve this behaviour
for different variations of the same board (setups).  The main reason is
that it's easier to independently update/release as/if the hardware for
the board gets changed.

Regards, Stuart

On Thu, 2008-09-11 at 05:02 -0700, Bizhan Gholikhamseh (bgholikh) wrote:
> HI All,
> In our environment we have two different platforms each have different
> Freescale processor (8541 and 8378). We run the same type of the
> application on both platform. So the same source code is shared
> between both platforms. We are planning to  use MULTIlibrary compiler
> from sourcery which supports both CPUs (or may be freescale provide
> one to us). 
> It is best for our developers to have one build env that could compile
> both platforms, (the only differences would be kernel package).
> Is this possible by using ltib?
>  
>  
> Regards,
> Bizhan