RE: [Ltib] Same build env for different processors

[Bizhan Gholikhamseh (bgholikh)]

Hi Stuart,
If we use one ltib to configure and build two different Platforms, I
assume the source lay out in the rpm/BUILD directory for linux source
code be like this:

rpm/BUILD/linux
rpm/BUILD/linux-2.6.10
rpm/BUILD/linux-2.6.25

Where:
linux   : a soft link to active linux kernel code?
linux-2.6.20: kernel source code for our older generation powerpc
platform
linux-2.6.25: kernel source code for our newer generation powerpc
plattorm

What does sets the "linux" link to active linux kernel source code
directory?

Also the older platform and newer platform are build with the same
software pkgs (e.g dhcp) but with different revision.
It might be a risk factor to update the pkgs for the older platform, so
how we can maintain and build two sets of the same pkg with different
revisions. Do we want to create two pkg_map file one for older platform
and one for newer one?


Many thanks in advance,
Bizhan



> -----Original Message-----
> From: Stuart Hughes [mailto:address@hidden 
> Sent: Thursday, September 11, 2008 6:15 AM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: address@hidden
> Subject: RE: [Ltib] Same build env for different processors
> 
> Hi Bizhan,
> 
> Yes, you can setup an auto-builder, I have some setup.
> 
> Your best bet is to have 2 instance of LTIB, one per board 
> and then setup an autobuilder.  Take a look in bin/autobuild_ltib
> 
> I use this and run it using these cron entries:
> 
> # run an incremental build Tues-Fri at 1910  (0010 UT)
> # run a full build on Sat at 0910            (1410 UT)
> 40 18 * * 2-5 (cd /home/seh/ltib_bsps ; ./autobuild_ltib -c 
> -P config/profile/max.config 2>&1 )
> 10 09 * * 6   (cd /home/seh/ltib_bsps ; ./autobuild_ltib -f 
> -c -P config/profile/max.config 2>&1 )
> 
> 
> The 'gui' to select packages is a curse interface: ./ltib -m config
> 
> Regards, Stuart
> 
> On Thu, 2008-09-11 at 05:59 -0700, Bizhan Gholikhamseh 
> (bgholikh) wrote:
> > Hi Stuart,
> > Thanks for response.
> > We need to automate the build through scripting, so my 
> questions are:
> > 1- Could we add an option to ltib which platform to build?
> > 2- ltib has a gui interface to configure, for example to select 
> > packages, Could we automate the build configuration through 
> scripting?
> > 
> > Thanks,
> > Bizhan
> > 
> > > -----Original Message-----
> > > From: Stuart Hughes [mailto:address@hidden
> > > Sent: Thursday, September 11, 2008 5:51 AM
> > > To: Bizhan Gholikhamseh (bgholikh)
> > > Cc: address@hidden
> > > Subject: Re: [Ltib] Same build env for different processors
> > > 
> > > 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
> > > 
> > > 
> > > 
> > 
> > 
> > _______________________________________________
> > LTIB home page: http://bitshrine.org
> > 
> > Ltib mailing list
> > address@hidden
> > http://lists.nongnu.org/mailman/listinfo/ltib
> 
>