Expand building Claude skill to cover general ET building from source - #2
Draft
psiddh wants to merge 15 commits into
Draft
Expand building Claude skill to cover general ET building from source#2psiddh wants to merge 15 commits into
psiddh wants to merge 15 commits into
Conversation
The existing building skill only covered runners (Makefile targets) and CMake workflow presets. This expands it to be a comprehensive guide for building ExecuTorch from source, including: - Prerequisites and toolchain requirements - Building the Python package (install_executorch.sh with all flags) - Building the C++ runtime standalone (presets, workflows, manual CMake) - Building model runners (Makefile) - Cross-compilation (Android, iOS, macOS, Windows) - Complete build options reference with dependency chains - Common build patterns (minimal, XNNPACK, profiling, tests, subdirectory) - Troubleshooting section covering 12 common build issues: - Submodule issues - Stale build artifacts - CMake version conflicts - Python version mismatch - Dependency version conflicts - Missing python-dev headers - Linking errors with --whole-archive - XNNPACK build failures - Windows symlink errors - MSVC kernel compilation failures - Intel macOS limitations - Duplicate kernel registration - Build output reference table - Tips for faster and more reliable builds
Reorganize the building skill to be concise and action-driven rather than encyclopedic. Key changes: - Add "do not ask questions" directive — detect and fix env issues automatically - Make conda the mandatory path (no venvs, no system Python) - Auto-fix for cmake >= 4.0 and PEP 668 errors - Default action is `./install_executorch.sh --editable` - Complete runner table from actual Makefile (adds voxtral, voxtral_realtime, sortformer, silero-vad, llava, debug variants) - Fix macOS commands: $(sysctl -n hw.ncpu) instead of $(nproc) - Note that --preset macos uses Xcode generator - Condense troubleshooting into scannable table - Trim cmake options to most-used flags (full list in CMakeLists.txt) Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
- Add venv fallback when conda is not installed - Handle conda PermissionError by checking env directory on disk - Auto-fix cmake: missing or < 3.24 gets pip-installed, >= 4.0 works fine - Add troubleshooting entries for conda not found and PEP 668 errors - Remove heavy-handed directive banner; let skill structure guide behavior Co-authored-by: Claude <noreply@anthropic.com>
Explicit decision tree at the top of Step 2 so Claude routes to the right section based on keywords (Android, iOS, model names, cmake) instead of always defaulting to the Python package build. Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
- Add ANDROID_NDK requirement and verification to Android section - Fix CMAKE_BUILD_TYPE description: not all presets set it - Separate build output table by flow (pip vs cmake vs cross-compilation) Co-authored-by: Claude <noreply@anthropic.com>
Three issues that would break a fresh Mac checkout: - Add Xcode Command Line Tools prerequisite check - Add conda shell.bash hook for non-interactive shells (Claude Code / CI) - Add brew install python@3.12 guidance for venv path when only 3.14+ exists Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Claude <noreply@anthropic.com>
psiddhforce-pushed
the
main
branch
2 times, most recently
from
August 25, 2026 16:18
d58eb7e to
baafd7eCompare
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 freeto 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.
Summary
The existing
/buildingClaude skill only covered runners (Makefile targets likemake llama-cpu) and a couple of CMake workflow presets. This PR expands it into a comprehensive guide for building ExecuTorch from source.Changes
Expanded
.claude/skills/building/SKILL.mdfrom 23 lines to 353 lines, covering:New Sections
install_executorch.shwith all flags, backend enablement viaCMAKE_ARGS, verificationMotivation
The original skill was too narrow for Claude to help users build ExecuTorch from source. Users asking Claude to 'build ExecuTorch' would only get runner-specific instructions, missing the broader Python package install, standalone C++ runtime build, cross-compilation, and troubleshooting guidance.
Testing
This is a documentation-only change to a Claude skill file. No code changes.
Target: pytorch/executorch (to be submitted as upstream PR)
cc @Mengwei-Liu