All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Add a waf bitbake class. (Koen Kooi)
Date: Mon, 21 Jun 2010 13:39:51 -0700	[thread overview]
Message-ID: <4C1FCE17.6010409@mentor.com> (raw)
In-Reply-To: <113134CF306E8E4CACC27BE5937261B2092DE57AC9@AUSX7MCPS303.AMER.DELL.COM>

Sean_Hudson@Dell.com wrote:
> On 18-06-10 21:58, Koen Kooi <k.kooi@student.utwente.nl> wrote:
> ------------------------------
>> On 18-06-10 21:58, Sean_Hudson@Dell.com wrote:
>>> Hi All,
>>>
>>>   We are using waf for some of our modules and decided to add a class to make it easier to write recipes.
>> Why is there still a staging method in there? Those have been deprecated
>> for months now.
> 
> Thanks for taking the time to reply.  To answer your question, the waf class was cloned from the autotools.bbclass, so the staging stuff came from there.  Is there a better way to handle the staging?
> 
> It's a fairly trivial class, but I'm interested to hear if anyone had any additional thoughts on ways to improve the class?

Koen's point is that for a long time now do_stage has been set as legacy 
and 'do_install' should instead set things up such that a package can 
then be installed into the sysroots/ directory and reused.  Like 
autotools.bbclass does today :)

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2010-06-21 20:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21 19:57 [PATCH] Add a waf bitbake class. (Koen Kooi) Sean_Hudson
2010-06-21 20:39 ` Tom Rini [this message]
2010-06-21 20:58   ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2010-06-22 15:06 Sean_Hudson
     [not found] <AANLkTilMpRi2oaQWKO7BcgkhZeVojh7GA_-5_3SDG1A4@mail.gmail.com>
     [not found] ` <113134CF306E8E4CACC27BE5937261B20931AA0A82@AUSX7MCPS303.AMER.DELL.COM>
     [not found]   ` <AANLkTikN2OKgSvwW4vQ4h5tegaxdkDmYZpmMK7Fy+a1g@mail.gmail.com>
     [not found]     ` <113134CF306E8E4CACC27BE5937261B20931FB4CF0@AUSX7MCPS303.AMER.DELL.COM>
2010-07-30 21:41       ` AJ ONeal

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=4C1FCE17.6010409@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-devel@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.