Skip to content

Remove the last relative include path (#39) - #781

Merged
ddehilster merged 1 commit into
masterfrom
chore/last-relative-include-39
Oct 14, 2026
Merged

ddehilster merged 1 commit into
masterfrom
chore/last-relative-include-39

Conversation

@ddehilster

Copy link
Copy Markdown
Member

Closes #39.

include/Api/lite/inline.h included "../prim/unicu.h". That was the only relative include left in lite, cs, src, nlp and include. Every engine build, and the compile-libs package used by compiled analyzers, has include/Api as an include root. So it's now "prim/unicu.h", the same as lite/fn.cpp, lite/str.h and lite/tok.cpp. No behaviour changes, so there's no version bump.

The rest of #39 should not be done, I think. The issue also suggests moving headers next to their .cpp files and removing the include paths from CMake. But include/Api is the engine's public header tree. It ships in nlpengine-compile-libs, and generated analyzer code and the Python package are built against those include roots. Flattening it would break them.

Testing: the engine builds locally. CI covers Linux, macOS, the Python-package-style builds, and the Windows step that compiles an analyzer against the packaged headers.

🤖 Generated with Claude Code

include/Api/lite/inline.h included "../prim/unicu.h"; every build and the
compile-libs package have include/Api as an include root, so it is now
"prim/unicu.h", like the other files that include it. No relative include
paths remain.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ddehilster
ddehilster merged commit d7e00d4 into master Oct 14, 2026
7 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.

Remove relative include paths from cpp files

1 participant