agentleFS
Sign inStart free
D-RoboticsD-Robotics/dsh-plugin-rdk/skills/bsp-skills/bsp-deb-build/SKILL.md

bsp-deb-build

Skill1 starsChanged 3 months agoApache-2.0View on GitHub

Rebuild the official hobot-* debian packages with mk_debs.sh (all or a named package like hobot-boot / hobot-dtb / hobot-multimedia). Use when the user wants to repackage a hobot-* component, inject fixes into the image via deb, or asks which packages can be built. 触发词:hobot-* 包、mk_debs、deb 包、重新打包、hobot-boot、hobot-configs. Do not use for kernel compilation itself (bsp-kernel-build) or full images (bsp-image-build).

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not use for compiling the kernel itself or the whole image.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

hobot-* Deb Package Build

Purpose

Rebuild the official D-Robotics debian packages (hobot-*) from their sources in the source/ tree. These packages carry the kernel image, dtb, kernel headers, multimedia libraries, samples, and system configs that get preinstalled into system images.

When to use

Use when:

  • A hobot-* source package was modified and needs repackaging
  • The user wants to inject a fixed package into the image instead of a full rebuild
  • Listing which packages the build system supports

Do not use for compiling the kernel itself or the whole image.

Instructions

  1. Prerequisite: kernel artifacts must exist first (see bsp-kernel-build) — the build system uses them for hobot-boot, hobot-dtb, hobot-kernel-headers.
  2. Build everything:
    ./mk_kernel.sh
./mk_debs.sh
    Outputs land in deploy/deb_pkgs/*.deb.
  3. Build a single package by name:
    ./mk_debs.sh hobot-configs
  4. Supported package names (from the official README help text): hobot-boot hobot-kernel-headers hobot-dtb hobot-configs hobot-utils hobot-display hobot-wifi hobot-io hobot-io-samples hobot-multimedia hobot-multimedia-dev hobot-camera hobot-dnn hobot-spdev hobot-sp-samples hobot-multimedia-samples hobot-miniboot hobot-audio-config For any other name the script answers "not supported" — report that verbatim instead of guessing.
  5. To get a rebuilt package into an image: drop the .deb into third_packages/ before bsp-image-build, or use it directly for on-board dpkg -i if the user asks (confirm target board compatibility first).

Safety

  • Wrong package name errors are informational — never edit mk_debs.sh to "add" a package without discussing with the user.
  • Packages built from a dirty source tree silently carry uncommitted changes — ask the user to review git status in source/ first.
  • Mixing X3 and X5 artifacts in one workspace corrupts packages — confirm the workspace matches the target board.

Sources: x5-rdk-gen README v3.5.0「编译 RDK 官方 debian 软件包」; rdk-gen README v3.0.3「编译 debian 软件包」。

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free