From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10246] BR2_ENABLE_DEBUG does not have the expected effect for cmake packages
Date: Wed, 23 Aug 2017 08:22:15 +0000 [thread overview]
Message-ID: <bug-10246-163-A9o9XYZN2n@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10246-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10246
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
What you're proposing is to exactly revert
https://git.buildroot.org/buildroot/commit/package/pkg-cmake.mk?id=104bb29e0490bfb487e2e665448dd3ca07fcc2b5,
which already reverted the change you're proposing :)
So, see the commit log of
https://git.buildroot.org/buildroot/commit/package/pkg-cmake.mk?id=104bb29e0490bfb487e2e665448dd3ca07fcc2b5
for the explanation of why we're using the Debug build type and not the
RelWithDebInfo build type.
If you disagree, please submit a patch to the mailing list with a precise
description of why reverting
https://git.buildroot.org/buildroot/commit/package/pkg-cmake.mk?id=104bb29e0490bfb487e2e665448dd3ca07fcc2b5
is a good idea. Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-08-23 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 4:10 [Buildroot] [Bug 10246] New: BR2_ENABLE_DEBUG does not have the expected effect for cmake packages bugzilla at busybox.net
2017-08-23 4:41 ` [Buildroot] [Bug 10246] " bugzilla at busybox.net
2017-08-23 8:22 ` bugzilla at busybox.net [this message]
2017-08-23 9:00 ` bugzilla at busybox.net
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=bug-10246-163-A9o9XYZN2n@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 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.