From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFCv2] Per-package out-of-tree build
Date: Mon, 15 Apr 2013 09:36:10 +0200 [thread overview]
Message-ID: <20130415093610.41836fc2@skate> (raw)
In-Reply-To: <CALR4fELqcE9HsOp+CoPzv-O0UrcH-iPii1CFVOr0z8zAb87tSg@mail.gmail.com>
Dear Diego Iastrubni,
On Sun, 14 Apr 2013 08:55:01 +0300, Diego Iastrubni wrote:
> > * A <pkg>_SUPPORTS_OUT_OF_TREE variable defines whether the package
> > supports out of tree build or not. By default, it's set to NO, in
> > which case the package source code is rsynced from its source
> > directory to the build directory at the beginning of the
> > configure step. It is set to YES by both the autotools and cmake
> > package infrastructures (which have been modified to do out of tree
> > build), and by some packages that use the generic infrastructure but
> > nonetheless support out of tree build.
> Does buildroot support also qmake? qmake has also out of source build
> support.
We don't have a specific qmake infrastructure, so for now the packages
that rely on the qmake build system use the 'generic-package' Buildroot
package infrastructure. It is therefore up to them to support
out-of-tree build.
If qmake packages become more widespread, it might be useful to add a
specific infrastructure for them. For now, I feel their number is a bit
limited to do so.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-04-15 7:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 18:54 [Buildroot] [RFCv2] Per-package out-of-tree build Thomas Petazzoni
2013-04-14 5:55 ` Diego Iastrubni
2013-04-15 7:36 ` Thomas Petazzoni [this message]
2013-04-16 23:03 ` Cam Hutchison
2013-04-17 7:51 ` Thomas Petazzoni
2013-04-17 16:33 ` Arnout Vandecappelle
2013-04-18 7:26 ` Thomas Petazzoni
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=20130415093610.41836fc2@skate \
--to=thomas.petazzoni@free-electrons.com \
--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