From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] libcurl: propagate buildroot debugging option
Date: Sat, 29 Apr 2017 16:18:18 +0200 [thread overview]
Message-ID: <20170429161818.0d541857@free-electrons.com> (raw)
In-Reply-To: <6e5e28bc-b89a-931e-be6c-98c2ebb5434f@awox.com>
Hello,
On Tue, 25 Apr 2017 17:42:16 +0200, Olivier Valentin wrote:
> When buildroot has debugging enabled, let libcurl configure
> its build accordingly.
>
> Signed-off-by: Olivier Valentin <ovalentin@awox.com>
Thanks, but since commit
https://git.buildroot.org/buildroot/commit/?id=0552a367dbdc27a211daaac3359d81dd537e384f,
we no longer pass --enable-debug/--disable-debug to packages. Indeed,
we have realized that packages are not consistent in what they do when
--enable-debug/--disable-debug is passed.
So, BR2_ENABLE_DEBUG is nowadays *only* to get packages built with
debugging symbols, and this is controlled by adding "-g" to CFLAGS.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-04-29 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 15:42 [Buildroot] libcurl: propagate buildroot debugging option Olivier Valentin
2017-04-29 14:18 ` Thomas Petazzoni [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=20170429161818.0d541857@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox