You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some users have requested Windows support for Kuzu, such as #1311 and #1313. The steps required to support Windows are as follows:
Fix compilation errors for the core library and test cases with MSVC.
Run the test cases, fix any testing error.
Build a dll version for libkuzu and test it with the MSVC toolchain.
Figure out how to build the Python wheel for Windows.
Replace linenoise with another Windows-compatible readline implementation for the shell.
Setup a Windows-based CI runner to ensure the compatibility with Windows for the PRs afterwards.
I worked on Windows support on branch https://github.com/kuzudb/kuzu/tree/windows by attempting fixing all the compilation errors and replace system API calls. However, there is one compilation error regarding template that I did not know how to fix (in src\storage\storage_structure\lists\lists_update_store.cpp). The branch is stale now since a lot of new features were added in version 0.0.3. I no longer have the detailed output from MSVC, but it can be reproduced by checking out the branch and run the build process in Windows PowerShell.
The text was updated successfully, but these errors were encountered:
Some users have requested Windows support for Kuzu, such as #1311 and #1313. The steps required to support Windows are as follows:
libkuzu
and test it with the MSVC toolchain.I worked on Windows support on branch https://github.com/kuzudb/kuzu/tree/windows by attempting fixing all the compilation errors and replace system API calls. However, there is one compilation error regarding template that I did not know how to fix (in
src\storage\storage_structure\lists\lists_update_store.cpp
). The branch is stale now since a lot of new features were added in version 0.0.3. I no longer have the detailed output from MSVC, but it can be reproduced by checking out the branch and run the build process in Windows PowerShell.The text was updated successfully, but these errors were encountered: