blocks|key|1082493|text|最后，我找到了一个带有所需的光辉GitHub回购平台工具集的MSBuild，将LLVM+clang5.0.0集成到VisualStudio2017中。按照自述文件的说明，您将有两个新的平台工具集LLVM-vs2017和LLVM-vs2017_xp。问题解决了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|1082494|更新|1082495|我创建了一个更新为LLVM6.0.0的分叉，并通过提供LLVM/clang的包含路径和库路径提供了更好的集成。|1082496|感谢罗依，他意识到原来的.prop文件是为LLVM5.0显式定制的，它没有添加适当的lib+(+$(LLVMInstallDir)\lib)和include+($(LLVMInstallDir)\lib\clang\6.0.0\include)文件夹。|1082497|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/arves100/llvm-vs2017-integration|1|https://github.com/plasmacel/llvm-vs2017-integration|2|https://stackoverflow.com/users/195787/royi^0|12|Z|2P|B|31|E|E|A|0|0|0|2|0|J|2|1|0|C|5|16|3|1C|L|1Z|7|28|15|2|2|2|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|D]|$9|13|A|14|B|D]]|E|@$9|15|A|16|1|17]]|F|$]]|$1|G|3|H|5|6|7|18|8|@$9|19|A|1A|B|C]]|E|@]|F|$]]|$1|I|3|J|5|6|7|1B|8|@]|E|@$9|1C|A|1D|1|1E]]|F|$]]|$1|K|3|L|5|6|7|1F|8|@$9|1G|A|1H|B|D]|$9|1I|A|1J|B|D]|$9|1K|A|1L|B|D]|$9|1M|A|1N|B|D]|$9|1O|A|1P|B|D]]|E|@$9|1Q|A|1R|1|1S]]|F|$]]|$1|M|3|-4|5|6|7|1T|8|@]|E|@]|F|$]]]|N|$O|$5|P|Q|R|F|$S|T]]|U|$5|P|Q|R|F|$S|V]]|W|$5|P|Q|R|F|$S|X]]]]

Finally, I found a <a href="https://github.com/arves100/llvm-vs2017-integration" rel="nofollow noreferrer">brilliant GitHub repo</a> with the required MSBuild platform toolsets which integrates LLVM clang 5.0.0 into Visual Studio 2017. After following the instructions of the README file, you will have two new platform toolsets <code>LLVM-vs2017</code> and <code>LLVM-vs2017_xp</code>. Problem solved.

Update

I made a <a href="https://github.com/plasmacel/llvm-vs2017-integration" rel="nofollow noreferrer">fork</a> which is updated for LLVM 6.0.0 and provides better integration by providing include and library paths of LLVM/clang.

Thanks to <a href="https://stackoverflow.com/users/195787/royi">Royi</a>, who realized that the original <code>.prop</code> files are explicitly tailored for LLVM 5.0 and it misses adding the proper <code>lib</code> (<code>
$(LLVMInstallDir)\lib</code>) and <code>include</code> (<code>$(LLVMInstallDir)\lib\clang\6.0.0\include</code>) folders.

blocks|key|924717|text|它需要一些只随C%2B%2B+v140工具集附带的msbuild目标，VS+2017默认只安装v141工具集。如果您打开VS+2017安装程序，找到v140工具集的复选框并安装它，那么正确的C%2B%2B+msbuild目标将可用，并且会正常工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|924718|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It requires some msbuild targets that only ship with the C++ v140 toolset, and VS 2017 only installs the v141 toolset by default. If you open the VS 2017 installer, find the checkbox for the v140 toolset and install that then the right C++ msbuild targets will be available and the thing will work.

blocks|key|2639891|text|LLVM项目现在通过https://marketplace.visualstudio.com/items?itemName=LLVMExtensions.llvm-toolchain显式支持VisualStudio2017|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2639892|entityMap|0|LINK|mutability|MUTABLE|url|https://marketplace.visualstudio.com/items?itemName=LLVMExtensions.llvm-toolchain^0|A|29|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

The LLVM project now explicitly supports Visual Studio 2017 via <a href="https://marketplace.visualstudio.com/items?itemName=LLVMExtensions.llvm-toolchain" rel="nofollow noreferrer">https://marketplace.visualstudio.com/items?itemName=LLVMExtensions.llvm-toolchain</a>

