Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Compiler errors pointing in BUILD_DIR when using OVERRIDE_SRCDIR
Date: Wed, 21 Oct 2015 22:26:55 +0200	[thread overview]
Message-ID: <5627F50F.2060201@mind.be> (raw)
In-Reply-To: <CAKMA=Nbi2xkzg77St8PAbmQ79WKCeFw3KWDTuFkRYNR0pULzeQ@mail.gmail.com>

On 21-10-15 15:16, Julien Rosener wrote:
> Hi,
> 
> In my company we are using buildroot for package development.
> According to the buildroot documentation we are using the
> <pkg>_OVERRIDE_SRCDIR mechanism.
> 
> It works great when the build is going well. However when there is a
> compiler error/warning the issue is referring files in
> output/build/<pkg> (because the source code was rsynced at this
> location to be built).
>>From a developer point of view (which is editing source code in
> <pkg>_OVERRIDE_SRCDIR), it is difficult to work because if you jump on
> the error, it does not jump on the source file which is edited. This
> behavior generates mistake.
> 
> What do you think about that (limitation, bug ?) ? Do you think it
> would be possible to improve it ?

 Some people (e.g., me :-) use the same source directory to build several
configurations in separate output directories. In that case, building in the
source directory wouldn't work...

 If the package in question supports out-of-tree building (like e.g. the kernel
or most autotools-based packages), it would be possible that we don't copy the
sources but instead just build out-of-tree in the build directory. Thomas
Petazzoni posted a patch series to that effect about two and a half years ago,
but that series was incomplete and never got applied. So you could take it over,
perhaps improve and repost it. See [1], but mind [2]. Also, Thomas may have a
more recent version of the series.

 Regards,
 Arnout

[1] http://lists.busybox.net/pipermail/buildroot/2013-April/070573.html
[2] http://lists.busybox.net/pipermail/buildroot/2013-May/072556.html


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2015-10-21 20:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 13:16 [Buildroot] Compiler errors pointing in BUILD_DIR when using OVERRIDE_SRCDIR Julien Rosener
2015-10-21 20:26 ` Arnout Vandecappelle [this message]
2015-10-21 20:51   ` Thomas Petazzoni
2015-10-21 21:35     ` Julien Rosener

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=5627F50F.2060201@mind.be \
    --to=arnout@mind.be \
    --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