espressif/binutils-gdb
1
0
Fork 0
mirror of https://github.com/espressif/binutils-gdb.git synced 2025-06-23 19:50:13 +08:00
Code Issues Packages Projects Releases Wiki Activity

* configure.texi: Explain better about .gdbinit and about

Browse Source 
the environment that configure.in sections run in.
This commit is contained in:
John Gilmore
1992-02-19 23:42:09 +00:00
parent 90d85bc42b
commit 442b8598ad
1 changed files with 13 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
configure.texi
View File

@ -145,11 +145,10 @@ output file. (See @ref{Makefiles, , , make, Makefiles}.)
@item Generate @file{.gdbinit} @item Generate @file{.gdbinit}
If the source directory contains a @file{.gdbinit} file and the build If the source directory contains a @file{.gdbinit} file and the build
directory is not the same as the source directory, a @file{.gdbinit} directory is not the same as the source directory, a @file{.gdbinit}
file is created in the build directory. (see @ref{Command Files, , , file is created in the build directory. This @file{.gdbinit} file
gdb, Command Files}.) contains just a @code{source} command, which will cause the @file{.gdbinit}
@c There doesn't seem to be anything else about this. Is the build-dir file from the source directory to be read by GDB. (see
@c .gdbinit identical with the source-dir one? If so should say "copy" @ref{Command Files, , , gdb, Command Files}.)
@c rather than "create" to make it clear.
@item Make symbolic links @item Make symbolic links
Most directories have some symbolic links with generic names built Most directories have some symbolic links with generic names built
@ -1006,10 +1005,15 @@ fragment.
A @file{configure.in} file for Cygnus configure consists of a A @file{configure.in} file for Cygnus configure consists of a
@dfn{per-invocation} section, followed by a @dfn{per-host} section, @dfn{per-invocation} section, followed by a @dfn{per-host} section,
followed by a @dfn{per-target} section, optionally followed by a followed by a @dfn{per-target} section, optionally followed by a
@dfn{post-target} section. Each section is a shell script fragment sourced by @dfn{post-target} section. Each section is a shell script fragment,
configure at the appropriate time. The interface between configure and which is sourced by the configure shell script at an appropriate time.
the shell fragments is through a set of shell variables. All sections Values are passed among configure and the shell fragments through a
are sourced in the build directory. set of shell variables. When each section is being interpreted
(sourced) by the shell, the shell's current directory is the build
directory, and any files created by the section (or referred to by the
section) will be relative to the build directory. To reference files
in other places (such as the source directory), prepend a shell
variable such as @code{srcdir} to the desired file name.
@cindex Per-invocation section @cindex Per-invocation section
The beginning of the @file{configure.in} file begins the per-invocation The beginning of the @file{configure.in} file begins the per-invocation