From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] LIBFOO_SITE in .mk file
Date: Tue, 29 Nov 2011 08:31:31 +0100 [thread overview]
Message-ID: <20111129083131.77889c21@skate> (raw)
In-Reply-To: <002001ccade8$e03e9f00$0400a8c0@dspcgrnzks9p98>
Le Mon, 28 Nov 2011 10:14:58 -0600,
"Jeff Krasky" <jeff.krasky@dspcg.com> a ?crit :
> Because I don't want just the default source of EtherCAT built into
> the Linux image. Lets say I want to modify something in the examples
> directory of EtherCAT. For instance, I had to modify the sample code
> and rebuild. So what I want is this "rebuilt" version of EtherCAT,
> with customized example code, as part of the Linux image. If I point
> at the EtherCAT website, that won't be the correct version. The
> EtherCAT examples development will occur on the same machine that
> Buildroot is on, hence why I like the local filesystem solution.
I am not sure what you are trying to achieve here. If the upstream
package has issues that need to be fixed, then you can put patches in
the package/ethercat/ directory, which Buildroot will apply after
extracting the upstream tarball.
In addition, if you want to do quick development on EtherCAT, you can
also use the new "source override" feature that is part of the
upcoming Buildroot 2011.11. With this feature, you can tell Buildroot
to use a local directory for the source code instead of an upstream
tarball without changing the package .mk file itself, so that the .mk
file remains usable for upstreaming in Buildroot.
To do this, just create a local.mk file in the top directory of
Buildroot with the following contents :
ETHERCAT_OVERRIDE_SRCDIR = /my/local/place/
and then reference this local.mk file in the BR2_PACKAGE_OVERRIDE_FILE
configuration option.
If you really want to use a local directory directly in the package .mk
file, then you can use
ETHERCAT_SITE = /my/local/place
ETHERCAT_SITE_METHOD = local
But this is not great as it won't allow you to submit Ethercat to the
Buildroot developers, and will also force all users (including in your
company) to have Ethercat available at this location.
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:[~2011-11-29 7:31 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 20:51 [Buildroot] equivalent of a 'make modules' Jeff Krasky
2011-11-22 22:04 ` Thomas Petazzoni
2011-11-22 22:11 ` Jeff Krasky
2011-11-22 22:29 ` Thomas Petazzoni
2011-11-22 22:35 ` Jeff Krasky
2011-11-23 7:19 ` Thomas De Schampheleire
2011-11-23 21:38 ` [Buildroot] LIBFOO_SITE in .mk file Jeff Krasky
2011-11-23 22:43 ` Jeff Krasky
2011-11-24 8:15 ` Thomas De Schampheleire
2011-11-28 15:07 ` Jeff Krasky
2011-11-28 15:11 ` Thomas Petazzoni
2011-11-28 15:19 ` Jeff Krasky
2011-11-28 15:54 ` Thomas Petazzoni
2011-11-28 16:14 ` Jeff Krasky
2011-11-28 17:39 ` Michael S. Zick
2011-11-28 18:50 ` Jeff Krasky
2011-11-28 19:24 ` Michael S. Zick
2011-11-28 19:33 ` Jeff Krasky
2011-11-28 21:14 ` Jeff Krasky
2011-11-28 22:15 ` Jeff Krasky
2011-11-29 7:37 ` Thomas Petazzoni
2011-11-29 14:28 ` Jeff Krasky
2011-11-29 14:36 ` Thomas Petazzoni
2011-11-29 14:43 ` Jeff Krasky
2011-11-29 21:43 ` Jeff Krasky
2011-11-29 22:42 ` Jeff Krasky
2011-11-30 15:59 ` Jeff Krasky
2011-11-30 16:04 ` Thomas Petazzoni
2011-11-30 16:20 ` Jeff Krasky
2011-11-30 16:33 ` Thomas Petazzoni
2011-11-30 16:38 ` Jeff Krasky
2011-11-30 16:49 ` Michael S. Zick
2011-11-30 16:57 ` Jeff Krasky
2011-11-30 17:08 ` Michael S. Zick
2011-11-30 17:48 ` Thomas De Schampheleire
2011-11-30 17:58 ` Thomas Petazzoni
2011-11-30 18:11 ` Jeff Krasky
2011-11-30 19:31 ` Jeff Krasky
2011-11-30 19:44 ` Thomas De Schampheleire
2011-11-30 20:01 ` Jeff Krasky
2011-11-30 22:21 ` Thomas Petazzoni
[not found] ` <001201ccafb0$4b5e06e0$0400a8c0@dspcgrnzks9p98>
2011-11-30 22:49 ` Thomas Petazzoni
2011-11-30 22:54 ` Jeff Krasky
2011-12-01 8:11 ` Thomas Petazzoni
2011-12-01 14:58 ` Jeff Krasky
2011-12-01 15:03 ` Michael S. Zick
2011-12-01 15:55 ` Jeff Krasky
2011-12-01 16:16 ` Jeff Krasky
2011-12-01 16:33 ` Jeff Krasky
2011-12-01 16:52 ` Michael S. Zick
2011-12-01 18:15 ` Jeff Krasky
2011-12-01 22:56 ` Jeff Krasky
2011-12-02 7:50 ` Thomas De Schampheleire
2011-12-02 8:50 ` Thomas Petazzoni
2011-12-02 13:33 ` Michael S. Zick
2011-12-02 15:57 ` Jeff Krasky
2011-12-02 16:09 ` Quotient Remainder
2011-12-02 16:51 ` [Buildroot] Kernel panic - not syncing: Attempted to kill init! Jeff Krasky
2011-12-02 16:59 ` Jeff Krasky
2011-12-02 17:33 ` Tim Judd
2011-12-02 18:02 ` Jeff Krasky
2011-12-02 18:21 ` Aleksander Dutkowski
2011-12-02 18:30 ` Jeff Krasky
2011-12-03 0:25 ` Aleksander Dutkowski
2011-12-03 8:25 ` [Buildroot] Device files and Buildroot Thomas Petazzoni
2011-12-03 12:53 ` Trevor Woerner
2011-12-03 18:40 ` Thomas Petazzoni
2011-12-05 10:54 ` Aleksander Dutkowski
2011-12-08 21:30 ` Felipe Contreras
2011-12-08 23:49 ` Michael S. Zick
2011-12-09 18:49 ` Thomas Petazzoni
2011-12-02 18:31 ` [Buildroot] Kernel panic - not syncing: Attempted to kill init! Tim Judd
2011-12-02 18:24 ` Tim Judd
2011-11-29 14:54 ` [Buildroot] LIBFOO_SITE in .mk file Michael S. Zick
2011-11-29 7:35 ` Thomas Petazzoni
2011-11-28 18:55 ` Quotient Remainder
2011-11-28 19:02 ` Jeff Krasky
2011-11-29 7:31 ` Thomas Petazzoni [this message]
2011-11-23 8:25 ` [Buildroot] equivalent of a 'make modules' Thomas Petazzoni
2011-11-23 14:17 ` Jeff Krasky
2011-11-23 14:23 ` 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=20111129083131.77889c21@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