blocks|key|1082398|text|我是一个使用LLVM技术的新手，我使用的是Visual扩展。它们有一个设置页面，您可以在其中安装>=+(所有版本的LLVM+4.0)。之后，通过使用VS工具栏中的扩展按钮，您可以自由地应用clang、编译或整理代码现代化(这是我最欣赏的)。这样您就不需要配置任何东西了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1082399|更新|offset|length|style|BOLD|1082400|打开扩展设置并从顶部选择LLVM页面。在LLVM页面上，您将看到所有受支持的LLVM版本，并在每个版本的右侧看到安装按钮。安装您需要的任何版本。页面底部是一个下拉列表，它允许您选择在安装多个版本时使用的版本。|1082401|在这个博客帖子中，将逐步解释这个特性。|1082402|entityMap|0|LINK|mutability|MUTABLE|url|https://clangpowertools.com/blog/setting-up-llvm.html^0|0|0|2|0|0|3|4|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

I'm a newbie with the LLVM technology and I'm using a Visual Studio extension, Clang Power Tools. They have a settings page from where you can install LLVM (all versions &gt;= 4.0). After that you are free to apply clang compile or tidy with code modernization(this is what I appreciate the most) by using the extension buttons from VS toolbar. In this way you don't need to configure anything.
Update
Open the extension settings and select the LLVM page from the top. On the LLVM page, you'll see all the supported LLVM versions and at the right of each version the install button. Install any version you need. On the bottom of the page is a dropdown that allows you to select what version to use in case you installed multiple versions.
The feature is explained step by step in this <a href="https://clangpowertools.com/blog/setting-up-llvm.html" rel="nofollow noreferrer">blog post</a>

blocks|key|2639738|text|LLVM/Clang现在有了一个更新的修补程序，允许您在VS2017中使用它。但他们仍然不直接支持VS2017。我在LLVM开发人员邮件列表中要求他们更新他们对VS2017的支持，所以希望他们会这么做。如果他们听我的话。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2639739|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

LLVM/Clang now has an updated patch that allows you to use it with VS2017. But they still don't directly support VS2017. I asked on the LLVM developer mailing list for them to update their support for VS2017, so hopefully they'll do it. If they listen to what I said.

blocks|key|924790|text|我已经知道了如何将LLVM+Clang+7.0与Visual+2017更新15.5.6集成起来。v1913完全支持基于PDB的调试，使用最新的LLVM构建。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|924791|例如，link+/DEBUG:GHASH；clang+-mllvm+-发射-代码视图-ghash-节标志到clang.|924792|这是一个三步走的过程。|924793|安装最新的llvm|ordered-list-item|924794|更新VS中的toolset.props、toolset.targets以支持最新的clang|924795|选择用于构建C/C%2B%2B或其他lang项目的新工具集|924796|截至VisualStudio2017更新15.4.5，微软“实验性”Clang+C2不再工作。因此，需要使用上述修复来编译具有完全PDB+(不仅仅是CodeView+/Z7限制)可调试器的代码。这也成为一个更完整的套件，用于跨平台构建的可移植性测试，因为您可以使用从clang编译器前端到LLVM代码end后端和LLVM链接器的所有LLVM组件为windows构建和PDB调试。|924797|干杯，大卫|924798|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|V|8|@]|9|@]|A|$]]|$1|I|3|J|5|H|7|W|8|@]|9|@]|A|$]]|$1|K|3|L|5|H|7|X|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Y|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Z|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|R|$]]

I have figured out how to integrate LLVM Clang 7.0 with Visual Studio 2017 update 15.5.6. v1913 with full support for PDB based debugging using the latest LLVM builds.

i.e., lld-link /DEBUG:GHASH; clang-cl -mllvm -emit-codeview-ghash-section flag to clang-cl.

It is a three step process.

<ol>
<li>Install latest llvm</li>
<li>Update the toolset.props, toolset.targets in VS to support latest clang</li>
<li>Select the new toolset to use for building your C/C++ or other lang project</li>
</ol>

As of Visual Studio 2017 update 15.4.5 the Microsoft "experimental" Clang C2 no longer works. Thus, the above fixes are necessary to use clang to compile code that has full PDB (not just CodeView /Z7 limited) debuggability. This also now becomes a more complete suite for portability testing cross-platform builds since you can build and PDB debug for windows using all LLVM components from the clang compiler front end to the LLVM codegen backend and LLVM linker.

