Results of 1 - 7 of about 7 for compiling (0.001 sec.)
- Troubleshoot 11541
- Overview This page collects common issues encountered when using the DuckDB Rust client, together with their workarounds. If you run into a problem that is not covered here, search the client's issue tracker on GitHub. Linking against a Sys
...nly when building an extension. See Write User Defined Functions for how loadable extensions are built and packaged. Cross-Compiling with bundled Cross-compiling with the bundled feature compiles DuckDB's C++ source for the target, so it requires a workin... - https://man.mtool.work/duckdb/2.0/clients/rust/troubleshoot.html
- R 11087
- This page contains instructions for building the R client library. Parallelizing the Build Problem: By default, R compiles packages using a single thread, which causes the build to be slow. Solution: To parallelize the compilation, create o
...c) However, note that, the more threads that are used, the higher the RAM consumption. If the system runs out of RAM while compiling, then the R session will crash.... - https://man.mtool.work/duckdb/2.0/dev/building/r.html
- Troubleshoot 10632
- Overview This page collects common issues encountered when using the DuckDB Go client, together with their workarounds. Because the client uses cgo to embed DuckDB, most build problems are cgo or linker problems. If you run into a problem t
...toolchain. On Debian or Ubuntu, install them with: bash sudo apt-get update && sudo apt-get install build-essential Cross-compiling disables cgo. The Go compiler turns cgo off automatically when cross-compiling. Re-enable it and point at the right cross-... - https://man.mtool.work/duckdb/2.0/clients/go/troubleshoot.html
- Debugging 8360
- The purpose of the tests is to figure out when things break. Inevitably changes made to the system will cause one of the tests to fail, and when that happens the test needs to be debugged. First, it is always recommended to run in debug mod
...e. This can be done by compiling the system using the command make debug . Second, it is recommended to only run the test that breaks. This can be done by... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/debugging.html
- Unofficial and Unsupported Platforms 7906
- Warning The platforms listed on this page are not officially supported. The build instructions are provided on a best-effort basis. Community contributions are very welcome. DuckDB is built and distributed for several platforms with differe
...ux-gnu-g++ -march=rv64gcv_zicsr_zifencei_zihintpause_zvl256b' \ make For more reference information on DuckDB RISC-V cross-compiling, see the mocusez/duckdb-riscv-ci and DuckDB Pull Request #16549 . Known Issues Platform Reported Incorrectly As of version... - https://man.mtool.work/duckdb/2.0/dev/building/unofficial_and_unsupported_platfo...
- Rust Client 6997
- Installation To use the DuckDB Rust client, visit the Rust installation page . The latest stable version of the DuckDB Rust client is 2.0.0. The DuckDB Rust client, duckdb-rs , is an ergonomic wrapper over the DuckDB C API that exposes an i
...e is the simplest way to get started. Without it, the libduckdb-sys crate links against a system DuckDB library instead of compiling one, which is covered in Troubleshoot . To track the latest bindings before they are released on crates.io, depend on the... - https://man.mtool.work/duckdb/2.0/clients/rust/overview.html
- Statically Linking Extensions 6997
- This page is for client and binding authors, and for anyone who embeds libduckdb in their own application. It describes how statically linking extensions changed in DuckDB 2.0 and what builders on top of DuckDB need to do. This change is in
..._extension.a libjson_extension.a libicu_extension.a The list of extensions to link in is now chosen when linking, not when compiling. As a follow-up, the extension loader and the built-in httplib also became opt-in at link time ( duckdb#26188 ). Two aspec... - https://man.mtool.work/duckdb/2.0/dev/building/linking_extensions.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work