jetson-build-source
Use when you need to rebuild the BSP overlay — DT, OOT modules, or kernel — from changes under bsp_sources/. Triggers: build bsp, rebuild dtb, rebuild kernel.
npx skills add NVIDIA/skills --skill jetson-build-source --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Rebuild the kernel-side artifacts implied by changes under <source.root_path>/bsp_sources/, and write a manifest that /jetson-promote-image reads to stage outputs into the BSP image. Outputs stay in-tree under <source.root_path>/bsp_sources/. It selects a build mode (dt, oot, kernel, full) based on dirty repos or a forced argument, and supports manual re-run via /jetson-build-source [<mode>].
How it works
- Validates active target and paths, sourcing the NVIDIA build env with
source "$BSP_SRC/kernel_src_build_env.sh"to obtain KERNEL_SRC_DIR, KERNEL_DEF_CONFIG, OOT_SOURCE_LIST, kernel_name, KERNEL_MODULAR_BUILD. - Reads and enforces prerequisites: host packages flex, bison, libssl-dev (hard); git, build-essential, bc, zstd (warn); ensures CROSS_COMPILE ends with a trailing dash and that
${CROSS_COMPILE}gccexists. - Detects dirty sources by comparing HEADs against a watermark and checking for uncommitted edits; handles mono-repo with per-sub-path watermarking.
- Determines build mode automatically from the dirty set (dt, oot, kernel, full) or uses a user-supplied argument; supports switching to a specific mode via the argument.
- Executes the mode-specific build using the common setup and per-mode make invocations described in references/build-modes.md, operating from the KS directory and using the upstream primitives found under <bsp_image.root_path>/Linux_for_Tegra/source/.
- For dt or full modes, registers a composite overlay by modifying per-dir Makefile (dtbo-y) and carrier flash conf (OVERLAY_DTB_FILE+), ensuring patches are idempotent and compliant with the overlay registration rules.
- Writes a manifest by iterating the DIRTY set and emitting per-artifact entries, then atomically moves the manifest into place. Updates the watermark and summary with new HEADs, toolchain, version, and mode.
- Outputs a summary including toolchain, build mode, dirty repos, built artifacts counts, manifest path, and next step (/jetson-promote-image).
When to use it
- Auto-chained at the end of a Customize customize-* invocation when kernel-side source changes were committed.
- Manual re-run via
/jetson-build-source [<mode>]when the auto-build was interrupted, new commits arrived, a rebuild is desired without a fresh edit, or a specific mode (e.g., install consolidation) is required.
What it can touch
- Environment variables and paths defined in the Resolve active target step (WORKSPACE, BSP_SRC, KS, KOUT, STAGE, STATE, MANIFEST).
- The kernel source tree under
<source.root_path>/bsp_sourcesand the composite overlay files (Makefile patches, OVERLAY_DTB_FILE) in the BSP sources directory when in dt or full mode.
Caveats
- Toolchain resolution is jetson-init-source's job; this skill only reads source.toolchain and exports CROSS_COMPILE. Missing field leads to routing instead of in-skill resolution.
- Direct edits to in-tree .dts/.dtsi under bsp_sources are forbidden by design; composite overlay content is owned by customize-* skills, while this skill handles registration and flash-conf updates.
- The skill assumes proper upstream environment and file layout; missing <source.root_path>/bsp_sources or missing kernel_src_build_env.sh triggers routing or failure as described in prerequisites and resolve steps.
- No overlay staging into the BSP image is performed; the manifest governs promotion via jetson-promote-image.
# Build BSP Source ## Purpose Rebuild the kernel-side artifacts (DTBs, OOT modules, in-tree modules, kernel `Image`) implied by changes under `<source.root_path>/bsp_sources/`, and write a manifest that `/jetson-promote-image` reads to stage those outputs into the BSP image. The skill never writes into `<bsp_image.root_path>` itself. ## Prerequisites - Active target-platform profile with `bsp_imag
What does the jetson-build-source skill do?
Use when you need to rebuild the BSP overlay — DT, OOT modules, or kernel — from changes under bsp_sources/. Triggers: build bsp, rebuild dtb, rebuild kernel.
How do I install it?
Run `npx skills add NVIDIA/skills --skill jetson-build-source --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From NVIDIA/skills, a repository with 2,789 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.