diff options
| author | Thomas Petazzoni <thomas.petazzoni@bootlin.com> | 2018-03-24 15:20:01 +0100 |
|---|---|---|
| committer | Peter Korsgaard <peter@korsgaard.com> | 2018-03-25 17:35:26 +0200 |
| commit | 6729050f3a49dba42d2d881d31dbefd6b82b8dad (patch) | |
| tree | 6ee2f280927a17eb0a896d9ec86953d28c641645 /toolchain | |
| parent | 3ff90c8888dbc910665a8d76cc996cb3cb10c77d (diff) | |
| download | buildroot-6729050f3a49dba42d2d881d31dbefd6b82b8dad.tar.gz buildroot-6729050f3a49dba42d2d881d31dbefd6b82b8dad.zip | |
pkg-cmake: install CMake files as part of a package
Currently, the toolchainfile.cmake and Buildroot.cmake files are
installed outside of any package, just triggered by the toolchain
target.
As part of the per-package SDK effort, we are trying to avoid anything
that installs to the global $(HOST_DIR), and this is one of the
remaining files installed in $(HOST_DIR) outside of any package. We
fix this by installing such files as part of the toolchain package
post-install staging hooks.
Yes, a post-install staging hook to install things to $(HOST_DIR) is a
bit weird, but the toolchain infrastructure is made of target packages
only, and they all install a lot of stuff to $(HOST_DIR) already.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Diffstat (limited to 'toolchain')
| -rw-r--r-- | toolchain/toolchain/toolchain.mk | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/toolchain/toolchain/toolchain.mk b/toolchain/toolchain/toolchain.mk index 179c09edf1..91c9ca2eff 100644 --- a/toolchain/toolchain/toolchain.mk +++ b/toolchain/toolchain/toolchain.mk @@ -38,6 +38,3 @@ TOOLCHAIN_INSTALL_STAGING = YES endif $(eval $(virtual-package)) - -toolchain: $(HOST_DIR)/share/buildroot/toolchainfile.cmake -toolchain: $(HOST_DIR)/share/buildroot/Platform/Buildroot.cmake |
