Resolve meos_catalog.c through MDB_SRC_ROOT for the installed-headers path#74
Merged
estebanzimanyi merged 1 commit intoJul 23, 2026
Conversation
… path The object-model resolver returns the meos/src directory only when a source tree sits beside the headers. On the installed-headers build path the headers carry no source, so it returns none and the type-relation registry drops out — even though the provisioning checks out the full repository under MDB_SRC_ROOT. Locate meos_catalog.c from the resolved source root when present, otherwise from MDB_SRC_ROOT/meos/src, so the registry attaches on both build paths. A test covers the MDB_SRC_ROOT fallback, and the degrade test clears the env var so it still proves honest absence when neither source is available.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The object-model resolver returns the
meos/srcdirectory only when a source tree sits beside the headers. On the installed-headers build path the headers carry no source, so it returns none and the type-relation registry drops out — even though the provisioning checks out the full repository underMDB_SRC_ROOT.This locates
meos_catalog.cfrom the resolved source root when present, otherwise fromMDB_SRC_ROOT/meos/src, so the registry attaches on both the source-headers and installed-headers build paths. A test covers theMDB_SRC_ROOTfallback, and the degrade test clears the env var so it still proves honest absence when neither source is available.