From: James Hogan <james.hogan@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gdb: convert to the package infrastructure
Date: Thu, 28 Feb 2013 08:39:18 +0000 [thread overview]
Message-ID: <512F17B6.70501@imgtec.com> (raw)
In-Reply-To: <512F0EAD.4080406@mind.be>
On 28/02/13 08:00, Arnout Vandecappelle wrote:
> On 26/02/13 23:13, Thomas Petazzoni wrote:
>> This commit converts gdb to the package infrastructure, and therefore
>> moves it from toolchain/gdb to package/gdb.
>>
>> The target package is now visible in "Package selection for the
>> target" => "Debugging, profiling and benchmark". The main option,
>> "gdb", forcefully selects the "gdbserver" sub-option by
>> default. Another sub-option, "full debugger" allows to install the
>> complete gdb on the target. When this option is enabled, then
>> "gdbserver" is no longer forcefully selected. This ensures that at
>> least gdbserver or the full debugger gets built/installed, so that the
>> package is not a no-op.
>>
>> The host debugger is still enabled through a configuration option in
>> "Toolchain". It is now visible regardless of the toolchain type (it
>> used to be hidden for External Toolchains). The configuration options
>> relative to the host debugger are now in package/gdb/Config.in.host,
>> similar to how we have package/binutils/Config.in.host.
>>
>> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>
> This looks like a great idea!
>
> Just a couple of generic remarks, and then a few specific ones below.
> The generic remarks are probably for follow-up patches.
>
> * It really doesn't make sense to build host-gdb without a gdbserver for
> the target. So I would auto-select gdbserver from host-gdb.
Kgdb (kernel debugging) is one use case where you'd want host-gdb
without necessarily gdbserver.
>
> * Does it really make sense to keep options for four different gdb
> versions? Can't we just remove the user-selectable version completely?
The option is useful for arches which don't have their gdb port upstream
yet, giving them a chance to update their patches.
Cheers
James
next prev parent reply other threads:[~2013-02-28 8:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 22:13 [Buildroot] [PATCH] gdb: convert to the package infrastructure Thomas Petazzoni
2013-02-28 8:00 ` Arnout Vandecappelle
2013-02-28 8:39 ` James Hogan [this message]
2013-02-28 8:47 ` Thomas Petazzoni
2013-02-28 12:11 ` James Hogan
2013-02-28 12:20 ` Thomas Petazzoni
2013-02-28 12:24 ` James Hogan
2013-02-28 8:56 ` Thomas Petazzoni
2013-03-01 21:42 ` Arnout Vandecappelle
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=512F17B6.70501@imgtec.com \
--to=james.hogan@imgtec.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