llvm添加自动化脚本

[Dozingfiretruck]

你在什么场景下需要该功能？

llvm新版本发布时候自动添加新版，类似sdl那样

描述可能的解决方案

类似sdl那样

描述你认为的候选方案

No response

其他信息

No response

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Title: llvm add automation script

In what scenario do you need this function?

When a new version of llvm is released, a new version is automatically added, similar to sdl

describe possible solutions

like sdl

Describe what you think is a candidate

No response

other information

No response

[waruqi]

目前不支持自动更新，更新版本，你可以提 pr 过来。。

sdl 那个也是别人本地搞的自动更新脚本提交的。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Automatic update is currently not supported, you can submit a pr for an updated version. .

The sdl one was also submitted by someone else's local automatic update script.

[Dozingfiretruck]

目前不支持自动更新，更新版本，你可以提 pr 过来。。

sdl 那个也是别人本地搞的自动更新脚本提交的。

我提交了llvm 16.0.6的pr，但是实际下载并没有从 https://github.com/xmake-mirror/llvm-windows/releases 下载对应的 clang+llvm-16.0.6-win64.zip，而是从 https://github.com/xmake-mirror/build-artifacts/releases 下载 windows-x64-vc142-bf90dad5e32842c68f41604d3332224b.7z 这是为什么呢？有什么区别？后者我看名字里有VC142而且编译报错和MSVC一样

[waruqi]

build-artifacts 是预编译包。。xmake-repo 仓库更新，会自动触发 ci 编译打包上传到 build-artifacts 。会优先走这个，，如果 原始包本来就是 二进制包，那么也顶多就是重新压缩打包下，走哪个 没有本质区别。。里面还是原始包的那点东西

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

build-artifacts are precompiled packages. . The update of the xmake-repo warehouse will automatically trigger ci compilation and packaging to be uploaded to build-artifacts. This will be given priority. If the original package is originally a binary package, then at most it will be recompressed and packaged. There is no essential difference in which one to use. . It's still in the original bag.

[Dozingfiretruck]

build-artifacts 是预编译包。。xmake-repo 仓库更新，会自动触发 ci 编译打包上传到 build-artifacts 。会优先走这个，，如果 原始包本来就是 二进制包，那么也顶多就是重新压缩打包下，走哪个 没有本质区别。。里面还是原始包的那点东西

了解了，还有个问题，build-artifacts上的命名为何有vc142呢？是win上的llvm对MSVC有什么依赖么？

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

build-artifacts are precompiled packages. . The update of the xmake-repo warehouse will automatically trigger ci compilation, packaging and uploading to build-artifacts. This will be given priority. If the original package is originally a binary package, then at most it will be recompressed and packaged. There is no essential difference in which one to use. . It's still in the original bag.

Understood, there is another question, why is the name on build-artifacts vc142? Does llvm on win have any dependence on MSVC?

[waruqi]

build-artifacts 是预编译包。。xmake-repo 仓库更新，会自动触发 ci 编译打包上传到 build-artifacts 。会优先走这个，，如果 原始包本来就是 二进制包，那么也顶多就是重新压缩打包下，走哪个 没有本质区别。。里面还是原始包的那点东西

了解了，还有个问题，build-artifacts上的命名为何有vc142呢？是win上的llvm对MSVC有什么依赖么？

主要用于库的预编译，toolset 的版本，有向下abi兼容的需要。。。对工具链无所谓 不用管它

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

build-artifacts are precompiled packages. . The update of the xmake-repo warehouse will automatically trigger ci compilation and packaging to be uploaded to build-artifacts. This will be given priority. If the original package is originally a binary package, then at most it will be recompressed and packaged. There is no essential difference in which one to use. . It's still in the original bag.

Understood, there is another question, why is the name on build-artifacts vc142? Does llvm on win have any dependence on MSVC?

It is mainly used for library precompilation and toolset version, which requires backward ABI compatibility. . . Don't care about the toolchain, leave it alone

[Dozingfiretruck]

windows下是否可以直接使用此包不必单独处理 https://github.com/llvm/llvm-project/releases/tag/llvmorg-18.1.8

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Can this package be used directly under windows without having to deal with it separately? https://github.com/llvm/llvm-project/releases/tag/llvmorg-18.1.8