You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-2Lines changed: 10 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -83,9 +83,17 @@ number of different environment variables.
83
83
certain `TARGET`s, it also is assumed to know about other flags (most
84
84
common is `-fPIC`).
85
85
*`AR` - the `ar` (archiver) executable to use to build the static library.
86
-
*`CRATE_CC_NO_DEFAULTS` - the default compiler flags may cause conflicts in some cross compiling scenarios. Setting this variable will disable the generation of default compiler flags.
86
+
*`CRATE_CC_NO_DEFAULTS` - the default compiler flags may cause conflicts in
87
+
some cross compiling scenarios. Setting this variable
88
+
will disable the generation of default compiler
89
+
flags.
87
90
*`CXX...` - see [C++ Support](#c-support).
88
91
92
+
Furthermore, projects using this crate may specify custom environment variables
93
+
to be inspected, for example via the `Build::try_flags_from_environment`
94
+
function. Consult the project’s own documentation or its use of the `cc` crate
95
+
for any additional variables it may use.
96
+
89
97
Each of these variables can also be supplied with certain prefixes and suffixes,
90
98
in the following prioritized order:
91
99
@@ -94,7 +102,7 @@ in the following prioritized order:
94
102
3.`<build-kind>_<var>` - for example, `HOST_CC` or `TARGET_CFLAGS`
95
103
4.`<var>` - a plain `CC`, `AR` as above.
96
104
97
-
If none of these variables exist, cc-rs uses built-in defaults
105
+
If none of these variables exist, cc-rs uses built-in defaults.
98
106
99
107
In addition to the above optional environment variables, `cc-rs` has some
100
108
functions with hard requirements on some variables supplied by [cargo's
0 commit comments