trcrsired wrote: > @trcrsired Can you try https://crates.io/crates/xwin? (and use it with > `--use-winsysroot-style`) This achieves the same effect as what you're doing > here it seems. In practical terms, one can then do `clang-cl /winsysroot ...` > as usual from Linux. Chromium does cross-compilation along the same lines > (https://chromium.googlesource.com/chromium/src/+/lkgr/docs/win_cross.md)
Thanks for replying. xwin that project is another issue. Since it is mainly for rust. It only deals with the library part, not the headers part, which just fail to compile even things like go standard library. That project really does not work. https://github.com/Jake-Shadle/xwin/issues/138 >From my understanding, clang-cl is supposed to deal with cl compatibility >while the raw clang/clang++ is supposed to be exactly the same behavior with >gcc. just like, we do clang++ -o hello.exe hello.cc -O3 >--target=x86_64-windows-msvc, not clang++ /EHsc /Ox hello.cc >/target:x86_64-windows-msvc. In that sense, why won't --sysroot have the same >behavior as GCC one? https://github.com/llvm/llvm-project/pull/96417 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
