From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Docu: Add LIBFOO_EXTRACT_CMDS
Date: Tue, 29 Jan 2013 11:39:42 +0100 [thread overview]
Message-ID: <5107A6EE.3060607@relinux.de> (raw)
In-Reply-To: <CAHXCMM+zLhKOZaz9YAw=s147nSOBgP-WUAOFWhjaNafbjAQ4TA@mail.gmail.com>
Am 29.01.2013 11:18, schrieb Samuel Martin:
> Hi Stephan,
>
> 2013/1/29 Stephan Hoffmann <sho@relinux.de>:
>> Signed-off-by: Stephan Hoffmann <sho@relinux.de>
>> ---
>> docs/manual/adding-packages-generic.txt | 3 +++
>> 1 files changed, 3 insertions(+), 0 deletions(-)
>>
>> diff --git a/docs/manual/adding-packages-generic.txt b/docs/manual/adding-packages-generic.txt
>> index 7b8561a..53c8c21 100644
>> --- a/docs/manual/adding-packages-generic.txt
>> +++ b/docs/manual/adding-packages-generic.txt
>> @@ -288,6 +288,9 @@ LIBFOO_VERSION = 2.32
>> Now, the variables that define what should be performed at the
>> different steps of the build process.
>>
>> +* +LIBFOO_EXTRACT_CMDS+ lists the actions to be performed to
>> + extract the package in case no standard method applies
> It could be nice to add what are the standard/supported methods
Sure. But I do not know them, I just decided to document this one
because I had to search for the information recently.
>
>> +
>> * +LIBFOO_CONFIGURE_CMDS+ lists the actions to be performed to
>> configure the package before its compilation.
>>
>> --
>> 1.7.0.4
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>
> Regards,
>
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
next prev parent reply other threads:[~2013-01-29 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 10:04 [Buildroot] [PATCH] Docu: Add LIBFOO_EXTRACT_CMDS Stephan Hoffmann
2013-01-29 10:18 ` Samuel Martin
2013-01-29 10:39 ` Stephan Hoffmann [this message]
2013-01-29 17:29 ` Arnout Vandecappelle
2013-02-16 16:22 ` Stephan Hoffmann
2013-02-16 17:35 ` Arnout Vandecappelle
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=5107A6EE.3060607@relinux.de \
--to=sho@relinux.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.