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

Output extension to a sub-directory that respect the input mode/feature #1527

Merged
merged 1 commit into from
Dec 12, 2023

Conversation

Y--
Copy link
Contributor

@Y-- Y-- commented Dec 11, 2023

Today, the build_loadable.sh scripts output every extension under loadable_extensions folder.

This PR outputs them under loadable_extensions/$MODE/$FEATURE where MODE and FEATURE are the parameters provided in input to select the source directory (eg. mode=relperf feature=mvp)

That respect the input parameters
Copy link
Collaborator

@carlopi carlopi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I though about and solving this generally (= in duckdb Makefile), with having a postprocessing step where extensions are copied to build/release/extensions/${duckdb_version}/${platform}/${name}.duckdb_extension[.wasm], since that will also allow to use the folder as a local extension directory, basically SET custom_extension_repository='/path/to/folder';

Stuff might move more that direction, but for not this is still more clean.

Thanks.

@Mytherin Mytherin merged commit a85ae61 into duckdb:main Dec 12, 2023
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants