-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
6764e09
commit 1c17757
Showing
6 changed files
with
453 additions
and
260 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,13 @@ | ||
# DuckDB C API Headers | ||
This directory contains the C API headers of DuckDB. These headers should generally match the `MINIMUM_DUCKDB_VERSION` | ||
This directory contains the C API headers of DuckDB. These headers should generally match the `TARGET_DUCKDB_VERSION` | ||
that is specified in the `Makefile`. Note that these headers can be updated automatically | ||
to match the `MINIMUM_DUCKDB_VERSION` makefile variable by running (assuming the default makefile setup): | ||
to match the `TARGET_DUCKDB_VERSION` makefile variable by running (assuming the default makefile setup): | ||
|
||
```shell | ||
make update_duckdb_headers | ||
``` | ||
|
||
Of course manually updating the headers is also fine, just make sure that the headers are always from the same | ||
DuckDB version and that they are not from a later release of DuckDB than is specified in the `MINIMUM_DUCKDB_VERSION` | ||
build variable. Using headers from an older version than `MINIMUM_DUCKDB_VERSION` is allowed, but you probably don't want | ||
DuckDB version and that they are not from a later release of DuckDB than is specified in the `TARGET_DUCKDB_VERSION` | ||
build variable. Using headers from an older version than `TARGET_DUCKDB_VERSION` is allowed, but you probably don't want | ||
that. |
Oops, something went wrong.