scripts/functions: Fix CT_ExtractGit function.
Change CT_ExtractGit so that it clones the repository, instead of just
symlinking it. After cloning, any given ref is checked out, or if no
ref is given, the HEAD of the repository is checked out.
This makes CT_Extract behave similar for git repositories as it does
for tarballs, so that it for example can be used for passing glibc-ports
as a git repository.
Signed-off-by: "Esben Haabendal" <esben.haabendal@prevas.dk>
[yann.morin.1998@anciens.enib.fr: fix incomplete var rename]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
1 # Menu for the cross GDB
3 config STATIC_TOOLCHAIN
4 select GDB_CROSS_STATIC if GDB_CROSS
10 select GDB_GDBSERVER if ! BARE_METAL
12 Build and install a cross-gdb for the target, to run on host.
16 config GDB_CROSS_STATIC
18 prompt "Build a static cross gdb"
19 select WANTS_STATIC_LINK
21 A static cross gdb can be usefull if you debug on a machine that is
22 not the one that is used to compile the toolchain.
24 That way, you can share the cross-gdb without installing a toolchain
25 on every machine that will be used to debug target programs.
27 config GDB_CROSS_PYTHON
29 prompt "Enable python scripting"
30 depends on ! GDB_CROSS_STATIC
33 Say 'y' if you want to use Python scripting inside gdb.
34 Say 'n' if you do not want to.
36 Beware that enabling Python scripting could render the gdb
37 executable non-functional if you move it to another machine.
38 Building a static gdb can help in this regard, although there
39 have been reports of problems when linking gdb to the static
40 libpython.a. This should be fixed in gdb >=7.3. YMMV.