Skip to main content

building

Build ExecuTorch from source — Python package, C++ runtime, runners, cross-compilation, and backend-specific builds. Use when compiling anything in the ExecuTorch repo, diagnosing build failures, or setting up platform-specific builds.

소스 정보

저장소
pytorch/executorch
최근 소스 활동
2026년 11월 6일 22:41
감지된 SKILL.md 언어
영어
스타
5,164
포크
1,238

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
building
description
Build ExecuTorch from source — Python package, C++ runtime, runners, cross-compilation, and backend-specific builds. Use when compiling anything in the ExecuTorch repo, diagnosing build failures, or setting up platform-specific builds.
# Building ExecuTorch ## Step 1: Ensure Python environment (detect and fix automatically) **Path A — conda (preferred):** ```bash # Initialize conda for non-interactive shells (required in Claude Code / CI) eval "$(conda shell.bash hook 2>/dev/null)" # Check if executorch conda env exists; create if not conda env list 2>/dev/null | grep executorch || \ ls "$(conda info --base 2>/dev/null)/envs/" 2>/dev/null | grep executorch || \ conda create -yn executorch python=3.12 # Activate conda activate executorch ``` **Path B — no conda (fall back to venv):** ```bash # Find a compatible Python (3.11–3.15). python3.12 -m venv .executorch-venv # or python3.11, python3.13, python3.14, python3.15 source .executorch-venv/bin/activate pip install --upgrade pip ``` **Then verify (either path):** Run `python --version` and `cmake --version`. Fix automatically: - **Python not 3.11–3.15**: recreate the env with a correct Python version. - **cmake missing or < 3.24**: run `pip install 'cmake>=3.24'` inside the env. - **cmake >= 4.0**: works in practice, no action needed. Parallel jobs: `$(sysctl -n hw.ncpu)` on macOS, `$(nproc)` on Linux. ## Step 2: Build Route based on what the user asks for: - User mentions **Android** → skip to [Cross-compilation: Android](#cross-compilation) - User mentions **iOS** or **frameworks** → skip to [Cross-compilation: iOS](#cross-compilation) - User mentions a **model name** (llama, whisper, etc.) → skip to [LLM / ASR model runner](#llm--asr-model-runner-simplest-path-for-running-models) - User mentions **C++ runtime** or **cmake** → skip to [C++ runtime](#c-runtime-standalone) - Otherwise → default to **Python package** below ### Python package (default) ```bash conda activate executorch ./install_executorch.sh --editable # editable install from source ``` This handles everything: submodules, deps, C++ build, Python install. Takes ~10 min on Apple Silicon. For subsequent rebuilds (deps already present): `pip install -e . --no-build-isolation` For minimal install (skip example deps): `./install_executorch.sh --minimal` Enable additional backends: ```bash CMAKE_ARGS="-DEXECUTORCH_BUILD_COREML=ON -DEXECUTORCH_BUILD_VULKAN=ON" ./install_executorch.sh --editable ``` Verify: `python -c "from executorch.exir import to_edge_transform_and_lower; print('OK')"` ### LLM / ASR model runner (simplest path for running models) ```bash conda activate executorch make <model>-<backend> ``` Available targets (run `make help` for full list): | Target | Backend | macOS | Linux | |--------|---------|-------|-------| | `llama-cpu` | CPU | yes | yes | | `llama-cuda` | CUDA | — | yes | | `llama-cuda-debug` | CUDA (debug) | — | yes | | `llava-cpu` | CPU | yes | yes | | `whisper-cpu` | CPU | yes | yes | | `whisper-metal` | Metal | yes | — | | `whisper-cuda` | CUDA | — | yes | | `parakeet-cpu` | CPU | yes | yes | | `parakeet-metal` | Metal | yes | — | | `parakeet-cuda` | CUDA | — | yes | | `voxtral-cpu` | CPU | yes | yes | | `voxtral-cuda` | CUDA | — | yes | | `voxtral-metal` | Metal | yes | — | | `voxtral_realtime-cpu` | CPU | yes | yes | | `voxtral_realtime-cuda` | CUDA | — | yes | | `voxtral_realtime-metal` | Metal | yes | — | | `gemma3-cpu` | CPU | yes | yes | | `gemma3-cuda` | CUDA | — | yes | | `sortformer-cpu` | CPU | yes | yes | | `sortformer-cuda` | CUDA | — | yes | | `silero-vad-cpu` | CPU | yes | yes | | `clean` | — | yes | yes | Output: `cmake-out/examples/models/<model>/<runner>` ### C++ runtime (standalone) **With presets (recommended):** | Platform | Command | |----------|---------| | macOS | `cmake -B cmake-out --preset macos` (uses Xcode generator — requires Xcode) | | Linux | `cmake -B cmake-out --preset linux -DCMAKE_BUILD_TYPE=Release` | | Windows | `cmake -B cmake-out --preset windows -T ClangCL` | Then: `cmake --build cmake-out --config Release -j$(sysctl -n hw.ncpu)` (macOS) or `cmake --build cmake-out -j$(nproc)` (Linux) **LLM libraries via workflow presets** (configure + build + install in one command): ```bash cmake --workflow --preset llm-release # CPU cmake --workflow --preset llm-release-metal # Metal (macOS) cmake --workflow --preset llm-release-cuda # CUDA (Linux/Windows) ``` **Manual CMake (custom flags):** ```bash cmake -B cmake-out \ -DCMAKE_BUILD_TYPE=Release \ -DEXECUTORCH_BUILD_XNNPACK=ON \ -DEXECUTORCH_BUILD_KERNELS_OPTIMIZED=ON \ -DEXECUTORCH_BUILD_EXTENSION_MODULE=ON \ -DEXECUTORCH_BUILD_EXTENSION_FLAT_TENSOR=ON \ -DEXECUTORCH_BUILD_EXTENSION_NAMED_DATA_MAP=ON \ -DEXECUTORCH_BUILD_EXTENSION_DATA_LOADER=ON \ -DEXECUTORCH_BUILD_EXTENSION_TENSOR=ON cmake --build cmake-out --parallel "$(nproc 2>/dev/null || sysctl -n hw.ncpu)" ``` Run `cmake --list-presets` to see all available presets. ### Cross-compilation **iOS/macOS frameworks:** ```bash ./scripts/build_apple_frameworks.sh --coreml --xnnpack ``` Link in Xcode with `-all_load` linker flag. **Android:** Requires `ANDROID_NDK` on PATH (typically set by Android Studio or standalone NDK install). ```bash # Verify NDK is available echo $ANDROID_NDK # must point to NDK root, e.g. ~/Library/Android/sdk/ndk/<version> export ANDROID_ABIS=arm64-v8a BUILD_AAR_DIR=aar-out mkdir -p $BUILD_AAR_DIR && sh scripts/build_android_library.sh ``` ## Key build options Most commonly needed flags (full list: `CMakeLists.txt`): | Flag | What it enables | |------|-----------------| | `EXECUTORCH_BUILD_XNNPACK` | XNNPACK CPU backend | | `EXECUTORCH_BUILD_COREML` | Core ML (macOS/iOS) | | `EXECUTORCH_BUILD_METAL` | Metal compute (macOS, requires EXTENSION_TENSOR) | | `EXECUTORCH_BUILD_CUDA` | CUDA GPU (Linux/Windows, requires EXTENSION_TENSOR) | | `EXECUTORCH_BUILD_KERNELS_OPTIMIZED` | Optimized kernels | | `EXECUTORCH_BUILD_KERNELS_QUANTIZED` | Quantized kernels | | `EXECUTORCH_BUILD_EXTENSION_MODULE` | Module extension (requires DATA_LOADER + FLAT_TENSOR + NAMED_DATA_MAP) | | `EXECUTORCH_BUILD_EXTENSION_LLM` | LLM extension | | `EXECUTORCH_BUILD_TESTS` | Unit tests (`ctest --test-dir cmake-out --output-on-failure`) | | `EXECUTORCH_BUILD_DEVTOOLS` | DevTools (Inspector, ETDump) | | `EXECUTORCH_OPTIMIZE_SIZE` | Size-optimized build (`-Os`, no exceptions/RTTI) | | `CMAKE_BUILD_TYPE` | `Release` or `Debug` (5-10x slower). Some presets (e.g. `llm-release`) set this; others require it explicitly. | ## Troubleshooting | Symptom | Fix | |---------|-----| | Missing headers / `CMakeLists.txt not found` in third-party | `git submodule sync --recursive && git submodule update --init --recursive` | | Mysterious failures after `git pull` or branch switch | `rm -rf cmake-out/ pip-out/ && git submodule sync && git submodule update --init --recursive` | | `conda env list` PermissionError | Use `CONDA_NO_PLUGINS=true conda env list` or check env dir directly | | CMake >= 4.0 | Works in practice despite `< 4.0` in docs; only fix if build actually fails | | `externally-managed-environment` / PEP 668 error | You're using system Python, not conda. Activate conda env first. | | pip conflicts with torch versions | Fresh conda env; or `./install_executorch.sh --use-pt-pinned-commit` | | Missing `Python.h` (Linux) | `sudo apt install python3.X-dev` | | Missing operator registrations at runtime | Link kernel libs with `-Wl,-force_load,<lib>` (macOS) or `-Wl,--whole-archive <lib> -Wl,--no-whole-archive` (Linux) | | `install_executorch.sh` fails on Intel Mac | No prebuilt PyTorch wheels; use `--use-pt-pinned-commit --minimal` | | XNNPACK build errors about cpuinfo/pthreadpool | Ensure `EXECUTORCH_BUILD_CPUINFO=ON` and `EXECUTORCH_BUILD_PTHREADPOOL=ON` (both ON by default) | | Duplicate kernel registration abort | Only link one `gen_operators_lib` per target | ## Build output **From `./install_executorch.sh` (Python package):** | Artifact | Location | |----------|----------| | Python package | `site-packages/executorch` | **From CMake builds** (`cmake --install` with `CMAKE_INSTALL_PREFIX=cmake-out`): | Artifact | Location | |----------|----------| | Core runtime | `cmake-out/lib/libexecutorch.a` | | XNNPACK backend | `cmake-out/lib/libxnnpack_backend.a` and `cmake-out/lib/libxnnpack_profiler.a` | | executor_runner | `cmake-out/executor_runner` (Ninja/Make) or `cmake-out/Release/executor_runner` (Xcode) | | Model runners | `cmake-out/examples/models/<model>/<runner>` | **From cross-compilation:** | Artifact | Location | |----------|----------| | iOS frameworks | `cmake-out/*.xcframework` | | Android AAR | `aar-out/` | ## Tips - Always use `Release` for benchmarking; `Debug` is 5–10x slower - `ccache` is auto-detected if installed (`brew install ccache`) - `Ninja` is faster than Make (`-G Ninja`) — but `--preset macos` uses Xcode generator - For LLM workflows, `make <model>-<backend>` is the simplest path - After `git pull`, clean and re-init submodules before rebuilding
GitHub에서 보기