duckdb / duckdb/extension-template
vcpkg with CMake's target_link_libraries
- Dominant language
- Python
- Stars
- 290
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
This does not actually link libraries. See [duckdb-zlib](https://github.com/mcolosimo-p4/duckdb-zlib)
```
eERNS_6VectorE]+0x5b6): undefined reference to `zlibVersion'
extension/quack/libquack_extension.a(quack_extension.cpp.o):quack_extension.cpp:(.text._ZN6duckdb25QuackZlibVersionScalarFunERNS_9DataChunkERNS_15ExpressionStateERNS_6VectorE[_ZN6duckdb25QuackZlibVersionScalarFunERNS_9DataChunkERNS_15ExpressionStateERNS_6VectorE]+0xcc5): more undefined references to `zlibVersion' follow
collect2: error: ld returned 1 exit status
```
I was able to link zlib with a simple vcpkg and CMake project so it works.
We are adding it to `LOADABLE_EXTENSION_NAME` but probably need it for `TARGET_NAME` which generates this message:
```
Cannot specify link libraries for target "quack" which is not built by this project.
```
This is probably related to Issue #118
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the CMake configuration that defines LOADABLE_EXTENSION_NAME and TARGET_NAME, then compare its target_link_libraries usage with the simple vcpkg/CMake project referenced in the issue. Reproduce the extension link and verify that zlibVersion resolves without the “target not built by this project” error, using Issue #118 as related context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100