VS2022使用指定的LLVM版本

2024-09-04 05:28
文章标签 使用 指定 版本 vs2022 llvm

本文主要是介绍VS2022使用指定的LLVM版本,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

LLVM下载地址:Releases · llvm/llvm-project · GitHub

LLVM/Clang toolsets for Visual Studio 2022, 2019, 2017, 2015, 2013, 2012 and 2010.

GitHub - zufuliu/llvm-utils: LLVM/Clang toolsets for Visual Studio 2022, 2019, 2017, 2015, 2013, 2012 and 2010.

关键就是这个llvm-utils工具了,可以配置VS2022的平台工具集包含LLVM

备用下载地址:llvm-utils

Installation

Please download and install LLVM from Releases · llvm/llvm-project · GitHub or Download LLVM releases.

VS2017\install.bat can be used to install MSBuild script for Visual Studio 2017, 2019 and 2022. (may require Administrator privilege. In Windows 8 or later, you can quickly open an elevated PowerShell prompt by File -> Open Windows PowerShell -> Open PowerShell as Administrator).

Visual Studio 2022

The Platform Toolset is "LLVM for Visual Studio 2022 (LLVM_v143)", "LLVM for Visual Studio 2019 (LLVM_v142)", "LLVM for Visual Studio 2017 (LLVM_v141)" and "LLVM for Visual Studio 2017 - Windows XP (LLVM_v141_xp)".

Assume VS_PATH is your Visual Studio 2020 installation path (e.g: C:\Program Files\Microsoft Visual Studio\2022\Community), please manually copy folders under VS2017 to their target paths.

FolderTarget Path
VS2017\LLVM%VS_PATH%\MSBuild\Microsoft\VC\v170\
VS2017\LLVM_v143%VS_PATH%\MSBuild\Microsoft\VC\v170\Platforms\x64\PlatformToolsets\
VS2017\LLVM_v143%VS_PATH%\MSBuild\Microsoft\VC\v170\Platforms\Win32\PlatformToolsets\
VS2017\LLVM_v143%VS_PATH%\MSBuild\Microsoft\VC\v170\Platforms\ARM64\PlatformToolsets\
VS2017\LLVM_v143%VS_PATH%\MSBuild\Microsoft\VC\v170\Platforms\ARM\PlatformToolsets\
VS2017\LLVM%VS_PATH%\MSBuild\Microsoft\VC\v160\
VS2017\LLVM_v142%VS_PATH%\MSBuild\Microsoft\VC\v160\Platforms\x64\PlatformToolsets\
VS2017\LLVM_v142%VS_PATH%\MSBuild\Microsoft\VC\v160\Platforms\Win32\PlatformToolsets\
VS2017\LLVM_v142%VS_PATH%\MSBuild\Microsoft\VC\v160\Platforms\ARM64\PlatformToolsets\
VS2017\LLVM_v142%VS_PATH%\MSBuild\Microsoft\VC\v160\Platforms\ARM\PlatformToolsets\
VS2017\LLVM%VS_PATH%\MSBuild\Microsoft\VC\v150\
VS2017\LLVM_v141%VS_PATH%\MSBuild\Microsoft\VC\v150\Platforms\x64\PlatformToolsets\
VS2017\LLVM_v141_xp%VS_PATH%\MSBuild\Microsoft\VC\v150\Platforms\x64\PlatformToolsets\
VS2017\LLVM_v141%VS_PATH%\MSBuild\Microsoft\VC\v150\Platforms\Win32\PlatformToolsets\
VS2017\LLVM_v141_xp%VS_PATH%\MSBuild\Microsoft\VC\v150\Platforms\Win32\PlatformToolsets\
VS2017\LLVM_v141%VS_PATH%\MSBuild\Microsoft\VC\v150\Platforms\ARM64\PlatformToolsets\
VS2017\LLVM_v141%VS_PATH%\MSBuild\Microsoft\VC\v150\Platforms\ARM\PlatformToolsets\

Visual Studio 2019

The Platform Toolset is "LLVM for Visual Studio 2019 (LLVM_v142)", "LLVM for Visual Studio 2017 (LLVM_v141)" and "LLVM for Visual Studio 2017 - Windows XP (LLVM_v141_xp)".

Assume VS_PATH is your Visual Studio 2019 installation path (e.g: C:\Program Files (x86)\Microsoft Visual Studio\2019\Community), please manually copy folders under VS2017 to their target paths.

