-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using WASI SDK in CMake build on Windows #179
Comments
Btw, is there a reason why the Windows release still has |
Indeed, it looks like it was mistake to remove the CMAKE_SYSROOT from the version of Interestingly enough the very latest change should remove the need for explicit sysroot: 14d7b78. If we wan't for that change then we would need to add it back, but since 14d7b78 landed, the next release won't need it. |
Just tried 14d7b78 and indeed it fixes the issue. So I'm closing and hoping for a new release soon 😄 |
Do we know when a new release might have these changes @sbc100 ? Alternatively are there any docs / hints for making a windows build? |
A new llvm due to out tomorrow (Sept 21) so we should probably do wasi-sdk release as soon as that happens. In them an time I think you should be able to add |
I'm trying to use the Windows release of WASI SDK to build a WASI module using CMake, but I'm not quite able to wrap my head around this. Maybe someone can point out what I'm doing wrong here.
I have a simple CMakeLists.txt:
And try to build as follows:
Which fails:
So it seems clang isn't picking up the sysroot. I dug around a bit and found these settings in an older version of
wasi-sdk.cmake
:Adding these to my
share\cmake\wasi-sdk.cmake
makes the build succeed. But these settings were removed in #161, so presumably they shouldn't be necessary anymore?The text was updated successfully, but these errors were encountered: