binutils/binutils: Add CUSTOM version and CUSTOM_LOCATION config options and GetCustom
CUSTOM_LOCATION config options only presented in menuconfig if component
CUSTOM version selected.
Signed-off-by: "David Holsgrove" <david.holsgrove@xilinx.com>
[yann.morin.1998@free.fr: fix indentation, don't patch custom dir location]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Message-Id: <7a604b5df9c84a1e20c3.1349931195@localhost.localdomain>
PatchWork-Id: 190788
2 Helper Makefile for testing gcc toolchains using the gcc-testsuite
3 ==================================================================
8 * DejaGnu 'runtest' v1.4.4+
15 Edit default.cfg to reflect your toolchain and target configuration.
17 Alternatively, override configuration variables on the command line.
19 Available config variables:
22 The name of the tool you want to test.
23 Currently supported: gcc or g++
27 The hostname or IP of the machine to execute run-tests
31 Execute the run-test as this user on DG_TARGET_HOSTNAME
36 The C/C++ tests you want to check
37 Default: (empty, means all tests)
43 The first two examples require a networked target with ssh access and automatic
44 ssh login (see section below). Target SW should be compiled with the toolchain
47 Run default gcc compile/execution tests:
48 $ make DG_TOOLNAME=gcc DG_TARGET_HOSTNAME=192.168.17.93 DG_TARGET_USERNAME=root
50 Run default g++ compile/execution tests:
51 $ make DG_TOOLNAME=g++ DG_TARGET_HOSTNAME=192.168.17.93 DG_TARGET_USERNAME=root
53 Run selected gcc compile only tests (no target required):
54 $ make DG_TOOLNAME=gcc DG_C_TESTS="compile.exp noncompile.exp"
57 SSH automatic login configuration example
58 -----------------------------------------
61 ssh-keygen -t rsa (then simply press enter thru all steps)
62 ssh-copy-id -i ~/.ssh/id_rsa.pub <username>@<target IP>
64 Now automatic ssh login should work - test by doing a simple ssh session to target.
66 Note: The procedure might be slightly different for your particular target.
69 Getting rid of the test-suite
70 -----------------------------
72 If you no longer have a need for the test-suite, then you can remove it altogether
73 from your toolchain. Just delete the test-suite/ dub-dir.
78 Martin Lund <mgl@doredevelopment.dk>
81 "Yann E. MORIN" <yann.morin.1998@free.fr>
82 Getting rid of the test-suite