Fix build-and-release: Linux/macOS standalone executables - #6
Merged
Merged
Conversation
The native MovingBoundarySolver executable links FronTier, which does not compile under MSVC, so the Windows leg always failed — and with no fail-fast: false it cancelled the Linux/macOS jobs, leaving every tag with no artifacts and no release. Build Linux + macOS standalone executables only (Windows tracked in #2), and set fail-fast: false so one platform's failure no longer sinks the others. Also drop the obsolete Python .so copy (Python distribution is handled by wheels.yml/PyPI now) and use a portable core-count for ctest -j. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
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.
Summary
Restores the native standalone executable release pipeline, which has been failing on every tag.
MovingBoundarySolverlinks the bundled FronTier library, which does not compile under MSVC (same blocker as Windows wheels — issue Windows wheels: port FronTier to compile under MSVC (or build via clang-cl/MinGW) #2). Windows always failed.fail-fast: false. Previously the Windows failure cancelled the Linux/macOS jobs, so a tag produced no artifacts and no release at all. Now Linux + macOS build independently.vcellmbsolver_py*.socopy (Python distribution is handled bywheels.yml→ PyPI now) and use a portablegetconf _NPROCESSORS_ONLNforctest -j.Effect
On each
v*tag this builds the Linux + macOSMovingBoundarySolverexecutable +libMovingBoundaryLib.aand attaches them to the GitHub Release (with auto-generated notes). Windows native executables remain blocked until FronTier is ported (#2).Note: this is the executables/GitHub-Release pipeline; it is separate from and complementary to
wheels.yml(which builds Python wheels and publishes to PyPI). Both run on av*tag.🤖 Generated with Claude Code