[cfe-dev] Clang universal driver project state

[Sean Silva]

On Thu, Aug 1, 2013 at 1:11 PM, Simon Atanasyan <simon at atanasyan.com> wrote:

> On Wed, Jul 31, 2013 at 7:03 PM, Reid Kleckner <rnk at google.com> wrote:
> > On Wed, Jul 31, 2013 at 4:58 AM, Simon Atanasyan <simon at atanasyan.com>
> > wrote:
> >> That's why I'd like to implement the clang driver's configuration file
> >> support. My current plan is to put to this file the following settings
> >> and use these settings in the driver:
> >> - target triple
> >> - include files search paths (-I)
> >> - library search paths (-L)
> >> - program and files search paths (-B)
> >> - explicit paths for files and / or programs
> >>
> >> User will be able to select configuration file
> >> by --target=<config name> option.
> >
> > Can you implement this using the existing response file support,
> > rather than coming up with a new config file format?
>
> Unfortunately response file format does not satisfy all requirements.
>
> First I need a fine grained control over include headers directories.
> I need to distinguish regular system include directories, include
> directories with extern "C" semantic, c++ system include directories.
>

I believe that clang does actually have flags for this functionality (e.g.
-internal-externc-isystem). Does `clang -help | grep -A1 isystem` have
flags for all you need?

-- Sean Silva
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20130802/7bcbbd5c/attachment.html>