From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] config cache
Date: Sun, 2 Sep 2007 17:58:02 +0200 [thread overview]
Message-ID: <000301c7ed9d$c08b9510$54b0780a@atmel.com> (raw)
In-Reply-To: 20070901193243.GQ11697@aon.at
> Hi,
>
> read ./TODO
>
> Now i'd like to think loud about how to "implement" this.
>
> preface:
> ========
> First, i'm not too happy (any more) with the naming of the variables
> TARGET_CONFIGURE_OPTS and TARGET_CONFIGURE_ARGS -- same for HOST.
> Both are variables and not really OPTS, as opposed to the cache
> option/argument.
>
> Let me suggest that the CC= CFLAGS= settings live in (the respective
> CONFIGURE_ENV) variables.
>
> Suggestions for the known cv_* vars? CONFIGURE_SETTINGS come to mind,
> but that's a bit long to type.. TARGET_CONFIGURE_PARAMS ?
>
> cache:
> ======
>
> Per PROJECT, we use (resp. i suggest to use a) *central* config.cache,
> via --config-cache=$(PROJECT_BUILD_DIR)/target_config.cache which is put
> into a TARGET_CONFIGURE_OPTS variable (we renamed the formerly _OPTS to
> something like PARAM that is passed *before* the
> $(PACKAGE_DIR)/configure script).
>
> Since the advent of PROJECT one may even consider to build the
> autoconf'ed packages out-of-tree, i.e. unpack them in build_dir, step
> into project_dir/package/ and there do a
> $(PACKAGE_DIR)/configure $(TARGET_CONFIGURE_OTPS) && make
>
One of the advantages of the PROJECT thing, is that you can share
the result of the build between projects.
Only packages which can be configured in different ways should be
built in the project_build_dir.
> We would end up with a stanza like (modulo naming of the variables):
>
> (cd $(PROJECT_DIR)/$(PACKAGE_NAME) && \
> $(TARGET_CONFIGURE_ENV) \
> $(TARGET_CONFIGURE_PARAMS) \
> $(PACKAGE_DIR)/configure \
> $(TARGET_CONFIGURE_OPTS) \
Are you not using $(TARGET_CONFIGURE_OPTS) in a new meaning then.
I think in that case you should come up with a new name
to avoid bugs.
> --prefix=/usr \
> etc...
> )
>
Best Regards
Ulf Samuelsson ulf at atmel.com
Atmel Nordic AB
Mail: Box 2033, 174 02 Sundbyberg, Sweden
Visit: Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22 Fax +46 (8) 441 54 29
GSM +46 (706) 22 44 57
next prev parent reply other threads:[~2007-09-02 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-01 19:32 [Buildroot] [RFC] config cache Bernhard Fischer
2007-09-02 15:58 ` Ulf Samuelsson [this message]
2007-09-04 22:11 ` Bernhard Fischer
2007-09-04 22:50 ` Ulf Samuelsson
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='000301c7ed9d$c08b9510$54b0780a@atmel.com' \
--to=ulf@atmel.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