All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Vuille, Martin (Martin)" <vmartin@avaya.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: autotools-brokensep.bbclass not working
Date: Fri, 24 Oct 2014 09:31:35 +0100	[thread overview]
Message-ID: <1414139495.30118.2.camel@ted> (raw)
In-Reply-To: <30C2D590D16A5C46ADFE6521910377984114712F@AZ-US1EXMB03.global.avaya.com>

On Fri, 2014-10-24 at 00:08 +0000, Vuille, Martin (Martin) wrote:
> #
> set /home/platform/Workspace/dvf99_gitlab/poky/meta/conf/bitbake.conf:348
> #     "${S}"
> #
> set /home/platform/Workspace/dvf99_gitlab/poky/meta/conf/documentation.conf:77
> #     [doc] "The Build Directory. The OpenEmbedded build system places
> generated objects into the Build Directory during a recipe's build
> process."
> #
> set /home/platform/Workspace/dvf99_gitlab/poky/meta/classes/autotools-brokensep.bbclass:5
> #     "${S}"
> #   finalize ast.py:323 [finalize]
> #     "was: ${S}"
> #
> override[pn-dhcp]:set /home/platform/Workspace/dvf99_gitlab/poky/meta/conf/distro/include/seperatebuilddir.inc:105
> #     "${SEPB}"
> #   finalize override[pn-dhcp]:
> #     "${SEPB}"
> # computed:
> #   "${SEPB}"
>  
> so seperatebuilddir.inc is overriding the use of autotools-brokensep.
>  
> How can I override the override? What’s the point of
> autotools-brokensep?

The brokensep class was in its initial stages of development in 1.6 so
there are two mechanisms in action and dhcp is being controlled by
that .inc file which no longer exists in 1.7.

You can probably override it by Setting SEPB = "${S}" in the recipe (or
SEPB_pn-dhcp = "${S}" in local.conf). 

Cheers,

Richard



  reply	other threads:[~2014-10-24  8:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24  0:08 autotools-brokensep.bbclass not working Vuille, Martin (Martin)
2014-10-24  8:31 ` Richard Purdie [this message]
2014-10-24 11:21   ` Vuille, Martin (Martin)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1414139495.30118.2.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=vmartin@avaya.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.