Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/balena-os/balena-connectcore
BalenaOS for the Digi ConnectCore SBCs and System-On-Modules
https://github.com/balena-os/balena-connectcore
Last synced: about 1 month ago
JSON representation
BalenaOS for the Digi ConnectCore SBCs and System-On-Modules
- Host: GitHub
- URL: https://github.com/balena-os/balena-connectcore
- Owner: balena-os
- License: apache-2.0
- Created: 2020-12-17T20:46:21.000Z (about 4 years ago)
- Default Branch: master
- Last Pushed: 2024-11-11T14:36:38.000Z (about 1 month ago)
- Last Synced: 2024-11-11T15:34:48.700Z (about 1 month ago)
- Language: BitBake
- Homepage:
- Size: 5.82 MB
- Stars: 2
- Watchers: 6
- Forks: 2
- Open Issues: 9
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
# balena-connectcore repository
## Clone/Initialize the repository
There are two ways of initializing this repository:
* Clone this repository with "git clone --recursive".or
* Run "git clone" and then "git submodule update --init --recursive". This will
bring in all the needed dependencies.## Build information
balenaOS currently only builds with cgroups v1. If your distribution defaults
to using cgroups v2, please boot with the following kernel command line
argument:
`systemd.unified_cgroup_hierarchy=0`### Containerized build
* If you have a working docker installation, you can build in a containerized
environment as follows:
`./balena-yocto-scripts/build/balena-build.sh -d -s `Where:
* Device type is one of the supported devices with a valid `.coffee` description file.
* Shared directory is the absolute path to the build folder### Native build
To build all supported device types natively, please make sure your Linux
distribution is [supported](https://docs.yoctoproject.org/singleindex.html#supported-linux-distributions) by Yocto Project.Additional host tools need to be installed for native builds to work.
* Run the barys build script:
`./balena-yocto-scripts/build/barys`* You can also run barys with the -h switch to inspect the available options
### Custom build using this repository
* Run the barys build script in dry run mode to setup an empty `build` directory
`./balena-yocto-scripts/build/barys --remove-build --dry-run`* Edit the `local.conf` in the `build/conf` directory
* Prepare build's shell environment
`source layers/poky/oe-init-build-env`* Run bitbake (see message outputted when you sourced above for examples)
### Build flags
* Consult layers/meta-balena/README.md for info on various build flags (setting
up serial console support for example) and build prerequisites. Build flags can
be set by using the build scripts (barys or balena-build) or by manually
modifying `local.conf`.## Contributing
### Issues
For balenaOS issues we use an aggregated github repository available [here](https://github.com/balena-os/meta-balena/issues). When you create issue make sure you select the right labels.
Device specific issues can be opened in this repository.
### Pull requests
To contribute send github pull requests targeting this repository.
Please refer to: [Yocto Contribution Guidelines](https://wiki.yoctoproject.org/wiki/Contribution_Guidelines#General_Information) and try to use the commit log format as stated there. Example:
```
test.bb: I added a test[Issue #01]
I'm going to explain here what my commit does in a way that history
would be useful.Signed-off-by: Joe Developer
```Make sure you mention the issue addressed by a PR. See:
* https://help.github.com/articles/autolinked-references-and-urls/#issues-and-pull-requests
* https://help.github.com/articles/closing-issues-via-commit-messages/#closing-an-issue-in-a-different-repository