FolderTarget Path
VS2017\LLVM%VS_PATH%\MSBuild\Microsoft\VC\v160\
VS2017\LLVM_v142%VS_PATH%\MSBuild\Microsoft\VC\v160\Platforms\x64\PlatformToolsets\
VS2017\LLVM_v142%VS_PATH%\MSBuild\Microsoft\VC\v160\Platforms\Win32\PlatformToolsets\
VS2017\LLVM_v142%VS_PATH%\MSBuild\Microsoft\VC\v160\Platforms\ARM64\PlatformToolsets\
VS2017\LLVM_v142%VS_PATH%\MSBuild\Microsoft\VC\v160\Platforms\ARM\PlatformToolsets\
VS2017\LLVM%VS_PATH%\MSBuild\Microsoft\VC\v150\
VS2017\LLVM_v141%VS_PATH%\MSBuild\Microsoft\VC\v150\Platforms\x64\PlatformToolsets\
VS2017\LLVM_v141_xp%VS_PATH%\MSBuild\Microsoft\VC\v150\Platforms\x64\PlatformToolsets\
VS2017\LLVM_v141%VS_PATH%\MSBuild\Microsoft\VC\v150\Platforms\Win32\PlatformToolsets\
VS2017\LLVM_v141_xp%VS_PATH%\MSBuild\Microsoft\VC\v150\Platforms\Win32\PlatformToolsets\
VS2017\LLVM_v141%VS_PATH%\MSBuild\Microsoft\VC\v150\Platforms\ARM64\PlatformToolsets\
VS2017\LLVM_v141%VS_PATH%\MSBuild\Microsoft\VC\v150\Platforms\ARM\PlatformToolsets\

Visual Studio 2017

The Platform Toolset is "LLVM for Visual Studio 2017 (LLVM_v141)" and "LLVM for Visual Studio 2017 - Windows XP (LLVM_v141_xp)".

Assume VS_PATH is your Visual Studio 2017 installation path (e.g: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community), please manually copy folders under VS2017 to their target paths.

FolderTarget Path
VS2017\LLVM%VS_PATH%\Common7\IDE\VC\VCTargets\
VS2017\LLVM_v141%VS_PATH%\Common7\IDE\VC\VCTargets\Platforms\x64\PlatformToolsets\
VS2017\LLVM_v141_xp%VS_PATH%\Common7\IDE\VC\VCTargets\Platforms\x64\PlatformToolsets\
VS2017\LLVM_v141%VS_PATH%\Common7\IDE\VC\VCTargets\Platforms\Win32\PlatformToolsets\
VS2017\LLVM_v141_xp%VS_PATH%\Common7\IDE\VC\VCTargets\Platforms\Win32\PlatformToolsets\
VS2017\LLVM_v141%VS_PATH%\Common7\IDE\VC\VCTargets\Platforms\ARM64\PlatformToolsets\
VS2017\LLVM_v141%VS_PATH%\Common7\IDE\VC\VCTargets\Platforms\ARM\PlatformToolsets\

LLVM for Visual Studio 2010, 2012, 2013 and 2015

Assume MB_PATH is the MSBuild path for Visual C++ (e.g.: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0 or C:\Program Files\MSBuild\Microsoft.Cpp\v4.0), please manually copy VS2017\LLVM and related folders under VS2015 to their target paths.

VS2015\install.bat (based on install script for LLVM 6.0.1) can be used to install MSBuild script for Visual Studio 2010, 2012, 2013 and 2015.

Visual Studio 2015

The Platform Toolset is "LLVM for Visual Studio 2015 (LLVM_v140)" and "LLVM for Visual Studio 2015 - Windows XP (LLVM_v140_xp)".

FolderTarget Path
VS2017\LLVM%MB_PATH%\V140\
VS2015\LLVM_v140%MB_PATH%\V140\Platforms\x64\PlatformToolsets\
VS2015\LLVM_v140_xp%MB_PATH%\V140\Platforms\x64\PlatformToolsets\
VS2015\LLVM_v140%MB_PATH%\V140\Platforms\Win32\PlatformToolsets\
VS2015\LLVM_v140_xp%MB_PATH%\V140\Platforms\Win32\PlatformToolsets\

Visual Studio 2013

The Platform Toolset is "LLVM for Visual Studio 2013 (LLVM_v120)" and "LLVM for Visual Studio 2013 - Windows XP (LLVM_v120_xp)".

