From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] core: allow check-host-cmake.sh to check several candidates
Date: Fri, 5 May 2017 19:34:46 -0300 (BRT) [thread overview]
Message-ID: <829990645.21765498.1494023686203.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <20170505210703.GA3001@scaer>
> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
> To: "Carlos Santos" <casantos@datacom.ind.br>
> Cc: buildroot at buildroot.org
> Sent: Friday, May 5, 2017 6:07:03 PM
> Subject: Re: [Buildroot] [PATCH 1/3] core: allow check-host-cmake.sh to check several candidates
>> --- a/support/dependencies/check-host-cmake.sh
>> +++ b/support/dependencies/check-host-cmake.sh
>> @@ -1,39 +1,41 @@
>> #!/bin/sh
>>
>> -candidate="${1}"
>> -version_min="${2}"
>> +eval 'version_min="${'${#}'}"'
>
> It took me a moment to understand what this was doing (and I am known
> for being a shell fanboy!).
>
> Just revert the order options are passed: version first, then
> candidates. This will allow you to get rid of this weird construct.
>
> version_min="${1}"
> shift # Keep only candidates
I did it that way because all invocations of the "suitable-host-package"
macro pass the candidate name as the first argument to the script but I
must admit that the script lost some readability.
>
> So that you can do...
>
>> major_min="${version_min%.*}"
>> minor_min="${version_min#*.}"
> [--SNIP--]
>> +while [ $# -gt 1 ]; do
>> + cmake=`which "${1}" 2>/dev/null`
>
> for cmake; do
> cmake=`which "${cmake}" 2>/dev/null`
>
>> +
>> + if [ -x "${cmake}" ]; then
>
> Please use an early cut:
>
> [ -x "${cmake}" ] || continue
>
> which allows you to gain a indentation level below.
Ok.
--
Carlos Santos (Casantos) - DATACOM, P&D
?The greatest triumph that modern PR can offer is the transcendent
success of having your words and actions judged by your reputation,
rather than the other way about.? ? Christopher Hitchens
next prev parent reply other threads:[~2017-05-05 22:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 20:30 [Buildroot] [PATCH 0/3] Support a list of "cmake" candidates Carlos Santos
2017-05-05 20:30 ` [Buildroot] [PATCH 1/3] core: allow check-host-cmake.sh to check several candidates Carlos Santos
2017-05-05 21:07 ` Yann E. MORIN
2017-05-05 22:34 ` Carlos Santos [this message]
2017-05-05 23:19 ` Carlos Santos
2017-05-06 8:16 ` Yann E. MORIN
2017-05-05 20:30 ` [Buildroot] [PATCH 2/3] core: allow having a list of "cmake" candidates Carlos Santos
2017-05-05 21:09 ` Yann E. MORIN
2017-05-05 22:43 ` Carlos Santos
2017-05-06 8:17 ` Yann E. MORIN
2017-05-05 20:30 ` [Buildroot] [PATCH 3/3] core: add "cmake3" to the list of cmake candidates Carlos Santos
2017-05-05 21:10 ` Yann E. MORIN
2017-05-06 8:18 ` Yann E. MORIN
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=829990645.21765498.1494023686203.JavaMail.zimbra@datacom.ind.br \
--to=casantos@datacom.ind.br \
--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.