[cfe-dev] Clang on Windows targeting gcc requirements

[Nikola Smiljanic]

>
>
> Why is it "uncommitted" and not a part of clang source ?
>
>
Because it hasn't been reviewed.


> What does supporting mingw-64 have to do with the hardcoded path c:\mingw ?
>
>
Clang driver has no official support for mingw. Just a bunch of hardcoded
paths in the current driver. They break whenever new version of mingw is
released as version numbers are hardcoded as well. They also don't work for
mingw-w64 which as far as I know is more active than the original mingw
project.


> I do not understand how one obtains a patch from the link given, how one
> applies the patch, and to what the patch is supposed to be applied ( but I
> assume the patch is applied to the clang source somewhere ).
>
>
Download raw diff will give you a patch file. You apply it to your local
clang directory.



>
>>
>> 2015-06-26 0:13 GMT+03:00 Edward Diener
>> <eldlistmailingz at tropicsoft.com
>> <mailto:eldlistmailingz at tropicsoft.com>>:
>>
>>     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=-ZW8tznEmhb5NHese2XpJkBMuo2l_Omp4pNY90r31gU&s=H5rNcz_aIhE0PghyOY7-YGlv69ay3I3K9Ce6FABMqLI&e=
>> >
>>         <
>> 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>
>>         <mailto: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 ?
>>
>>
>>     _______________________________________________
>>     cfe-dev mailing list
>>     cfe-dev at cs.uiuc.edu
>>     <mailto:cfe-dev at cs.uiuc.edu>
>>     http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>>
>>
>>
>>
>> _______________________________________________
>> cfe-dev mailing list
>> cfe-dev at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>>
>>
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20150626/49d99a4e/attachment.html>