From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3] spidev_test: new package
Date: Sat, 25 Oct 2014 10:55:32 +0200 [thread overview]
Message-ID: <20141025105532.26c151dc@free-electrons.com> (raw)
In-Reply-To: <1414169770-18234-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Fri, 24 Oct 2014 13:56:10 -0300, Gustavo Zacarias wrote:
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> package/Config.in | 1 +
> package/spidev_test/Config.in | 17 +++++++++++++++++
> package/spidev_test/spidev_test.mk | 32 ++++++++++++++++++++++++++++++++
> 3 files changed, 50 insertions(+)
> create mode 100644 package/spidev_test/Config.in
> create mode 100644 package/spidev_test/spidev_test.mk
Applied, after doing a small change, see below.
> +# Downloaded file is C source
> +SPIDEV_TEST_EXTRACT_CMDS =
> +
> +define SPIDEV_TEST_BUILD_CMDS
> + $(TARGET_MAKE_ENV) $(TARGET_CC) $(TARGET_CFLAGS) -x c \
> + -o $(@D)/spidev_test $(BR2_DL_DIR)/$(SPIDEV_TEST_SOURCE)
> +endef
I've chosen to actually implement SPIDEV_TEST_EXTRACT_CMDS by copying
the source file from $(BR2_DL_DIR) to $(@D). This allows to have
patches applied on spidev_test, or to do some manual tweaks (for
testing) in the build directory and rebuild the package. Consequently,
I've dropped the "-x c" option since the file is now copied with a .c
extension.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-10-25 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 16:56 [Buildroot] [PATCHv3] spidev_test: new package Gustavo Zacarias
2014-10-25 8:55 ` 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=20141025105532.26c151dc@free-electrons.com \
--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