FolderTarget Path
VS2017\LLVM%MB_PATH%\v120\
VS2015\LLVM_v120%MB_PATH%\v120\Platforms\x64\PlatformToolsets\
VS2015\LLVM_v120_xp%MB_PATH%\v120\Platforms\x64\PlatformToolsets\
VS2015\LLVM_v120%MB_PATH%\v120\Platforms\Win32\PlatformToolsets\
VS2015\LLVM_v120_xp%MB_PATH%\v120\Platforms\Win32\PlatformToolsets\

Visual Studio 2012

The Platform Toolset is "LLVM for Visual Studio 2012 (LLVM_v110)" and "LLVM for Visual Studio 2012 - Windows XP (LLVM_v110_xp)".

FolderTarget Path
VS2017\LLVM%MB_PATH%\v110\
VS2015\x64\LLVM_v110%MB_PATH%\v110\Platforms\x64\PlatformToolsets\
VS2015\x64\LLVM_v110_xp%MB_PATH%\v110\Platforms\x64\PlatformToolsets\
VS2015\Win32\LLVM_v110%MB_PATH%\v110\Platforms\Win32\PlatformToolsets\
VS2015\Win32\LLVM_v110_xp%MB_PATH%\v110\Platforms\Win32\PlatformToolsets\

Visual Studio 2010

The Platform Toolset is "LLVM for Visual Studio 2010 (LLVM_v100)" and "LLVM for Visual Studio 2008 (LLVM_v90)".

FolderTarget Path
VS2017\LLVM%MB_PATH%\
VS2015\x64\LLVM_v100%MB_PATH%\Platforms\x64\PlatformToolsets\
VS2015\x64\LLVM_v90%MB_PATH%\Platforms\x64\PlatformToolsets\
VS2015\Win32\LLVM_v100%MB_PATH%\Platforms\Win32\PlatformToolsets\
VS2015\Win32\LLVM_v90%MB_PATH%\Platforms\Win32\PlatformToolsets\

Install to AppVeyor or GitHub Actions Build Image

Install LLVM on the build image

curl -fsSL -o "LLVM-18.1.0-win64.exe" "https://github.com/llvm/llvm-project/releases/download/llvmorg-18.1.0/LLVM-18.1.0-win64.exe"
LLVM-18.1.0-win64.exe /S

Install from release archives

Archive NameVisual Studio Version
LLVM_VS2017.zip2017, 2019 and 2022
LLVM_VS2010_2015.zip2010, 2012, 2013 and 2015
LLVM_VS2015.zip2015
LLVM_VS2013.zip2013
LLVM_VS2012.zip2012
LLVM_VS2010.zip2010

Examples:

curl -fsSL -o "LLVM_VS2017.zip" "https://github.com/zufuliu/llvm-utils/releases/download/v23.05/LLVM_VS2017.zip"
7z x -y "LLVM_VS2017.zip" >NUL
CALL "LLVM_VS2017\install.bat" 1curl -fsSL -o "LLVM_VS2010_2015.zip" "https://github.com/zufuliu/llvm-utils/releases/download/v23.05/LLVM_VS2010_2015.zip"
7z x -y "LLVM_VS2010_2015.zip" >NUL
CALL "LLVM_VS2010_2015\install.bat" 1

Install from latest main source code

curl -fsSL -o "llvm-utils-main.zip" "https://github.com/zufuliu/llvm-utils/archive/main.zip"
7z x -y "llvm-utils-main.zip" >NUL
CALL "llvm-utils-main\VS2017\install.bat" 1
CALL "llvm-utils-main\VS2015\install.bat" 1

or

git clone -q --depth=1 --branch=main https://github.com/zufuliu/llvm-utils.git c:\projects\llvm-utils
CALL "c:\projects\llvm-utils\VS2017\install.bat" 1
CALL "c:\projects\llvm-utils\VS2015\install.bat" 1

clang-cl for Python 3 distutils

See clang\clang-cl-py3.diff for the changes on hwo to use clang-cl as distutils compiler. After apply these changes, you can build your extension with

python setup.py build --compiler=clang-cl

LLVM Windows Symbolic Link Maker

