From: Karel Zak <kzak@redhat.com>
To: util-linux@vger.kernel.org
Subject: build system changes
Date: Mon, 7 Nov 2011 11:34:00 +0100 [thread overview]
Message-ID: <20111107103400.GD25410@nb.net.home> (raw)
Hi,
I just pushed build-system changes:
- clean up AC macro names and move all macros to m4/ul.m4
- add macros (UL_REQUIRES_*) to maintain dependencies between components (e.g.
mountpoint(1) requires libmount)
and some developers oriented changes:
- add a new script tools/config-gen to call ./configure script with
predefined set of options (defined in tools/config-gen.d/), for example:
./tools/config-gen all
will enable all possible utils
./tools/config-gen devel non-nls selinux
will enable all possible utils, devel options, selinux support and
disable NLS.
Note, it's NOT expected that end-users or downstream will use the
config-gen script. This script is for developers only.
- add build-system regression test (based on tools/config-gen), note
that the test is not enabled by default, you have to use:
./tests/run.sh build-sys --force
See Documentation/howto-build-sys.txt for more details.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
reply other threads:[~2011-11-07 10:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111107103400.GD25410@nb.net.home \
--to=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).