[yocto] Detecting missing build dependencies

Martin Jansa martin.jansa at gmail.com
Wed Jan 27 06:59:46 PST 2016


On Wed, Jan 27, 2016 at 03:45:30PM +0100, Ulf Magnusson wrote:
> Hello,
> 
> If a recipe has a missing build dependency that the sysroot just
> happens to contain anyway from an earlier build, then the build will
> succeed only to fail later when the sysroot no longer has the build
> dependency. We want to avoid that, so we're looking for ways to
> automatically check for unspecified build dependencies.
> 
> The only method I know of at the moment is to remove or rename tmp/ so
> that the build uses a fresh sysroot and then trying to rebuild the
> recipe. Is there something nicer? I think I remember reading about a
> script for testing for missing build dependencies, but I might be
> misremembering.

See openembedded-core/scripts/test-dependencies.sh but it basically
automates rebuilding recipes after removing TMPDIR, but also it detects
autodetected dependencies.

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20160127/5e659755/attachment.pgp>


More information about the yocto mailing list