Re: [Ltib] building multiple platforms, rpm cache

[Stuart Hughes]

Hi Mike,

I'm not sure I can answer fully, but I can give a bit of background.

The --noclobber was a fairly recent thing contributed by Peter Barada to
allow the rpm/BUILD staging area to be deliberately wiped out even if it
had unpacked source (if I recall correctly).

As far as autobuild_ltib goes, this is what I used for the nightly
autobuilder, and indeed each platform in it's own directory.  The idea
is that Monday-Friday I just do and update/build, and once a week I do a
build from scratch (which takes a lot longer).

As far as the rpm caching goes, the original intention was to allow you
to change toolchains and re-build and then switch back (for example
glibc vs uClibc).  As designed, it did not consider the platform changing.

What may be happening in your case is that the default configuration
you're using in the preconfig does match the .config that was used when
you actually built the RPMs.  Remember that when you push a defconfig
into mconf/conf it can get changed as the config points are
re-evaluated.  So it's worth checking why the switch thinks the
pre-builds are no good. Take a look at rpm/BUILD/_cache_rpm_dir/.config
it shows you what config points must match in order to use these rpms
for the current BSP config.

Regards, Stuart

On 26/02/13 20:30, Mike Goins wrote:
> I am trying to build specific configurations in ltib under continous
> integration system using the command:
> ./ltib --batch --clobber --preconfig config/platform/iolite/defconfig-Iolite
> (I know that platform does not exist in ltib yet, but bear with me)
> 
> Then I may have to build for another platform, so I argue another
> platform after that:
> ./ltib --batch --clobber --preconfig config/platform/mpc8377/defconfig-8377
> 
> The first step I see that it removes all the rpms, caches those in a
> directory, looks a time-stamp, and builds the new platform.
> 
> So far so good, it seems.  But when I switch back to the original platform:
> ./ltib --batch --clobber --preconfig config/platform/iolite/defconfig-Iolite
> 
> The rpm removal does not take place and the cached rpms are not used.
> I can't quire figure out what I am missing.  Is --preconfig the
> correct argument for this?
> 
> I looked at bin/autobuild_ltib to see how it does it, but it appear
> that it expects a separate copy of ltib for each platform config.  I
> just can't find a good way to integrate that method into a ci system.
> 
> Thanks
> 
> _______________________________________________
> LTIB home page: http://ltib.org
> 
> Ltib mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/ltib
>