path: root/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
Commit message (Collapse)AuthorAgeFilesLines
* gdb-cross-canadian: use PACKAGECONFIG for python and readlineJonathan Liu2016-04-031-5/+7
| | | | | Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdb-cross-canadian: Add missing virtual/* DEPENDSRichard Purdie2016-02-151-1/+3
| | | | | | | cross-canadian does INHIBIT_DEFAULT_DEPS so we need to add the various virtual/* toolchain pieces we rely on manually. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdb: add whitespace to _appendRoss Burton2015-03-091-1/+1
| | | | | | | Add leading whitepace to EXTRA_OECONF_append so it doesn't rely on the original value ending with trailing whitespace. Spotted by Robert P. J. Day. Signed-off-by: Ross Burton <ross.burton@intel.com>
* gdb-cross-canadian: Add to sstate whitelistRichard Purdie2014-09-301-0/+2
| | | | | | | The various gdb variants overwrite in datadir so whitelist this for now, they are the same files and this is not an issue. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Replace one-line DESCRIPTION with SUMMARYPaul Eggleton2014-01-021-1/+1
| | | | | | | | | | | A lot of our recipes had short one-line DESCRIPTION values and no SUMMARY value set. In this case it's much better to just set SUMMARY since DESCRIPTION is defaulted from SUMMARY anyway and then the SUMMARY is at least useful. I also took the opportunity to fix up a lot of the new SUMMARY values, making them concisely explain the function of the recipe / package where possible. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
* cross-canadian: Handle powerpc linux verses linux-gnuspeRichard Purdie2013-10-301-0/+1
| | | | | | | | | | | | | | PowerPC toolchains can use the OS "linux" or "linux-gnuspe". This patch links them together so the one cross-canadian toolchain can support both. GCC_FOR_TARGET is set for the GCC recipe as otherwise configure can pick up an incorrect value. [YOCTO #5354] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com>
* gdb-cross-canadian: use correct exec-prefix path for pythonSamuli Piippo2013-05-291-1/+1
| | | | | | | | | | | | Incorrect exec-prefix path was given to gdb which leads to gdb startup failure when SDK is not installed to its original destination. Gdb relocates the exec-prefix path, so it will work for SDKs that are installed to different location. PYTHONHOME env in no longer neeeded for gdb. [YOCTO #3839] Signed-off-by: Saul Wold <sgw@linux.intel.com>
* gdb-cross-canadian: set everything in gdb-cross-canadian.incMarcin Juszkiewicz2013-05-121-0/+2
| | | | | | | This allows out-of-tree versions to include one file to have all set. Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> Signed-off-by: Saul Wold <sgw@linux.intel.com>
* gdb-cross-canadian: Set RDEPENDS on the specific package that needs itRichard Purdie2013-02-041-2/+2
| | | | | | | Set the RDEPENDS on the specific package that has the dependency and stop it being applied to for example ${PN}-doc (and others). Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk: Switch to using nativesdk as a prefix, not a suffixRichard Purdie2012-08-311-3/+4
| | | | | | | | | | | | | As discussed on the mailing lists, using a suffix to package names is hard and has lead to many recipes having to do PKGSUFFIX games. Its looking extremely hard to scale nativesdk much further without hacking many recipes. By comparison, using a prefix like multilib does works much better and doesn't involve "hacking" as many recipes. This change converts nativesdk to use a prefix using the existing multilib infrastructure. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdb-cross-canadian: Fix linking issues when python support is enabledKhem Raj2012-03-231-3/+4
| | | | | | | | | | | | | | | | gdb-cross-canadian was linking with static version of libpython and looking for build host python when run. This could be mismatch between python-nativesdk and build host provided python. So we make it consistent to always use python-nativesdk Instead of adding bunch of -L we add -rpath and -rpath-link so that gdb finds all needed libraries in SDK and does not reach out into host This should fix yocto PR# 2077 as well. Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdb-cross-canadian: not shipping libiberty.Lianhao Lu2012-03-231-0/+6
| | | | | | | | | | | Fixed package QA warnings. WARNING: QA Issue: non -staticdev package contains static .a library: gdb-cross-canadian-i586 path '/work/x86_64-nativesdk-pokysdk-linux/gdb-cross-canadian-i586-7.4-r6.3/packages-split/gdb-cross-canadian-i586/opt/poky/1.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/lib/lib/libiberty.a' Signed-off-by: Lianhao Lu <lianhao.lu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdb-cross-canadian: build gdb with python supportEric BENARD2012-02-261-1/+19
| | | | | | | | | | | | | | | | | | | | | * python support is needed for providing finer scripting control in gdb, and for remote controling gdb for example from qtcreator * gdb/configure tries to autodetect python using python executable with --includes --ldflags --exec-prefix to get the right flags As it's difficult to achieve in OE's context, we generate a script which will return the right values and make gdb's build system happy. This idea was taken from the following article : http://www.mentby.com/doug-evans-2/python-enabled-gdb-on-windows-and-relocation.html * tested using angstrom & armv7 target & qtcreator 201005 & 2.4.0 * MJ: updated paths to python as disscussed here http://lists.linuxtogo.org/pipermail/openembedded-core/2012-February/018222.html now it's easier with cross-canadian staging dir and SDKPATH fixed :) Signed-off-by: Eric BĂ©nard <eric@eukrea.com> Cc: fcooper@ti.com Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add readline as dependecy for gdb-cross-canadianMatthew McClintock2011-10-271-1/+1
| | | | | | | | Got errors that we were unable to find -lreadline, this fixed the issue Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Using TRANSLATED_TARGET_ARCH instead of TARGET_ARCH.Lianhao Lu2010-12-101-1/+1
| | | | | | | | | | | Using TRANSLATED_TARGET_ARCH instead of TARGET_ARCH for cross-canadian packages. This is due to the TARGET_ARCH of x86_64 would results incorrect packaging in cross-canadian packages. The pacakge name appendix of x86_64 target in cross-canadian packages is x86-64. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
* cross-canadian: pkg name includes target archLianhao Lu2010-12-101-0/+7
This commit fixes Bug #528. 1. Added the target arch name to the pkg name of gcc-cross-canadian, gdb-cross-candian and bintuils-cross-candian. 2. Move the cross-canadian pkgs out of task-sdk-host into a new task task-cross-canadian. 3. Added the RDEPENDS of task-cross-canadian into meta-toolchain. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>