feat(eui-neo): add 0.5.8 - #333
Merged
Merged
Conversation
CORE_SOURCES gains exactly one TU — core/render/image_stream.cpp, the new dynamic-texture surface (CPU-side pixel upload, e.g. decoded video frames). It is self-contained (its own header plus the STL), so the descriptor's sources go 25 → 26 and nothing else moves: 3rd/ is byte-identical, the tray bridge and window/input backends are unchanged, and deps/features/flags all carry over. The remaining upstream changes are backend internals for the new surface (opengl and vulkan image/upload paths, both shader sets), an off-by-default EUI_APP_RUNNER umbrella-main variant aimed at xmake-repo packaging, and an FFmpeg example behind EUI_BUILD_FFMPEG_VIDEO_EXAMPLE — all outside this package's source list. -fno-char8_t is still required: platform.cpp/shadertoy_json.cpp/ image_source.cpp still return path::u8string() as std::string. No CN mirror yet (never published to mcpp-res); same GLOBAL+CN entry shape as 0.5.7. sha256 derived from the tag tarball. All seven workspace members bumped to 0.5.8 and verified locally with mcpp 2026.9.4.1 (parse OK, lint green; eui-neo, eui-neo-window, eui-neo-app-main, eui-neo-markdown, eui-neo-vulkan, eui-neo-sdl2 and eui-neo-tray all pass — 549s total).
The { GLOBAL, CN } pair pointed at a gitcode release that does not
exist, and CI's mirror check probes every CN url. A plain string is
exempt from that check (and falls back to upstream for CN users); the
maintainer flips it to the pair when the mcpp-res mirror lands.
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.
Upstream released v0.5.8.
What changed upstream (0.5.7 → 0.5.8)
CORE_SOURCESgains exactly one TU:core/render/image_stream.cpp— the new dynamic-texture surface (CPU-side pixel upload, e.g. decoded video frames). Self-contained: its own header plus the STL, no new dependency.EUI_APP_RUNNERumbrella-main variant aimed at xmake-repo packaging, and an FFmpeg example behindEUI_BUILD_FFMPEG_VIDEO_EXAMPLE(app-level, not part of the lib).3rd/is byte-identical; tray bridge, window/input backends, both app-main TUs unchanged. Deps / features / flags all carry over.-fno-char8_tis still required —platform.cpp/shadertoy_json.cpp/image_source.cppstill returnpath::u8string()asstd::string.Descriptor changes
xpm.{linux,macosx,windows}each gain a["0.5.8"]entry (sha256004d46f3…, derived from the tag tarball). No CN mirror yet — same GLOBAL+CN entry shape as 0.5.7.sources25 → 26:*/core/render/image_stream.cpp.tests/examples/eui-neo*members bumped to 0.5.8.Verification (mcpp 2026.9.4.1, linux)
mcpp xpkg parse→ OK (5 versions × 3 platforms, 26 sources, 6 features)check_mirror_urls/check_package_name/check_platform_version_parity/check_duplicate_versions/check_cross_package_refs) → all greentests/run_members.shon all seven members — all pass, 549s total: