[cfe-dev] VS2015 Update 3 type_traits Header Issues
Reid Kleckner via cfe-dev
cfe-dev at lists.llvm.org
Wed Jul 13 08:38:03 PDT 2016
I didn't think -resource-dir was a driver option, it's a -cc1 option. I'm
not sure how to set it in the context of a clang tool, but there should be
a way to get it through. Worst case you can use -Xclang.
Sent from phone
On Jul 12, 2016 5:48 PM, "Daniel Dilts via cfe-dev" <cfe-dev at lists.llvm.org>
> I am uncertain on how to proceed with this. immintrin.h (as provided by
> clang) is in the directory specified by -resource-dir. In order for clang
> (and tools based on it) to handle the Windows header files, it must use
> these files or you get lots of errors parsing Microsoft's standard library
> Since the -resource-dir flag doesn't appear to be valid anymore (but is
> still generated by clang), what is the method to cause clang to use the
> files in this directory?
> On Thu, Jun 30, 2016 at 11:05 AM, Daniel Dilts <diltsman at gmail.com> wrote:
>> My command line roughly looks like this:
>> MyTool.exe D:\Source1.cpp D:\Source2.cpp -- --driver-mode=cl
>> -Wno-c99-extensions -Wno-microsoft-enum-value -Wno-undefined-internal
>> -fms-compatibility-version=19 -EHsc
>> My code to parse the command line arguments is this:
>> CommonOptionsParser optionsParser(argc, const_cast<const char**>(argv),
>> The only places where the code mentions -resource-dir are in Clang or
>> LLVM code.
>> On Thu, Jun 30, 2016 at 8:42 AM, Hans Wennborg <hans at chromium.org> wrote:
>>> On Wed, Jun 29, 2016 at 5:46 PM, Daniel Dilts <diltsman at gmail.com>
>>> > I am now building my tool against trunk. I am seeing the following
>>> > which I had a long time ago and I seem to remember that the tool had
>>> to know
>>> > about where the Clang build copied certain files. Is there some other
>>> > project that needs to be built to make this work? I have already set
>>> > clang-headers as a dependency.
>>> > CUSTOMBUILD : warning : unknown argument ignored in clang-cl:
>>> > '-resource-dir=D:\Some\Directory\lib\clang\3.9.0'
>>> This looks like the problem. I don't know where this flag is coming
>>> from, but does it work better if you remove the '='?
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev