From: Saul Wold <sgw@linux.intel.com>
To: Ross Burton <ross.burton@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3] cmake: respect ${S} and ${B}
Date: Mon, 13 Jan 2014 14:06:23 -0800 [thread overview]
Message-ID: <52D4635F.6030304@linux.intel.com> (raw)
In-Reply-To: <1389376488-22286-2-git-send-email-ross.burton@intel.com>
On 01/10/2014 09:54 AM, Ross Burton wrote:
> Instead of the class-specific variables OECMAKE_BUILDPATH and
> OECMAKE_SOURCEPATH, just use ${B} and ${S}.
>
> If these two paths are different, delete any existing ${B} before running a
> build so that previous builds don't taint the current build.
>
> Note that OECMAKE_SOURCEPATH and OECMAKE_BUILDPATH are not respected, so recipes
> that manually set these in the past will need to be updated to either use
> something along the lines of separatebuilddir.inc or set B themselves. If the
> old variables are set, a warning is displayed.
>
> Signed-off-by: Ross Burton <ross.burton@intel.com>
> ---
> meta/classes/cmake.bbclass | 35 +++++++++++------------------------
> 1 file changed, 11 insertions(+), 24 deletions(-)
>
> diff --git a/meta/classes/cmake.bbclass b/meta/classes/cmake.bbclass
> index 30c1792..1dc406d2 100644
> --- a/meta/classes/cmake.bbclass
> +++ b/meta/classes/cmake.bbclass
> @@ -6,15 +6,6 @@ CCACHE = ""
> # We want the staging and installing functions from autotools
> inherit autotools
>
> -# Use in-tree builds by default but allow this to be changed
> -# since some packages do not support them (e.g. llvm 2.5).
> -OECMAKE_SOURCEPATH ?= "."
> -
> -# If declaring this, make sure you also set EXTRA_OEMAKE to
> -# "-C ${OECMAKE_BUILDPATH}". So it will run the right makefiles.
> -OECMAKE_BUILDPATH ?= ""
> -B="${S}"
> -
> # C/C++ Compiler (without cpu arch/tune arguments)
> OECMAKE_C_COMPILER ?= "`echo ${CC} | sed 's/^\([^ ]*\).*/\1/'`"
> OECMAKE_CXX_COMPILER ?= "`echo ${CXX} | sed 's/^\([^ ]*\).*/\1/'`"
> @@ -73,10 +64,14 @@ EOF
> addtask generate_toolchain_file after do_patch before do_configure
>
> cmake_do_configure() {
> - if [ ${OECMAKE_BUILDPATH} ]
> - then
> - mkdir -p ${OECMAKE_BUILDPATH}
> - cd ${OECMAKE_BUILDPATH}
> + if [ "${OECMAKE_BUILDPATH}" -o "${OECMAKE_SOURCEPATH}" ]; then
> + bbnote "cmake.bbclass no longer uses OECMAKE_SOURCEPATH and OECMAKE_BUILDPATH. This recipe now will do in-tree builds, to do out-of-tree builds set S and B."
> + fi
> +
> + if [ "${S}" != "${B}" ]; then
> + rm -rf ${B}
> + mkdir -p ${B}
> + cd ${B}
> fi
>
> # Just like autotools cmake can use a site file to cache result that need generated binaries to run
> @@ -88,7 +83,7 @@ cmake_do_configure() {
>
> cmake \
> ${OECMAKE_SITEFILE} \
> - ${OECMAKE_SOURCEPATH} \
> + ${S} \
> -DCMAKE_INSTALL_PREFIX:PATH=${prefix} \
> -DCMAKE_INSTALL_SO_NO_EXE=0 \
> -DCMAKE_TOOLCHAIN_FILE=${WORKDIR}/toolchain.cmake \
> @@ -98,20 +93,12 @@ cmake_do_configure() {
> }
>
> cmake_do_compile() {
> - if [ ${OECMAKE_BUILDPATH} ]
> - then
> - cd ${OECMAKE_BUILDPATH}
> - fi
> -
> + cd ${B}
> base_do_compile
> }
>
> cmake_do_install() {
> - if [ ${OECMAKE_BUILDPATH} ];
> - then
> - cd ${OECMAKE_BUILDPATH}
> - fi
> -
> + cd ${B}
> autotools_do_install
This seems to cause a problem:
ERROR: Logfile of failure stored in:
/srv/hdd/builds/world/tmp/work/ppc7400-poky-linux/cmake/2.8.12.1-r0/temp/log.do_install.5697
Log data follows:
| DEBUG: SITE files ['endian-big', 'bit-32', 'powerpc-common',
'common-linux', 'common-glibc', 'powerpc32-linux', 'powerpc-linux',
'common']
| DEBUG: Executing shell function do_install
| NOTE: make -j 16
DESTDIR=/srv/hdd/builds/world/tmp/work/ppc7400-poky-linux/cmake/2.8.12.1-r0/image
install
| make: *** No rule to make target `install'. Stop.
| ERROR: oe_runmake failed
| WARNING:
/srv/hdd/builds/world/tmp/work/ppc7400-poky-linux/cmake/2.8.12.1-r0/temp/run.do_install.5697:1
exit 1 from
| exit 1
| ERROR: Function failed: do_install (log file is located at
/srv/hdd/builds/world/tmp/work/ppc7400-poky-linux/cmake/2.8.12.1-r0/temp/log.do_install.5697)
ERROR: Task 7891
(/srv/hdd/poky/meta/recipes-devtools/cmake/cmake_2.8.12.1.bb,
do_install) failed with exit code '1'
Sau!
> }
>
>
next prev parent reply other threads:[~2014-01-13 22:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 17:54 [RFC][PATCH][V2] cmake: respect ${S} and ${B} Ross Burton
2014-01-10 17:54 ` [PATCH 1/3] " Ross Burton
2014-01-13 22:06 ` Saul Wold [this message]
2014-01-13 22:15 ` Saul Wold
2014-01-14 10:24 ` Burton, Ross
2014-01-10 17:54 ` [PATCH 2/3] separatebuilddir: build libproxy and taglib out of the source tree Ross Burton
2014-01-10 17:54 ` [PATCH 3/3] cmake: default to out-of-tree builds Ross Burton
2014-01-16 10:26 ` Stefan Herbrechtsmeier
2014-01-21 11:39 ` Burton, Ross
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=52D4635F.6030304@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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