Target/Host configuration elucidated
This commit is contained in:
parent
3f258ada43
commit
5ec2d62bea
|
@ -171,13 +171,16 @@ Since newlib is a library, the target concept does not apply to it, and the
|
||||||
build, host, and target options given to the top-level configure script must
|
build, host, and target options given to the top-level configure script must
|
||||||
be changed for newlib's use.
|
be changed for newlib's use.
|
||||||
|
|
||||||
The options are shifted according to these correspondences:
|
The build system shifts the options according to these correspondences:
|
||||||
|
|
||||||
gcc's build platform has no equivalent in newlib.
|
gcc's build platform has no equivalent in newlib.
|
||||||
gcc's host platform is newlib's build platform.
|
gcc's host platform is newlib's build platform.
|
||||||
gcc's target platform is newlib's host platform.
|
gcc's target platform is newlib's host platform.
|
||||||
and as mentioned before, newlib has no concept of target.
|
and as mentioned before, newlib has no concept of target.
|
||||||
|
|
||||||
|
In summary: the --target=TARGET switch to the top-level configure
|
||||||
|
script configures newlib's host platform.
|
||||||
|
|
||||||
`configure' options
|
`configure' options
|
||||||
===================
|
===================
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue