mirror of
https://github.com/espressif/binutils-gdb.git
synced 2025-06-22 02:50:08 +08:00
Update descriptions for ${host} and ${target} to reflect that they are now
canonical triples, not the original user entries.
This commit is contained in:
@ -1013,12 +1013,19 @@ same Makefile fragments, and the same @code{configure.in}.
|
|||||||
@end defvar
|
@end defvar
|
||||||
|
|
||||||
@defvar{host}
|
@defvar{host}
|
||||||
Contains the name that the user entered for the host. Since many things
|
Contains the full configuration name (generated by the script
|
||||||
that the user could enter would map to the same output from
|
@file{config.sub} from the name that the user entered) for the host.
|
||||||
@code{config.sub}, this variable is innappropriate to use for picking
|
This is a three-part name of the form
|
||||||
available configurations. For that, use @code{host_cpu},
|
|
||||||
@code{host_vendor}, and/or @code{host_os}. This variable is useful,
|
@example
|
||||||
however, for error messages.
|
@var{cpu}-@var{vendor}-@var{os}
|
||||||
|
@end example
|
||||||
|
|
||||||
|
@noindent
|
||||||
|
There are separate variables @code{host_cpu}, @code{host_vendor}, and
|
||||||
|
@code{host_os} that you can use to test each of the three parts; this
|
||||||
|
variable is useful, however, for error messages, and for testing
|
||||||
|
combinations of the three components.
|
||||||
@end defvar
|
@end defvar
|
||||||
|
|
||||||
@defvar{host_cpu}
|
@defvar{host_cpu}
|
||||||
@ -1044,12 +1051,19 @@ host as returned by @file{config.sub}.
|
|||||||
@end defvar
|
@end defvar
|
||||||
|
|
||||||
@defvar{target}
|
@defvar{target}
|
||||||
Contains the name that the user entered for the target. Since
|
Contains the full configuration name (generated by the script
|
||||||
many things that the user could enter would map to the same canonical
|
@file{config.sub} from the name that the user entered) for the target.
|
||||||
triple, this variable is innappropriate to use for picking available
|
This is a three-part name of the form
|
||||||
configurations. For that, use @code{target_cpu}, @code{target_vendor},
|
|
||||||
and/or @code{target_os}. This variable is useful, however, for error
|
@example
|
||||||
messages.
|
@var{cpu}-@var{vendor}-@var{os}
|
||||||
|
@end example
|
||||||
|
|
||||||
|
@noindent
|
||||||
|
There are separate variables @code{target_cpu}, @code{target_vendor}, and
|
||||||
|
@code{target_os} that you can use to test each of the three parts; this
|
||||||
|
variable is useful, however, for error messages, and for testing
|
||||||
|
combinations of the three components.
|
||||||
@end defvar
|
@end defvar
|
||||||
|
|
||||||
@defvar{target_cpu}
|
@defvar{target_cpu}
|
||||||
|
Reference in New Issue
Block a user