[cfe-commits] r71109 - /cfe/trunk/docs/tools/clang.pod
daniel at zuster.org
Wed May 6 12:18:09 PDT 2009
Date: Wed May 6 14:18:09 2009
New Revision: 71109
Document environment variables we handle, and don't mention -pipe (it
isn't yet supported... lazy developers).
--- cfe/trunk/docs/tools/clang.pod (original)
+++ cfe/trunk/docs/tools/clang.pod Wed May 6 14:18:09 2009
@@ -179,11 +179,6 @@
Write output to I<file>.
-FIXME: WHY DOCUMENT THIS.
-Use pipes between commands, when possible.
Print the full library path of I<file>.
@@ -263,14 +258,41 @@
-No environment variables read.
+=item B<TMPDIR>, B<TEMP>, B<TMP>
+These environment variables are checked, in order, for the location to
+write temporary files used during the compilation process.
+If this environment variable is present, it is treated as a delimited
+list of paths to be added to the default system include path list. The
+delimiter is the platform dependent delimitor, as used in the I<PATH>
+Empty components in the environment variable are ignored.
+=item B<C_INCLUDE_PATH>, B<OBJC_INCLUDE_PATH>, B<CPLUS_INCLUDE_PATH>,
+These environment variables specify additional paths, as for CPATH,
+which are only used when processing the appropriate language.
+=item B<MACOSX_DEPLOYMENT_TARGET> (Apple only)
+If -mmacosx-version-min is unspecified, the default deployment target
+is read from this environment variable.
Clang currently does not have C++ support, and this manual page is incomplete.
To report bugs, please visit L<http://llvm.org/bugs/>. Most bug reports should
-include preprocessed source files (use the B<-E> option) along with information
+include preprocessed source files (use the B<-E> option) and the full output of
+the compiler, along with information to reproduce.
=head1 SEE ALSO
More information about the cfe-commits