r174612 - Documentation: add information about builtin includes to FAQ

[Dmitri Gribenko]

On Thu, Feb 7, 2013 at 7:10 PM, Jordan Rose <jordan_rose at apple.com> wrote:
>
> On Feb 7, 2013, at 6:36 , Dmitri Gribenko <gribozavr at gmail.com> wrote:
>
> Author: gribozavr
> Date: Thu Feb  7 08:36:37 2013
> New Revision: 174612
>
> URL: http://llvm.org/viewvc/llvm-project?rev=174612&view=rev
> Log:
> Documentation: add information about builtin includes to FAQ
>
> Modified:
>    cfe/trunk/docs/FAQ.rst
>    cfe/trunk/docs/LibTooling.rst
>
> Modified: cfe/trunk/docs/FAQ.rst
> URL:
> http://llvm.org/viewvc/llvm-project/cfe/trunk/docs/FAQ.rst?rev=174612&r1=174611&r2=174612&view=diff
> ==============================================================================
> --- cfe/trunk/docs/FAQ.rst (original)
> +++ cfe/trunk/docs/FAQ.rst Thu Feb  7 08:36:37 2013
> @@ -51,3 +51,14 @@ driver and add the option you need.  Alt
> ``clang -Xclang <option> ...`` to force the driver pass ``<option>`` to
> ``clang -cc1``.
>
> +I get errors about some headers being missing (``stddef.h``, ``stdard.h``)
> +--------------------------------------------------------------------------
> +
> +Some header files (``stddef.h``, ``stdard.h``, and others) are shipped with
> +Clang --- these are called builtin includes.  Clang searches for them in a
> +directory relative to the location of the ``clang`` binary.  If you moved
> the
> +``clang`` binary, you need to move the builtin headers, too.
>
>
> The thing I always forget is where the relative path is. I believe it's
> ../include (?) but it's probably worth mentioning here regardless.

It is documented in the linked page:

> +More information can be found in the :ref:`libtooling_builtin_includes`
> +section.

Dmitri

-- 
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/