This is the mail archive of the
newlib-cvs@sourceware.org
mailing list for the newlib project.
[newlib-cygwin] Target/Host configuration elucidated
- From: Corinna Vinschen <corinna at sourceware dot org>
- To: newlib-cvs at sourceware dot org
- Date: 23 Mar 2016 10:30:42 -0000
- Subject: [newlib-cygwin] Target/Host configuration elucidated
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=5ec2d62bea91c6574cb3677f09220c0170bf14cd
commit 5ec2d62bea91c6574cb3677f09220c0170bf14cd
Author: Konrad Schwarz <konrad.schwarz@siemens.com>
Date: Wed Mar 23 05:54:13 2016 +0100
Target/Host configuration elucidated
Diff:
---
newlib/README | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/newlib/README b/newlib/README
index bcabfba..a7b84dc 100644
--- a/newlib/README
+++ b/newlib/README
@@ -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
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 host platform is newlib's build platform.
gcc's target platform is newlib's host platform.
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
===================