build: isolate LegacyGL implementation from core builds - #41
Open
tritao wants to merge 3 commits into
Open
Conversation
tritao
force-pushed
the
stack/legacygl-boundary-rewrite
branch
2 times, most recently
from
August 10, 2026 11:18
91449be to
3d3562e
Compare
tritao
force-pushed
the
stack/legacygl-boundary-rewrite
branch
from
August 10, 2026 11:23
3d3562e to
e31d81e
Compare
tritao
force-pushed
the
stack/legacygl-boundary-rewrite
branch
3 times, most recently
from
August 10, 2026 14:16
7b7f2e9 to
3f6dae9
Compare
tritao
marked this pull request as ready for review
August 10, 2026 15:26
tritao
force-pushed
the
stack/legacygl-boundary-rewrite
branch
3 times, most recently
from
August 11, 2026 14:05
1a9ddc8 to
6e41f07
Compare
This was referenced Aug 11, 2026
tritao
force-pushed
the
stack/legacygl-boundary-rewrite
branch
2 times, most recently
from
August 16, 2026 00:25
317845a to
2672ef3
Compare
tritao
force-pushed
the
stack/legacygl-boundary-rewrite
branch
from
August 17, 2026 15:52
2672ef3 to
776a354
Compare
tritao
force-pushed
the
stack/legacygl-boundary-rewrite
branch
2 times, most recently
from
August 18, 2026 09:24
0182274 to
8018fb1
Compare
tritao
force-pushed
the
stack/legacygl-boundary-rewrite
branch
from
August 18, 2026 14:40
8018fb1 to
8555be1
Compare
tritao
force-pushed
the
stack/legacygl-boundary-rewrite
branch
2 times, most recently
from
August 18, 2026 18:12
15376f1 to
a1197b4
Compare
tritao
force-pushed
the
stack/legacygl-boundary-rewrite
branch
from
August 18, 2026 19:52
a1197b4 to
1f6aff6
Compare
tritao
force-pushed
the
stack/legacygl-boundary-rewrite
branch
2 times, most recently
from
August 19, 2026 01:16
0e91e8c to
b5a4914
Compare
tritao
force-pushed
the
stack/legacygl-boundary-rewrite
branch
3 times, most recently
from
August 19, 2026 02:27
d4bf829 to
6d12092
Compare
tritao
force-pushed
the
stack/legacygl-boundary-rewrite
branch
from
August 19, 2026 10:22
6d12092 to
21f3496
Compare
tritao
force-pushed
the
stack/legacygl-boundary-rewrite
branch
from
August 19, 2026 10:28
21f3496 to
8a1c2d0
Compare
tritao
force-pushed
the
stack/legacygl-boundary-rewrite
branch
from
August 19, 2026 14:29
8a1c2d0 to
4465e0d
Compare
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
Separate Coin core scene-management APIs from the optional LegacyGL implementation while preserving the public
SoNodeABI.SoNode::GLRender*()virtual surface stable in every configuration.COIN_BUILD_LEGACY_GL_RENDERER=ON.SoRenderManagerandSoSceneManagerusable in LegacyGL-disabled builds.COIN_HAVE_LEGACY_GL_RENDERER.This PR defines the implementation boundary only. It does not introduce a replacement renderer or change scene semantics.
Validation
find_package(Coin)consumer builds against both installed variants.Stack
Layer 7/18, based on PR #38.