Arthapz wrote:
i tried it for a while, it work very well ! thx u
https://github.com/llvm/llvm-project/pull/106683
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Arthapz wrote:
observed this today, this should be merge :D
https://github.com/llvm/llvm-project/pull/88404
___
cfe-commits mailing list
cfe-commits@lists.llvm.o
Arthapz wrote:
Ping
https://github.com/llvm/llvm-project/pull/88404
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Arthapz wrote:
> Given we are going to branch clang19 in the end of the month, it is highly
> possible that we can't land sufficient patches before that. Note that even if
> we land this patch before that, the support of modules in clangd is expected
> to very slow for real world applications.
Arthapz wrote:
> The file we're looking for is `modules.json`; Renaming it
> `libc++.modules.json` like `.so` / `.a` file might be a better idea which
> could avoid name clashes when installed in `/usr/lib`.
but i didn't rename it, it was installed like this :/
https://github.com/llvm/llvm-pr
Arthapz wrote:
How do we use this ?
i tried
```
> /opt/llvm-git/usr/bin/clang -std=c++23 -stdlib=libc++
> -print-library-module-manifest-path
```
and
```
> /opt/llvm-git/usr/bin/clang -std=c++23 -stdlib=libc++
> -print-library-module-manifest-path -resource-dir=/opt/llvm-git/usr/lib
```
b
Arthapz wrote:
Oh nice going to try this :)
https://github.com/llvm/llvm-project/pull/66462
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
