matt/yocto_imx
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Migrated from GitHub
13 commits 1 branch 0 tags 432 KiB
  • BitBake 82%
  • Shell 13%
  • Python 2.8%
  • C++ 1.5%
  • Dockerfile 0.3%
  • Other 0.3%
Find a file
Exact
Matthew Brocklehurst 8747c8bf3c Update README and kas scripts for NT6/NT7 enhancements and repository management 
- Expanded README.txt with details on NT6 and NT7 repository pinning and build commands.
- Added a new function in kas-yocto.sh to ensure compatibility for the summit-radio layer, addressing BitBake warnings.
- Updated local.conf for NT7 to specify preferred versions and silence multilib notes.
- Refactored nt7.yml to include commit-pinned repositories, ensuring consistency in builds.
- Removed obsolete gstreamer1.0-plugins-base.bbappend to streamline the codebase.

These changes improve documentation clarity, enhance build processes, and ensure better layer compatibility.
2026-04-07 16:33:36 +01:00
docker/yocto Fixes to get this to build with Yocto/Kas 2026-03-31 17:01:08 +01:00
Playtech Update README and kas scripts for NT6/NT7 enhancements and repository management 2026-04-07 16:33:36 +01:00
.gitignore Initial import: Yocto/Kas split from slots-firmware (v11.4-matt) 2026-03-31 17:01:08 +01:00
README.md Added README.md 2026-03-31 15:20:50 +00:00
README.txt Update README and kas scripts for NT6/NT7 enhancements and repository management 2026-04-07 16:33:36 +01:00

README.md

Introduction

TODO: Give a short introduction of your project. Let this section explain the objectives or the motivation behind this project.

Getting Started

TODO: Guide users through getting your code up and running on their own system. In this section you can talk about:

  1. Installation process
  2. Software dependencies
  3. Latest releases
  4. API references

Build and Test

TODO: Describe and show how to build your code and run the tests.

Contribute

TODO: Explain how other users and developers can contribute to make your code better.

If you want to learn more about creating good readme files then refer the following guidelines. You can also seek inspiration from the below readme files: