build-ptoas-wsl

Build and validate the PTOAS compiler toolchain from source in WSL.

30|74|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/hw-native-sys/PTOAS --skill build-ptoas-wsl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-ptoas-wsl
Source: https://github.com/hw-native-sys/PTOAS/tree/main/.codex/skills/build-ptoas-wsl
Command: npx skills add https://github.com/hw-native-sys/PTOAS --skill build-ptoas-wsl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a reliable workflow for building, installing, testing, and troubleshooting the PTOAS compiler toolchain in WSL without losing track of its LLVM, MLIR, Python, CMake, and runtime-linking requirements.

Core Features & Use Cases

  • WSL Environment Setup: Identify the Linux environment, install prerequisites, and choose an appropriate source location.
  • LLVM and PTOAS Builds: Configure shared LLVM/MLIR libraries from the VPTO feature branch, then build PTOAS with its editable Python package and command-line tools.
  • Validation and Troubleshooting: Run CLI smoke tests, verify namespaced MLIR Python dialect imports, and diagnose dependency, linker, CMake, and filesystem-performance issues.
  • Use Case: Build PTOAS from a Windows checkout or a WSL-native workspace, validate the generated tools and Python bindings, and reuse the persistent CMake tree for incremental development.

Quick Start

Use the build-ptoas-wsl skill to build PTOAS from source in WSL, install it in the active Python environment, and run its CLI and Python dialect smoke tests.

Frequently Asked Questions about build-ptoas-wsl

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build PTOAS from source in WSL?

To build PTOAS in WSL, configure shared LLVM and MLIR libraries from the VPTO feature branch, then use CMake and Ninja for incremental builds alongside an editable Python package installation. You can reuse the persistent CMake tree for ongoing development.

What's the best way to validate MLIR Python dialects after building PTOAS?

The best way to validate MLIR Python dialects in PTOAS is to run CLI smoke tests and verify namespaced MLIR Python dialect imports. This confirms your toolchain and Python bindings are functioning correctly.

Does building PTOAS require a specific pybind11 version for Python bindings?

Yes, building PTOAS requires pybind11 below version 3. You also need nanobind and compatible Python packaging tools to properly generate the editable Python installation and runtime library paths.

Why does my PTOAS build fail with linker or CMake errors in WSL?

PTOAS builds in WSL often fail due to missing shared LLVM or MLIR libraries, incorrect runtime library paths, or filesystem performance issues. Diagnosing dependency, linker, and CMake configurations is required to resolve these errors.

Can I use a Windows checkout to build PTOAS in WSL?

Yes, you can build PTOAS from a Windows checkout or a WSL-native workspace. The workflow involves identifying your Linux environment, installing prerequisites, and choosing an appropriate source location for the build.