summaryrefslogtreecommitdiffstats
path: root/package/gdb/gdb.mk
Commit message (Collapse)AuthorAgeFilesLines
* gdb: properly set the gdb site in all casesThomas Petazzoni2013-04-131-1/+4
| | | | | | | | | | | | | | | | | | | | | Until now, the gdb site for AVR32 was adjusted only when GDB_VERSION was not set, i.e only when the cross-gdb is *not* built. We should in fact also set the site when the cross-gdb is built, so when GDB_VERSION is defined through package/gdb/Config.in.host. So, instead, we now have something like: ifeq ($(GDB_VERSION),) # we define here a default version that is used when the cross-gdb is # not built and only the target gdb is selected. endif ifeq ($(GDB_VERSION),something-special) GDB_SITE = some-special-site-for-some-special-gdb-version endif Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* gdb: add back $ARCH-linux-gdb symlink for host-gdbPeter Korsgaard2013-04-111-0/+8
| | | | | | Like we do for the toolchain and we used to to do for gdb. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* gdb: install gdbserver into the SDKThomas Petazzoni2013-04-111-0/+14
| | | | | | | | | | | | In order for a Buildroot toolchain to be usable as an external toolchain, we should copy the target gdbserver somewhere into $(HOST_DIR). In order to match what Crosstool-NG does (and therefore to match something the external toolchain logic already understands), we install gdbserver in $(HOST_DIR)/usr/<tuple>/debug-root/usr/bin/gdbserver. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* gdb: convert to the package infrastructureThomas Petazzoni2013-04-111-0/+101
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. Since gdb is now a proper package, it is no longer allowed to 'select BR2_PTHREADS_DEBUG' to ensure thread debugging is available when needed. Instead, it now 'depends on BR2_TOOLCHAIN_HAS_THREADS_DEBUG'. This option, in turn, is selected by the different toolchain backends when appropriate. The 'BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED' option is removed, since we no longer need to know when it is allowed to 'select BR2_PTHREADS_DEBUG'. Also, the 'BR2_PTHREADS_DEBUG' option is moved to appear right below the thread implementation selection (in the case of the Buildroot toolchain backend). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>