Build libmeos via the shared provision-meos action - #21
Merged
estebanzimanyi merged 1 commit intoJul 10, 2026
Merged
Conversation
CI builds and installs libmeos through the shared provision-meos action instead of an inline copy of the MEOS build recipe; build-jmeos.sh now only builds the JMEOS jar against the installed libmeos. The MobilityDB commit is still taken from tools/meos-source-commit.txt.
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.
CI builds and installs libmeos through the shared
provision-meoscomposite action (MobilityDB/MEOS-API/.github/actions/provision-meos@master) instead of an inline copy of the MEOS build recipe. The workflow reads the pinned MobilityDB commit fromtools/meos-source-commit.txtand passes it to the action withbuild-libmeos: "true"; the action builds and installs an all-families libmeos under/usr/localand provisionsspatial_ref_sys.csv/ways1000.csvunder/usr/local/shareviacmake --install.build-jmeos.shnow reuses that installed libmeos when/usr/local/lib/libmeos.soexists, skipping its own MobilityDB clone, libmeos build, and CSV staging, and only builds the JMEOS jar against the installed libmeos. When no libmeos is installed (e.g. a plain local run) it still builds one from the pinned commit as before.The MobilityDB commit is still taken from
tools/meos-source-commit.txt, so no SHA is duplicated. The committedMeosOps*facades are unchanged.