Slice 10C — Maya 2025 devkit validation - #8
Merged
Conversation
Phase 2A version-matrix slice #2 of 4 (10A=2022 ✅ → 10C=2025 ✅; 10B/10D pending their devkits). Environment (out-of-repo, recorded for audit): * Relocated Maya 2025 devkit C:/Users/Administrator/Downloads/Autodesk_Maya_2025_3_Update_DEVKIT_Windows/devkitBase to canonical path C:/SDK/Maya2025/devkitBase (same-drive mv, instant; space-free, Downloads-cleanup-proof, parallels future C:/SDK/Maya2024 / C:/SDK/Maya2026 layout). * Maya 2025 runtime: C:/Program Files/Autodesk/Maya2025/bin/mayapy.exe (Python 3.11.4 embedded, vs Maya 2022's 3.7). Validation (all four steps first-try green): * Step 1 adapter + Phase 1 combined: 139/139 green, 11.60s * Step 2 rbfmax_maya.mll built clean (0 warn, 0 err, 25 088 bytes — byte-identical to 2022 output) * Step 3 mayapy 2025 smoke: exit 0, compute(1.0) bit-identical to exp(-1) (err=0.000e+00) * Step 4 Phase 1 regression: 136/136 green, 10.46s Design decisions (4 delta vs Slice 10A): * 10C-Δ1 MAYA_CXX_STD=17 branch of MayaVersionMatrix.cmake activated first time; adapter_core.hpp stayed C++14 verbatim. * 10C-Δ2 Python 3.11 mayapy in 2025 vs 3.7 in 2022; smoke script needed no adjustment (Python 3.6-stable features only). * 10C-Δ3 Maya 2025 inline namespace Autodesk::Maya::OpenMaya20250000 — no impact; 10A's F2 fix (dropping extern "C" in plugin_main.cpp) is version-agnostic. * 10C-Δ4 Canonical SDK path convention adopted via explicit -DMAYA_DEVKIT_ROOT; probe-path expansion deferred to 10B/10D when there's a concrete second example. Zero source-code changes. Zero spec drift. Zero in-flight fixes. The LOC count reflects what the pre-slice strategic argument predicted: "low-LOC high-audit-value" slice that proves the shift-left design held up. maya_node/README.md: new "Build — Maya 2025" section + status table updated to show 10A/10C both validated. No tag, no version bump (per 10A's D14). Co-Authored-By: Claude Opus 4.6 <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
2 participants
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
Phase 2A version-matrix validation. Exercises
cmake/MayaVersionMatrix.cmake's C++17 arm against the Maya 2025 devkit + Python 3.11 mayapy. Zero source code changes, zero spec drift, zero in-flight fixes — Slice 10A's shift-left abstractions held up verbatim.Phase 2A version matrix progress:
Environment setup (out-of-repo, audit-recorded)
C:/Users/Administrator/Downloads/Autodesk_Maya_2025_3_Update_DEVKIT_Windows/devkitBaseto canonicalC:/SDK/Maya2025/devkitBase. Same-drivemv, instant. Path is space-free and Downloads-cleanup-proof.C:/Program Files/Autodesk/Maya2025/bin/mayapy.exe, Python 3.11.4 (vs 2022's 3.7).Design decisions (4 delta vs Slice 10A)
MAYA_CXX_STD=17activated;adapter_core.hppunchanged (was C++14-compatible by design).Autodesk::Maya::OpenMaya20250000— no impact; 10A's F2 fix (noextern "C") is version-agnostic.C:/SDK/Maya2025/devkitBasepath via explicit-DMAYA_DEVKIT_ROOT; probe-path expansion deferred to 10B/10D.Local verification (4/4 first-try green)
rbfmax_maya.mllbuildcompute(1.0) == exp(-1)bit-identical (err=0.000e+00)R-09 self-check
No new tolerances introduced. Existing H1 exact / H2 / H3 at
1e-14/ mayapy assertion1e-12all observed witherr=0.Scope
Single commit, doc + validation only. No tag, no version bump.
Test plan
C:/SDK/Maya2025/devkitBase/{include/maya/MFn.h, lib/OpenMaya.lib}both presentWhy this slice before Slice 11
Decouples "Maya version compatibility" from "mRBFNode feature work". Slice 11 can now run its mayapy smoke on both Maya 2022 and Maya 2025 to distinguish "code bug" from "version bug" at a glance.
🤖 Generated with Claude Code