andrew/libakstdlib
1
0
Fork 0
Code Issues 26 Pull Requests Actions Packages Projects Releases Wiki Activity

libakerror does not namespace its coverage target when embedded #4

New Issue
Open
opened 2026-08-02 18:53:17 -04:00 by tachikoma · 0 comments
tachikoma commented 2026-08-02 18:53:17 -04:00
Collaborator
Copy Link

Source: TODO.md §1.3 (at 669b2b3)

deps/libakerror/CMakeLists.txt:172 versus :189 -- it namespaces mutation
and not coverage.

Consequence here. A -DAKSL_COVERAGE=ON top-level build fails to configure at
all: "another target with the same name already exists". CMakeLists.txt
shadows add_custom_target for the duration of the add_subdirectory() call and
renames the dependency's to akerror_coverage.

What closing it would touch. Apply the same
CMAKE_SOURCE_DIR STREQUAL CMAKE_CURRENT_SOURCE_DIR test upstream that the
mutation target already has; then delete the shadow here, which sits directly
above the add_test shadow and shares its comment.

Not fixable from inside this repository.

Files: deps/libakerror/CMakeLists.txt:172,189, CMakeLists.txt

Filed by Tachikoma (Claude Code, Opus 5, 1M context)

**Source:** TODO.md §1.3 (at 669b2b3) `deps/libakerror/CMakeLists.txt:172` versus `:189` -- **it namespaces `mutation` and not `coverage`.** **Consequence here.** A `-DAKSL_COVERAGE=ON` top-level build fails to configure at all: *"another target with the same name already exists"*. `CMakeLists.txt` shadows `add_custom_target` for the duration of the `add_subdirectory()` call and renames the dependency's to `akerror_coverage`. **What closing it would touch.** Apply the same `CMAKE_SOURCE_DIR STREQUAL CMAKE_CURRENT_SOURCE_DIR` test upstream that the `mutation` target already has; then delete the shadow here, which sits directly above the `add_test` shadow and shares its comment. Not fixable from inside this repository. **Files:** `deps/libakerror/CMakeLists.txt:172,189`, `CMakeLists.txt` --- Filed by Tachikoma (Claude Code, Opus 5, 1M context)
tachikoma added this to the 0.3.0 milestone 2026-08-02 18:53:17 -04:00
tachikoma added the packagingblast-radius:mediumstatus::grooming labels 2026-08-02 18:53:17 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abi-break
Cannot land without a soname bump
 api-gap
A caller cannot express something
 blast-radius:high
Ordering: highest blast radius
 blast-radius:low
Ordering: lowest blast radius
 blast-radius:medium
Ordering: middling blast radius
 defect
Wrong behaviour reachable from the public API
 design-decision
Needs a decision written down before code
 docs
Documentation, comments, AGENTS.md
 hygiene
Style, dead code, consistency
 packaging
Build, install, pkg-config, CMake config
 performance
Has a measurement behind it
 status::blocked
Waiting on something else -- a decision, a dependency, or another issue
 status::grooming
Not yet worked out: scope, approach or priority still being settled
 status::ready
Understood well enough to start: scope and approach are settled
 test-coverage
A gap in the suites, not a defect
No Label blast-radius:medium packaging status::grooming
Milestone
No items
No Milestone 0.3.0
Projects
Clear projects
No project
Assignees
Clear assignees
tachikoma andrew
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: andrew/libakstdlib#4
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?