[cfe-dev] Clang on Windows targeting gcc requirements

Edward Diener eldlistmailingz at tropicsoft.com
Thu Jun 25 14:13:01 PDT 2015

On 6/25/2015 2:13 PM, Yaron Keren wrote:
> See http://reviews.llvm.org/D5268
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__reviews.llvm.org_D5268&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=CnzuN65ENJ1H9py9XLiRvC_UQz6u3oG6GUNn7_wosSM&m=YgSrUuiAhPt76cF_h_LXb8Mg84W8p9nMvUiL3koHKP4&s=aW_6t6KDGfo5hO6NiTn5Hy9afNhzwfkX-BZHT9PtXmk&e=>

I don't understand what the above link means, or how it is connected to 
my suggestions below.

> 2015-06-25 10:46 GMT+03:00 Edward Diener
> <eldlistmailingz at tropicsoft.com
> <mailto:eldlistmailingz at tropicsoft.com>>:
>     For either the latest clang built from souce on Windows or a binary
>     distribution of clang on Windows it appears that clang expects the
>     supporting gcc include files and lib files to be in the hardcoded
>     directory:
>     c:\mingw
>     and follow the mingw directory structure.
>     1) Can this please be changed in the future so that some environment
>     variable ( maybe CLANG_GCC ) can be set to the gcc installation
>     rather than use a hardcoded path ?
>     2) Can clang be updated to support the mingw-64 directory structure
>     and not just the mingw directory structure ? The mingw-64 distros
>     seem now to be the preferred gcc distributions on Windows and
>     support the latest versions of gcc.
>     Do I need to make these suggestions on the clang bug tracker for the
>     suggestions to be seriously considered ?

More information about the cfe-dev mailing list