Opened 11 years ago
Last modified 8 years ago
#10190 closed task
Make Bluetooth stack an actual HPKG via build system — at Version 2
| Reported by: | mmadia | Owned by: | bonefish |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Build System | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description (last modified by )
By making Bluetooth an actual HPKG, it could be included in the default image as a non-activated package. This would make testing easier for end users.
build/jam/OptionalPackages contains the pre-package management code. build/jam/packages contains several working examples. An accompanying package-info-source will need to be created in src/data/package_infos/
Change History (3)
by , 11 years ago
| Attachment: | 0001-Bluetooth-as-HPKG-initial-steps.patch added |
|---|
comment:1 by , 11 years ago
| patch: | 0 → 1 |
|---|
comment:2 by , 11 years ago
| Description: | modified (diff) |
|---|
Attached is my attempt to update Bluetooth into a source-built HPKG. Being the first time doing this, I'm uncertain if it's properly done.
This turns the OptionalPackage "Bluetooth" into a HPKG. Currently it is installed to /_packages_. The idea is for the bluetooth package to be installed on the boot medium, without being activated by default.
build/jam/packages/Bluetooth contains a TODO for implementing the development symlink for libbluetooth.so.
Untested beyond being able to build bluetooth.hpkg.
Initial patch