From: Matt Schuckmann <Matt.Schuckmann@planar.com>
To: "Andreas Müller" <schnitzeltony@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: CMake based recipes and defining CMAKE_BUILD_TYPE
Date: Thu, 7 Feb 2019 00:08:54 +0000 [thread overview]
Message-ID: <1549498134289.97332@planar.com> (raw)
In-Reply-To: <CALbNGRSFTLXtRa4Q7nAsA3dctrj3axXkbD=N3KAh71iMiMHryQ@mail.gmail.com>
Aright thank you for checking into this, you went farther then I expected.
I will take the approach of setting it for the recipes I really care about and leave the rest alone.
Matt S.
________________________________________
From: Andreas Müller <schnitzeltony@gmail.com>
Sent: Wednesday, February 6, 2019 3:11 PM
To: Matt Schuckmann
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] CMake based recipes and defining CMAKE_BUILD_TYPE
On Wed, Feb 6, 2019 at 11:53 PM Andreas Müller <schnitzeltony@gmail.com> wrote:
>
> On Wed, Feb 6, 2019 at 11:24 PM Andreas Müller <schnitzeltony@gmail.com> wrote:
> >
> > On Wed, Feb 6, 2019 at 11:05 PM Matt Schuckmann
> > <Matt.Schuckmann@planar.com> wrote:
> > >
> > > Hi Andreas,
> > >
> > > Thanks for the response, do you set build type in each recipe individually or is there some central .conf file or other other location that you set it?
> > >
> > > Matt S.
> > Honestly: I do not set them yet because I thought RelWithDebInfo is
> > default. That assumption was based on some projects but I checked now:
> > it does not seem to be something to rely on...
> >
> Will build-/run-test this with my 'world':
>
> diff --git a/meta/classes/cmake.bbclass b/meta/classes/cmake.bbclass
> index fd40a9863e..a8e08e6d6f 100644
> --- a/meta/classes/cmake.bbclass
> +++ b/meta/classes/cmake.bbclass
> @@ -153,6 +153,7 @@ cmake_do_configure() {
> -DCMAKE_TOOLCHAIN_FILE=${WORKDIR}/toolchain.cmake \
> -DCMAKE_VERBOSE_MAKEFILE=1 \
> -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1 \
> + -DCMAKE_BUILD_TYPE=${@d.getVar(oe.utils.vartrue('DEBUG_BUILD',
> 'Debug', 'RelWithDebInfo', d))} \
> ${EXTRA_OECMAKE} \
> -Wno-dev
> }
>
> Takes a while...
>
Not exactly: After short build I saw:
* There are some sed on '*-noconfig.cmake' they are going to break
* libeigen fails because it supports 'Debug' and 'Release' only (and I
bet there are more)
Will skip further tests and get the feeling that a common solution won't do...
Andreas
next prev parent reply other threads:[~2019-02-07 0:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 18:23 CMake based recipes and defining CMAKE_BUILD_TYPE Matt Schuckmann
2019-02-06 21:31 ` Andreas Müller
2019-02-06 22:04 ` Matt Schuckmann
2019-02-06 22:24 ` Andreas Müller
2019-02-06 22:53 ` Andreas Müller
2019-02-06 23:11 ` Andreas Müller
2019-02-07 0:08 ` Matt Schuckmann [this message]
2019-02-07 8:03 ` Mikko.Rapeli
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=1549498134289.97332@planar.com \
--to=matt.schuckmann@planar.com \
--cc=schnitzeltony@gmail.com \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.