Cheers, David

blocks|key|2639789|text|查看2018年1月9日http://planet.clang.org/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2639790|看看“试试吧！”一节：|2639791|如果您今天已经在Windows上使用clang和link，那么您可以尝试这一点。启用此功能需要两个标志，一个用于编译器，另一个用于链接器:为了使编译器能够发射.debug$H部分，您需要将无文档的-mllvm+-emit-codeview-ghash-section标志传递给clang(这个标志在将来被认为是稳定的，并且足够好，可以默认打开)。要告诉link使用这些信息，您需要将/DEBUG:GHASH传递给lld。|blockquote|style|BOLD|CODE|2639792|您只需要在您的-mllvm+-emit-codeview-ghash-section项目“命令行:附加选项”区域中传递c%2B%2B标志，或者将它们直接放在您在C:\Program+Files+(x86)\Microsoft+Visual+Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Platforms\Win32\PlatformToolsets\LLVM-vs2017或C:\Program+Files+(x86)\Microsoft+Visual+Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Platforms\x64\PlatformToolsets\LLVM-vs2017中创建的"toolset.props“文件中。|2639793|关键是在添加这些cli选项时，您要告诉clang发出调试信息，即lld+(又名link)将理解并使用这些信息来生成完全填充的PDBE+227文件。而不是在2018年1月09日LLVM7.0下降之前所做的有限的。|2639794|toolset.targets：(任何版本)|2639795|<Project+ToolsVersion="14.1"+
xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
++<Import+Project="$(VCTargetsPath)\Microsoft.CppCommon.targets"+/>
</Project>|code-block|syntax|javascript|2639796|toolset.props：(Win32版本)|2639797|<Project+xmlns="http://schemas.microsoft.com/developer/msbuild/2003">++
++<Import+Project="$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v141\Microsoft.Cpp.$(Platform).v141.props"+Condition="Exists('$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v141\Microsoft.Cpp.$(Platform).v141.props')"/>
++<Import+Project="$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v141\Toolset.props"+Condition="Exists('$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v141\Toolset.props')"/>

++<PropertyGroup>
++++<LLVMInstallDir>$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\LLVM\LLVM)</LLVMInstallDir>
++++<LLVMInstallDir+Condition="'$(LLVMInstallDir)'+==+''">$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LLVM\LLVM)</LLVMInstallDir>
++++<ExecutablePath>$(LLVMInstallDir)\msbuild-bin;$(ExecutablePath)</ExecutablePath>
++++<LibraryPath>$(LLVMInstallDir)\lib\clang\7.0\lib\windows;$(LibraryPath)</LibraryPath>
++</PropertyGroup>

