From: L A Walsh <lkml@tlinx.org>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: RFD: --enable-bindir-path ?
Date: Thu, 06 Sep 2018 19:52:27 -0700 [thread overview]
Message-ID: <5B91E7EB.3040006@tlinx.org> (raw)
In-Reply-To: <20180904094158.6m2wxi22ulrlga4h@ws.net.home>
On 9/4/2018 2:41 AM, Karel Zak wrote:
Yeah, configure can be so tedious to use sometimes.
I set basic locations and the call common scripts to propagate settings
as defined in configure. So specific tools will get some
specific paths, and I try to ensure the rest are set
accordingly.
I try to default a bunch but based on previous settings, like (very
truncated list):
: ${exec_prefix:=${eprefix}}
: ${bits:=64}
: ${bindir=${eprefix}bin}
...
: ${localstatedir:=${prefix}var}
: ${includedir:=${exec_prefix}include}
Finally..I expand all the path stuff if the
associated var is set
declare -a path_ops=(
${prefix:+--prefix=$prefix}
${exec_prefix:+--exec-prefix=$exec_prefix}
${sharedstatedir:+--sharedstatedir=$sharedstatedir}
${sysconfdir:+--sysconfdir=$sysconfdir}
)
Result is almost all of the paths being set...
I keep all the above in a common location.
For all the option toggling, I use 4 arrays:
enable, disable, with and without, like:
declare -a enable=( readline select single-help-strings )
declare -a disable=(nls )
declare -a with=( gnu-ld )
declare -a without=()
then below (config_ops already has path_ops rolled in):
for action in enable disable with without; do
for op in $(eval echo "\${$action[@]}") ; do
config_ops+=( $(echo "--$action-$op") )
done
done
anyway -- some Q's on the versioning, but separate email...
prev parent reply other threads:[~2018-09-07 2:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 17:54 RFD: --enable-bindir-path ? L A Walsh
2018-08-30 8:45 ` Karel Zak
2018-08-31 22:55 ` L A Walsh
2018-09-03 10:17 ` Karel Zak
2018-09-04 9:41 ` Karel Zak
2018-09-07 2:52 ` L A Walsh [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=5B91E7EB.3040006@tlinx.org \
--to=lkml@tlinx.org \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).