From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] change default location for local.mk to $(CONFIG_DIR)
Date: Fri, 15 Mar 2013 12:46:24 +0100 [thread overview]
Message-ID: <20130315124624.60f408f9@skate> (raw)
In-Reply-To: <CAAXf6LWABPZcHrftL3LFLVB4ApLdS19-kRME101DG+9rfrfK4Q@mail.gmail.com>
Dear Thomas De Schampheleire,
On Tue, 12 Mar 2013 09:26:51 +0100, Thomas De Schampheleire wrote:
> However, unlike other config files, I still think of local.mk as a
> local hack used by an individual developer, and not something you
> would put under version control, neither in git nor in
> project-specific patches.
I would say it depends. We may imagine that some people use git
submodules to achieve something like this:
+ project
--+ buildroot
--+ linux
--+ uboot
--+ application
with a suitable local.mk, under version control, that tells Buildroot
to look for the kernel source code in $(TOPDIR)/../linux, U-Boot
source code in $(TOPDIR)/../uboot, etc.
(in the above, buildroot, linux, uboot and application are separate Git
repositories that are put together into a global project Git
repositories using git submodules).
But J?r?my's patch doesn't prevent from doing that, since it just
changes the default value.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-03-15 11:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 10:49 [Buildroot] [PATCH] change default location for local.mk to $(CONFIG_DIR) Jérémy Rosen
2013-03-11 21:26 ` Thomas Petazzoni
2013-03-12 8:12 ` Jeremy Rosen
2013-03-12 21:47 ` Arnout Vandecappelle
2013-03-14 8:37 ` Jeremy Rosen
2013-03-18 6:46 ` Arnout Vandecappelle
2013-03-18 8:10 ` Jeremy Rosen
2013-03-12 8:26 ` Thomas De Schampheleire
2013-03-15 11:46 ` Thomas Petazzoni [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=20130315124624.60f408f9@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