++<ItemDefinitionGroup>
++++<ClCompile>
++++++
++++++<ProgramDataBaseFileName></ProgramDataBaseFileName>
++++++
++++++<AdditionalOptions>-m32+-fmsc-version=1913+%25(AdditionalOptions)</AdditionalOptions>
++++</ClCompile>
++</ItemDefinitionGroup>
</Project>|2639798|对于x64，将-m32更改为-m64|2639799|p.p.s.，我还启用了Microsofts和ARM64编译器来构建本机Windows-10+ARM应用程序(不是UWP现代-com-垃圾软件)。但是，到目前为止，我还没有对clang源代码进行足够的挖掘，无法正确地为ARM配置类似于-m32和-m64为Intel代码-gen所做的类似配置。|2639800|见以下文章：|2639801|http://pete.akeo.ie/2017/05/compiling-desktop-arm-applications-with.html|unordered-list-item|2639802|https://www.theverge.com/2017/12/5/16737288/microsoft-windows-10-qualcomm-arm-laptops-launch|2639803|https://wiki.winehq.org/ARM|2639804|entityMap|0|LINK|mutability|MUTABLE|url|http://planet.clang.org/|1|2|3^0|B|O|0|0|0|I|5|O|4|27|8|3U|5|4W|4|2Q|Z|5B|C|0|7|Z|24|3O|5T|3M|0|8|3|J|5|W|3|13|4|1Q|17|1T|5|0|0|M|0|0|0|N|0|0|0|I|7|4|E|4|0|0|42|39|4|3E|4|0|0|6|0|0|20|0|20|1|0|0|2K|0|2K|2|0|0|R|0|R|3|0^^$0|@$1|2|3|4|5|6|7|1O|8|@]|9|@$A|1P|B|1Q|1|1R]]|C|$]]|$1|D|3|E|5|6|7|1S|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|1T|8|@$A|1U|B|1V|I|J]|$A|1W|B|1X|I|J]|$A|1Y|B|1Z|I|J]|$A|20|B|21|I|J]|$A|22|B|23|I|J]|$A|24|B|25|I|K]|$A|26|B|27|I|K]]|9|@]|C|$]]|$1|L|3|M|5|6|7|28|8|@$A|29|B|2A|I|K]|$A|2B|B|2C|I|K]|$A|2D|B|2E|I|K]]|9|@]|C|$]]|$1|N|3|O|5|6|7|2F|8|@$A|2G|B|2H|I|J]|$A|2I|B|2J|I|J]|$A|2K|B|2L|I|J]|$A|2M|B|2N|I|J]|$A|2O|B|2P|I|J]|$A|2Q|B|2R|I|K]]|9|@]|C|$]]|$1|P|3|Q|5|6|7|2S|8|@$A|2T|B|2U|I|J]]|9|@]|C|$]]|$1|R|3|S|5|T|7|2V|8|@]|9|@]|C|$U|V]]|$1|W|3|X|5|6|7|2W|8|@$A|2X|B|2Y|I|J]]|9|@]|C|$]]|$1|Y|3|Z|5|T|7|2Z|8|@]|9|@]|C|$U|V]]|$1|10|3|11|5|6|7|30|8|@$A|31|B|32|I|J]|$A|33|B|34|I|K]|$A|35|B|36|I|K]]|9|@]|C|$]]|$1|12|3|13|5|6|7|37|8|@$A|38|B|39|I|J]|$A|3A|B|3B|I|K]|$A|3C|B|3D|I|K]]|9|@]|C|$]]|$1|14|3|15|5|6|7|3E|8|@$A|3F|B|3G|I|J]]|9|@]|C|$]]|$1|16|3|17|5|18|7|3H|8|@$A|3I|B|3J|I|J]]|9|@$A|3K|B|3L|1|3M]]|C|$]]|$1|19|3|1A|5|18|7|3N|8|@$A|3O|B|3P|I|J]]|9|@$A|3Q|B|3R|1|3S]]|C|$]]|$1|1B|3|1C|5|18|7|3T|8|@$A|3U|B|3V|I|J]]|9|@$A|3W|B|3X|1|3Y]]|C|$]]|$1|1D|3|-4|5|6|7|3Z|8|@]|9|@]|C|$]]]|1E|$1F|$5|1G|1H|1I|C|$1J|1K]]|1L|$5|1G|1H|1I|C|$1J|17]]|1M|$5|1G|1H|1I|C|$1J|1A]]|1N|$5|1G|1H|1I|C|$1J|1C]]]]

Check out January 09, 2018 <a href="http://planet.clang.org/" rel="nofollow noreferrer">http://planet.clang.org/</a>

Look at the "Try it out!" section:

<blockquote>
 If you're already using clang-cl and lld-link on Windows today, you can try this out. There are two flags needed to enable this, one for the compiler and one for the linker:
 To enable the emission of a .debug$H section by the compiler, you will need to pass the undocumented <code>-mllvm -emit-codeview-ghash-section</code> flag to clang-cl (this flag should go away in the future, once this is considered stable and good enough to be turned on by default).
 To tell lld-link to use this information, you will need to pass the <code>/DEBUG:GHASH</code> to lld.
</blockquote>

You just need to pass the <code>-mllvm -emit-codeview-ghash-section</code> flags in either your c++ projects "Command Line:Additional Options" area, or place them directly in the "toolset.props" file that you created in <code>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Platforms\Win32\PlatformToolsets\LLVM-vs2017</code> or
<code>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Platforms\x64\PlatformToolsets\LLVM-vs2017</code>.

The key is that in adding those cli options you're telling clang to emit debug information that the lld (aka lld-link) will understand and use to produce fully populated PDB files. Not the limited ones it made prior to the Jan 09, 2018 drops of LLVM 7.0.

toolset.targets: (any version)

<pre><code>&lt;Project ToolsVersion="14.1" 
xmlns="http://schemas.microsoft.com/developer/msbuild/2003"&gt;
 &lt;Import Project="$(VCTargetsPath)\Microsoft.CppCommon.targets" /&gt;
