Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] gstreamer1-imx: new package
Date: Mon, 03 Mar 2014 23:07:07 -0300	[thread overview]
Message-ID: <5315354B.5070805@zacarias.com.ar> (raw)
In-Reply-To: <20140303205342.GF3380@free.fr>

On 03/03/2014 05:53 PM, Yann E. MORIN wrote:

Hi all.

>> +define GSTREAMER1_IMX_BUILD_CMDS
>> +       (cd $(@D); ./waf build -j $(PARALLEL_JOBS))
> 
> Waf is known to have lotta isue when cross-compiling. Is that really
> working correctly?
> 
> Fortunately, this is only supposed to ever be run for an ARM target, so
> maybe they were not really concerned of making it really cross-compile
> friendly, as long as it works in these specific comditions.

Waf makes no distinction between host and target tools.
That being said if the wscript doesn't want to execute cross-tests
(intended for the target) or need to build special host tools as part of
the build process, then it's possible it works.
Regards.

      reply	other threads:[~2014-03-04  2:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 21:24 [Buildroot] [PATCH v2] gstreamer1-imx: new package Peter Seiderer
2014-03-03 20:53 ` Yann E. MORIN
2014-03-04  2:07   ` Gustavo Zacarias [this message]

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=5315354B.5070805@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox