Skip to content
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

rust-analyzer panicks on duckdb_entrypoint_c_api due to lack of the envvars #15

Open
yutannihilation opened this issue Feb 22, 2025 · 0 comments · May be fixed by duckdb/duckdb-rs#472 or duckdb/duckdb-rs#473

Comments

@yutannihilation
Copy link
Contributor

#[duckdb_entrypoint_c_api()] macro requires DUCKDB_EXTENSION_MIN_DUCKDB_VERSION and DUCKDB_EXTENSION_NAME envvars if used without arguments. When running make debug, these are provided form the Makefile, so the build succeeds. However, rust-analyzer doesn't know the values.

Can this be solved? I think one option is to add these lines to .cargo/config.toml. If this looks good, I can create a pull request.

[env]
DUCKDB_EXTENSION_MIN_DUCKDB_VERSION = "v1.2.0"
DUCKDB_EXTENSION_NAME = "rusty_quack"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant