[cfe-dev] VS2015 Update 3 type_traits Header Issues

Daniel Dilts via cfe-dev cfe-dev at lists.llvm.org
Tue Jul 12 17:48:28 PDT 2016

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),
> gMyToolCategory);
> 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> wrote:
>> > I am now building my tool against trunk.  I am seeing the following
>> errors,
>> > 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 '='?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20160712/8a588dde/attachment.html>

More information about the cfe-dev mailing list