Skip to content

Extensions: add FAQ section and make entry for notable extensions #851

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
leggewie wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Extensions: add FAQ section and make entry for notable extensions #851

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion docs/Developer-Guide_Extensions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,14 @@ They're the same, except:
- That is useful if there are other files/assets that belong together with that extension. An example would be a template file, some configuration file, or other static asset that is directly related to the extension.
- Using directory-based extensions and `${EXTENSION_DIR}` allows for easy moving and PR'ing of user extensions.

# Opt-out of individual hook functions
### FAQ

#### Can you give me examples of some extensions shipped in Armbian?

- [image-output-qcow2](https://github.com/armbian/build/blob/main/extensions/image-output-qcow2.sh): create images in qcow2-format, suitable to test-run in a VM.
- [uboot-btrfs](https://github.com/armbian/build/blob/main/extensions/uboot-btrfs.sh): Add btrfs support for u-boot. This makes it possible to boot straight from btrfs partitions. A growing number of board maintainers have enabled this extension.

#### How to opt out of a specific hook function?

Any function making use of the extension framework [generally of the form `hook_name__individual_function`] can be skipped in a board or family config, by way of

Expand Down
Loading