All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-source: exlude from world
Date: Thu, 27 Aug 2015 23:17:16 -0400	[thread overview]
Message-ID: <55DFD2BC.7070405@windriver.com> (raw)
In-Reply-To: <1440731387-19733-1-git-send-email-Randy.MacLeod@windriver.com>


I've sent the parent email to fix
$ bitbake -c <stage> world.
I've confirmed that my change works for:
$ bitbake -c configure world

I wasn't sure if I should leave gcc-source as
is or change it to be similar to kernel-devsrc
because meta/recipes-devtools/gcc/gcc-source.inc does:

deltask do_configure
deltask do_compile
deltask do_package
...

whereas meta/recipes-kernel/linux/kernel-devsrc.bb does:
# There's nothing to do here, except install the source where we can 
package it
do_fetch[noexec] = "1"
do_unpack[noexec] = "1"
do_patch[noexec] = "1"
...

The kernel-devsrc approach doesn't break world builds
but it's probably slightly less efficient.

Also do people care about consistency in naming:
   gcc-source.inc vs
   kernel-devsrc.bb
? There are only two such 'source' packages so it's not a big deal.

../Randy


On 2015-08-27 11:09 PM, Randy MacLeod wrote:
> Exclude all versions of gcc-source from world builds so that:
>     bitbake -c <stage> world
> will work. gcc-source deletes most bitbake build stages
> since it is a source-only package.
>
> Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
> ---
>   meta/recipes-devtools/gcc/gcc-source_4.8.bb | 2 ++
>   meta/recipes-devtools/gcc/gcc-source_4.9.bb | 2 ++
>   meta/recipes-devtools/gcc/gcc-source_5.2.bb | 2 ++
>   3 files changed, 6 insertions(+)
>
> diff --git a/meta/recipes-devtools/gcc/gcc-source_4.8.bb b/meta/recipes-devtools/gcc/gcc-source_4.8.bb
> index 234b82e..b890fa3 100644
> --- a/meta/recipes-devtools/gcc/gcc-source_4.8.bb
> +++ b/meta/recipes-devtools/gcc/gcc-source_4.8.bb
> @@ -1,2 +1,4 @@
>   require recipes-devtools/gcc/gcc-${PV}.inc
>   require recipes-devtools/gcc/gcc-source.inc
> +
> +EXCLUDE_FROM_WORLD = "1"
> diff --git a/meta/recipes-devtools/gcc/gcc-source_4.9.bb b/meta/recipes-devtools/gcc/gcc-source_4.9.bb
> index 234b82e..b890fa3 100644
> --- a/meta/recipes-devtools/gcc/gcc-source_4.9.bb
> +++ b/meta/recipes-devtools/gcc/gcc-source_4.9.bb
> @@ -1,2 +1,4 @@
>   require recipes-devtools/gcc/gcc-${PV}.inc
>   require recipes-devtools/gcc/gcc-source.inc
> +
> +EXCLUDE_FROM_WORLD = "1"
> diff --git a/meta/recipes-devtools/gcc/gcc-source_5.2.bb b/meta/recipes-devtools/gcc/gcc-source_5.2.bb
> index 234b82e..b890fa3 100644
> --- a/meta/recipes-devtools/gcc/gcc-source_5.2.bb
> +++ b/meta/recipes-devtools/gcc/gcc-source_5.2.bb
> @@ -1,2 +1,4 @@
>   require recipes-devtools/gcc/gcc-${PV}.inc
>   require recipes-devtools/gcc/gcc-source.inc
> +
> +EXCLUDE_FROM_WORLD = "1"
>


-- 
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON, 
Canada, K2K 2W5


  parent reply	other threads:[~2015-08-28  3:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28  3:09 [PATCH] gcc-source: exlude from world Randy MacLeod
2015-08-28  3:14 ` Saul Wold
2015-08-28  3:17 ` Randy MacLeod [this message]
2015-08-28  3:27   ` Khem Raj
2015-08-28 15:45     ` Randy MacLeod
2015-08-28 16:19       ` Khem Raj

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=55DFD2BC.7070405@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=openembedded-core@lists.openembedded.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.