&lt;/Project&gt;
</code></pre>

toolset.props: (Win32 version)

<pre><code>&lt;Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003"&gt; 
 &lt;Import Project="$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v141\Microsoft.Cpp.$(Platform).v141.props" Condition="Exists('$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v141\Microsoft.Cpp.$(Platform).v141.props')"/&gt;
 &lt;Import Project="$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v141\Toolset.props" Condition="Exists('$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v141\Toolset.props')"/&gt;

 &lt;PropertyGroup&gt;
 &lt;LLVMInstallDir&gt;$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\LLVM\LLVM)&lt;/LLVMInstallDir&gt;
 &lt;LLVMInstallDir Condition="'$(LLVMInstallDir)' == ''"&gt;$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LLVM\LLVM)&lt;/LLVMInstallDir&gt;
 &lt;ExecutablePath&gt;$(LLVMInstallDir)\msbuild-bin;$(ExecutablePath)&lt;/ExecutablePath&gt;
 &lt;LibraryPath&gt;$(LLVMInstallDir)\lib\clang\7.0\lib\windows;$(LibraryPath)&lt;/LibraryPath&gt;
 &lt;/PropertyGroup&gt;

 &lt;ItemDefinitionGroup&gt;
 &lt;ClCompile&gt;
 &lt;!-- remove the implicit vcxxx.pdb path to avoid rebuilds every time as clang-cl only supports /Z7 --&gt;
 &lt;ProgramDataBaseFileName&gt;&lt;/ProgramDataBaseFileName&gt;
 &lt;!-- Set the value of _MSC_VER to claim for compatibility --&gt;
 &lt;AdditionalOptions&gt;-m32 -fmsc-version=1913 %(AdditionalOptions)&lt;/AdditionalOptions&gt;
 &lt;/ClCompile&gt;
 &lt;/ItemDefinitionGroup&gt;
&lt;/Project&gt;
</code></pre>

For x64, change <code>-m32</code> to <code>-m64</code>

p.p.s., I have also enabled Microsofts ARM and ARM64 compilers for building native Windows-10-ARM apps (not UWP modern-com-junk). But, as yet, I have not done enough digging through the clang sources to properly configure something similar for ARM to what <code>-m32</code> and <code>-m64</code> do for Intel code-gen.

See these articles:

<ul>
<li><a href="http://pete.akeo.ie/2017/05/compiling-desktop-arm-applications-with.html" rel="nofollow noreferrer">http://pete.akeo.ie/2017/05/compiling-desktop-arm-applications-with.html</a></li>
<li><a href="https://www.theverge.com/2017/12/5/16737288/microsoft-windows-10-qualcomm-arm-laptops-launch" rel="nofollow noreferrer">https://www.theverge.com/2017/12/5/16737288/microsoft-windows-10-qualcomm-arm-laptops-launch</a></li>
<li><a href="https://wiki.winehq.org/ARM" rel="nofollow noreferrer">https://wiki.winehq.org/ARM</a></li>
</ul>

The <a href="http://llvm.org/builds/" rel="nofollow noreferrer">official LLVM 4.0 build for Windows</a> integrates with Visual Studio up to Visual Studio 2015. Unfortunately it still doesn't support Visual Studio 2017.

When you try to set the Platform Toolset of a project to <code>LLVM-vs2014</code>, it pops up an error.

Do you know any way to make it work?

<hr>

Update

In 2018, LLVM 6.0 officially still doesn't support integration with Visual Studio 2017 (version 15.X.X), only with the Visual Studio 2015 (version 14.X.X) toolset.

Integrate LLVM Clang 4.x.x / 5.x.x / 6.x.x into Visual Studio 2017

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

与Visual集成到Visual 2015。不幸的是，它仍然不支持Visual 2017。当您尝试将项目的平台工具集设置为LLVM-vs2014时，它会弹出一个错误。你知道有什么办法让它起作用吗？更新2018年，LLVM 6.0官方仍然不支持与Visual 2017 (15.X.X版)的集成，只支持与Visual 2015 (14.X.X版)工具集的集成。

问将LLVM Clang 4.x.x / 5.x.x / 6.x.x集成到Visual 2017中
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将LLVM Clang 4.x.x / 5.x.x / 6.x.x集成到Visual 2017中EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将LLVM Clang 4.x.x / 5.x.x / 6.x.x集成到Visual 2017中
EN