From: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
To: Kevron Rees <kevron.m.rees@intel.com>,
openembedded-core@lists.openembedded.org
Cc: tripzero.kev@gmail.com
Subject: Re: [PATCH] cmake.bbclass: remove ${prefix} assignment
Date: Mon, 16 Nov 2015 12:33:08 +0100 [thread overview]
Message-ID: <5649BEF4.10002@herbrechtsmeier.net> (raw)
In-Reply-To: <1447464250-12204-1-git-send-email-kevron.m.rees@intel.com>
Am 14.11.2015 um 02:24 schrieb Kevron Rees:
> CMAKE_INSTALL_PREFIX has a different semantic meaning than ${prefix}[1]. cmake treats
> CMAKE_INSTALL_PREFIX the same as the DESTDIR environment variable.
CMAKE_INSTALL_PREFIX and DESTDIR are different and used together [1]:
[...] install the concerned software using the installation prefix [...]
prepended with the DESTDIR [...]
> Setting
> CMAKE_INSTALL_PREFIX to ${prefix} is inappropriate.
Why? It configures the prefix.
${prefix} is set to "/usr" in bitbake.conf. The default
CMAKE_INSTALL_PREFIX is "/usr/local"
> This will likely break a lot of cmake recipes that have do_post_install hacks to get
> around this bug.
What hacks do you mean?
> [1] - https://cmake.org/cmake/help/v3.0/variable/CMAKE_INSTALL_PREFIX.html
>
> Signed-off-by: Kevron Rees <kevron.m.rees@intel.com>
> ---
> meta/classes/cmake.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/cmake.bbclass b/meta/classes/cmake.bbclass
> index ae3cc02..b7d5950 100644
> --- a/meta/classes/cmake.bbclass
> +++ b/meta/classes/cmake.bbclass
> @@ -108,7 +108,7 @@ cmake_do_configure() {
> cmake \
> ${OECMAKE_SITEFILE} \
> ${OECMAKE_SOURCEPATH} \
> - -DCMAKE_INSTALL_PREFIX:PATH=${prefix} \
> + -DCMAKE_INSTALL_PREFIX:PATH="" \
> -DCMAKE_INSTALL_BINDIR:PATH=${bindir} \
> -DCMAKE_INSTALL_SBINDIR:PATH=${sbindir} \
> -DCMAKE_INSTALL_LIBEXECDIR:PATH=${libexecdir} \
prev parent reply other threads:[~2015-11-16 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 1:24 [PATCH] cmake.bbclass: remove ${prefix} assignment Kevron Rees
2015-11-16 11:33 ` Stefan Herbrechtsmeier [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=5649BEF4.10002@herbrechtsmeier.net \
--to=stefan@herbrechtsmeier.net \
--cc=kevron.m.rees@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tripzero.kev@gmail.com \
/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