The huge size of LLVM Windows installation can be reduced dramatically by using Windows symbolic link (see mklink command.

Usage

Just copy llvm\llvm-link.bat to LLVM installation path (e.g.: C:\Program Files\LLVM\), and run it (may require Administrator privilege).

Related Links

  • LLVM Extensions for Visual Studio 2017 in Visual Studio Marketplace, not works for Visual Studio 2019 alone.

  • Original source for MSBuild

    https://github.com/llvm/llvm-project/tree/main/llvm/tools/msbuild

    svn co https://github.com/llvm/llvm-project/trunk/llvm/tools/msbuild msbuild

    svn co https://llvm.org/svn/llvm-project/llvm/trunk/tools/msbuild msbuild

  • Outdated LLVM for Visual Studio 2017 by @WubbaLubba

  • Failed to find MSBuild toolsets directory in LLVM Bugzilla

这篇关于VS2022使用指定的LLVM版本的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/1135119

相关文章

Python使用FastAPI实现大文件分片上传与断点续传功能

《Python使用FastAPI实现大文件分片上传与断点续传功能》大文件直传常遇到超时、网络抖动失败、失败后只能重传的问题,分片上传+断点续传可以把大文件拆成若干小块逐个上传,并在中断后从已完成分片继... 目录一、接口设计二、服务端实现(FastAPI)2.1 运行环境2.2 目录结构建议2.3 serv

Python一次性将指定版本所有包上传PyPI镜像解决方案

《Python一次性将指定版本所有包上传PyPI镜像解决方案》本文主要介绍了一个安全、完整、可离线部署的解决方案,用于一次性准备指定Python版本的所有包,然后导出到内网环境,感兴趣的小伙伴可以跟随... 目录为什么需要这个方案完整解决方案1. 项目目录结构2. 创建智能下载脚本3. 创建包清单生成脚本4

Spring Security简介、使用与最佳实践

《SpringSecurity简介、使用与最佳实践》SpringSecurity是一个能够为基于Spring的企业应用系统提供声明式的安全访问控制解决方案的安全框架,本文给大家介绍SpringSec... 目录一、如何理解 Spring Security?—— 核心思想二、如何在 Java 项目中使用?——

springboot中使用okhttp3的小结

《springboot中使用okhttp3的小结》OkHttp3是一个JavaHTTP客户端,可以处理各种请求类型,比如GET、POST、PUT等,并且支持高效的HTTP连接池、请求和响应缓存、以及异... 在 Spring Boot 项目中使用 OkHttp3 进行 HTTP 请求是一个高效且流行的方式。

python获取指定名字的程序的文件路径的两种方法

《python获取指定名字的程序的文件路径的两种方法》本文主要介绍了python获取指定名字的程序的文件路径的两种方法,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一定的参考学习价值,需要... 最近在做项目,需要用到给定一个程序名字就可以自动获取到这个程序在Windows系统下的绝对路径,以下

Java使用Javassist动态生成HelloWorld类

《Java使用Javassist动态生成HelloWorld类》Javassist是一个非常强大的字节码操作和定义库,它允许开发者在运行时创建新的类或者修改现有的类,本文将简单介绍如何使用Javass... 目录1. Javassist简介2. 环境准备3. 动态生成HelloWorld类3.1 创建CtC

使用Python批量将.ncm格式的音频文件转换为.mp3格式的实战详解

《使用Python批量将.ncm格式的音频文件转换为.mp3格式的实战详解》本文详细介绍了如何使用Python通过ncmdump工具批量将.ncm音频转换为.mp3的步骤,包括安装、配置ffmpeg环... 目录1. 前言2. 安装 ncmdump3. 实现 .ncm 转 .mp34. 执行过程5. 执行结

Java使用jar命令配置服务器端口的完整指南

《Java使用jar命令配置服务器端口的完整指南》本文将详细介绍如何使用java-jar命令启动应用,并重点讲解如何配置服务器端口,同时提供一个实用的Web工具来简化这一过程,希望对大家有所帮助... 目录1. Java Jar文件简介1.1 什么是Jar文件1.2 创建可执行Jar文件2. 使用java

C#使用Spire.Doc for .NET实现HTML转Word的高效方案

《C#使用Spire.Docfor.NET实现HTML转Word的高效方案》在Web开发中,HTML内容的生成与处理是高频需求,然而,当用户需要将HTML页面或动态生成的HTML字符串转换为Wor... 目录引言一、html转Word的典型场景与挑战二、用 Spire.Doc 实现 HTML 转 Word1

SpringBoot实现不同接口指定上传文件大小的具体步骤

《SpringBoot实现不同接口指定上传文件大小的具体步骤》:本文主要介绍在SpringBoot中通过自定义注解、AOP拦截和配置文件实现不同接口上传文件大小限制的方法,强调需设置全局阈值远大于... 目录一  springboot实现不同接口指定文件大小1.1 思路说明1.2 工程启动说明二 具体实施2