From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next v6 10/10] package/pkg-kconfig: handle KCONFIG_DEPENDENCIES with per-package directories
Date: Sun, 25 Nov 2018 18:57:42 +0100 [thread overview]
Message-ID: <20181125175742.GE28830@scaer> (raw)
In-Reply-To: <20181123145815.13008-11-thomas.petazzoni@bootlin.com>
Thomas, All,
On 2018-11-23 15:58 +0100, Thomas Petazzoni spake thusly:
> The pkg-kconfig infrastructure hijacks the regular chain of build
> steps to insert its own step to prepare the configuration of kconfig
> packages. This additional step may have dependencies of its own, such
> as host-flex, host-bison or toolchain.
>
> In the context of per-package directory support, those dependencies
> must be copied to the per-package directory of the current package
> prior to doing the config preparation. This commit implements this
> logic by adding a call to prepare-per-package-directory at the right
> spot.
>
> Reported-by: Andreas Naumann <anaumann@ultratronik.de>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Regards,
Yann E. MORIN.
> ---
> package/pkg-kconfig.mk | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/pkg-kconfig.mk b/package/pkg-kconfig.mk
> index d6c95b897e..bf43632adc 100644
> --- a/package/pkg-kconfig.mk
> +++ b/package/pkg-kconfig.mk
> @@ -113,6 +113,7 @@ endef
> # Since the file could be a defconfig file it needs to be expanded to a
> # full .config first.
> $$($(2)_DIR)/$$($(2)_KCONFIG_DOTCONFIG): $$($(2)_KCONFIG_FILE) $$($(2)_KCONFIG_FRAGMENT_FILES)
> + $$(call prepare-per-package-folder,$$($(2)_KCONFIG_DEPENDENCIES))
> $$(Q)$$(if $$($(2)_KCONFIG_DEFCONFIG), \
> $$($(2)_KCONFIG_MAKE) $$($(2)_KCONFIG_DEFCONFIG), \
> $$(INSTALL) -m 0644 -D $$($(2)_KCONFIG_FILE) $$(@))
> --
> 2.19.1
>
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-11-25 17:57 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 14:58 [Buildroot] [PATCH next v6 00/10] Per-package host/target directory support Thomas Petazzoni
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 01/10] Makefile: evaluate CCACHE and HOST{CC, CXX} at time of use Thomas Petazzoni
2018-11-26 18:14 ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 02/10] support/scripts/check-host-rpath: split condition on two statements Thomas Petazzoni
2018-11-26 18:14 ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 03/10] Makefile: rework main directory creation logic Thomas Petazzoni
2018-11-23 18:07 ` Yann E. MORIN
2018-11-26 18:14 ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 04/10] Makefile: move .NOTPARALLEL statement after including .config file Thomas Petazzoni
2018-11-26 18:15 ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 05/10] Makefile: define TARGET_DIR_WARNING_FILE relative to TARGET_DIR Thomas Petazzoni
2018-11-26 18:15 ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 06/10] package/pkg-generic: adjust config scripts tweaks for per-package directories Thomas Petazzoni
2018-11-23 18:09 ` Yann E. MORIN
2018-11-26 18:15 ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 07/10] core: implement per-package SDK and target Thomas Petazzoni
2018-11-23 21:50 ` Yann E. MORIN
2018-12-04 22:24 ` Arnout Vandecappelle
2018-12-05 8:04 ` Thomas Petazzoni
2018-12-05 9:18 ` Arnout Vandecappelle
2018-12-05 9:44 ` Thomas Petazzoni
2018-12-05 10:41 ` Arnout Vandecappelle
2018-12-05 16:08 ` Andreas Naumann
2018-12-05 16:31 ` Thomas Petazzoni
2018-12-05 16:52 ` Andreas Naumann
2018-12-06 10:21 ` Andreas Naumann
2018-12-06 10:28 ` Thomas Petazzoni
2018-12-06 10:42 ` Andreas Naumann
2018-12-06 10:58 ` Thomas Petazzoni
2018-12-06 13:31 ` Andreas Naumann
2018-12-26 17:34 ` Thomas Petazzoni
2018-12-26 18:33 ` Thomas De Schampheleire
2019-01-10 21:25 ` Arnout Vandecappelle
2019-01-11 20:09 ` Thomas De Schampheleire
2019-01-13 22:10 ` Arnout Vandecappelle
2019-01-14 16:01 ` Thomas De Schampheleire
2019-01-14 16:33 ` Thomas Petazzoni
2019-01-14 20:19 ` Thomas De Schampheleire
2019-01-14 20:43 ` Thomas De Schampheleire
2018-12-26 18:58 ` Yann E. MORIN
2018-12-27 16:17 ` Thomas Petazzoni
2019-01-10 21:14 ` Arnout Vandecappelle
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 08/10] Makefile: allow top-level parallel build with BR2_PER_PACKAGE_DIRECTORIES=y Thomas Petazzoni
2018-11-23 18:11 ` Yann E. MORIN
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 09/10] package/pkg-generic: make libtool .la files compatible with per-package directories Thomas Petazzoni
2018-11-25 17:57 ` Yann E. MORIN
2018-11-30 10:20 ` Thomas Petazzoni
2018-12-01 10:59 ` Yann E. MORIN
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 10/10] package/pkg-kconfig: handle KCONFIG_DEPENDENCIES " Thomas Petazzoni
2018-11-25 17:57 ` Yann E. MORIN [this message]
2018-12-05 15:23 ` Andreas Naumann
2018-12-06 14:07 ` Andreas Naumann
2018-12-06 14:25 ` Thomas Petazzoni
2018-12-26 16:40 ` Thomas Petazzoni
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=20181125175742.GE28830@scaer \
--to=yann.morin.1998@free.fr \
--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