nolange
nolange
i dropped the support of using a system clang/llvm installation. its pretty hard to get right on windows, i am not even sure if its bc if bugs or if...
I added some more stuff in another branch, primary to add some unit tests: https://github.com/nolange/llvm-mingw/commits/new_toolchainfile/ There is a subdirectory `test/cmake/tests` building the existing tests. I am probably biased but this...
> The primary way of using the llvm-mingw tools is via the triple prefixed wrappers - this is easy to set up and use with all build systems, and matches...
> It's relevant to the point whether using toolchain files solves a technical issue (getting the right defaults flags for `-stdlib=libc++` to clang-tidy or similar) or just a convenience issue....
I updated the branch with the CMake Testsuite: https://github.com/nolange/llvm-mingw/commits/new_toolchainfile/ Now should work (almost) out of the Box with Editors supporting CMake Projects. Likely will need to setup the path to...
> I think I can agree that these toolchain files could be useful to some people, even if it is not how I use cmake. So perhaps we can aim...
Did alot more tests, was able to build and later find openssl3 + qt6 via pkgconf and cmake. Needed some fixes.
Hmm, come to think of it - I would really like if those files could be indiscriminately used and abused as templates, without any licensing concerns. Your project has a...
> It's not apache2, it's the ISC license (which is equivalent with simplified BSD and MIT) for the build scripts etc. It's meant as the simplest and least restrictive license...