[cfe-dev] MinGW header search paths (InitHeaderSearch.cpp)

[Ruben Van Boxem]

2011/4/22 Douglas Gregor <dgregor at apple.com>

>
> On Apr 21, 2011, at 8:07 AM, Ruben Van Boxem wrote:
>
> > I noticed a big blob of ugly code in InitHeaderSearch.cpp, especially
> when MinGW is involved. Aside from its atrocity, it assumes that MinGW is
> installed in c:\..., which is not true for my system (and may not be true
> for others as well).
> >
> > I would propose to change this hackery to a single (set of) path(s)
> deduced from the location of the gcc executable used to link the Clang
> generated object files together.
> >
> > Two things are required for this to work:
> > 1. Clang needs to be able to locate the gcc executable (from PATH),
> including version and target info (for step 2)
> > 2. Relative paths need to be generated from that location.
> >
> > Is this a sensible way of solving the problem?
>
> Perhaps. This is a longstanding issue across platforms; probing GCC at
> ./configure time to find the paths it uses would probably be most effective.
>
>        - Doug
>

I was thinking of a runtime search, to allow Clang to be moved/installed in
Windows. Not the most efficient, but workable untill it's not necessary
anymore (ie Clang grows independent of GCC).

Ruben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20110422/fcf25560/attachment.html>