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
When building from source, running the build steps in the following order doesn't create a build directory in tools/shell and tools/python_api, which is unexpected behaviour.
This doesn't work
make extension-release NUM_THREADS=20
make release NUM_THREADS=20
make python NUM_THREADS=20
When run in this order, the extension release directory has a build directory in it, but there is no build directory in the tools/shell and tools/python_api directories as we might expect.
This works
make release NUM_THREADS=20
make python NUM_THREADS=20
make extension-release NUM_THREADS=20
When run in this order, all the required directories have a build directory and I can run the Kùzu CLI, Python client and extensions in both with no issues.
I think there's a flag missing somewhere that causes the build to not work when run as per the order shown in the former case?
Are there known steps to reproduce?
No response
The text was updated successfully, but these errors were encountered:
Kùzu version
master
What operating system are you using?
macOS Sonoma 14.5
What happened?
When building from source, running the build steps in the following order doesn't create a
build
directory intools/shell
andtools/python_api
, which is unexpected behaviour.This doesn't work
When run in this order, the extension release directory has a
build
directory in it, but there is nobuild
directory in thetools/shell
andtools/python_api
directories as we might expect.This works
When run in this order, all the required directories have a
build
directory and I can run the Kùzu CLI, Python client and extensions in both with no issues.I think there's a flag missing somewhere that causes the
build
to not work when run as per the order shown in the former case?Are there known steps to reproduce?
No response
The text was updated successfully, but these errors were encountered: