Lithosphere is providing infrastructure to build thunder firmware images based on Buildroot. Buildroot is known to keep the process of creating embedded Linux systems simple. The key benefit of Lithosphere is that it is designed to be modular and extensible by using external layers. This keeps the custom changes needed for thunder away from the buildroot sources, making updating and maintaining images easy and clear. With a decent modern laptop it should take you about one hour, from cloning this repo, till a completed image with Thunder.
To get started with Lithosphere, follow these steps:
-
Clone the Lithosphere repository:
git clone https://github.com/WebPlatformForEmbedded/Lithosphere.git
-
Initialize the submodules:
git submodule update --init --recursive
-
On-time Buildroot setup:
make \ -C buildroot \ BR2_EXTERNAL="${PWD}/buildroot-external-metrological-restricted:${PWD}/buildroot-external-metrological-open-source" \ O=${PWD}/raspberrypi3_wpe \ raspberrypi3_wpe_defconfig
-
Build the image:
cd raspberrypi3_wpe make
or
make -C raspberrypi3_wpe
To update the Lithosphere project, follow these steps:
-
Pull the latest changes from the Lithosphere repository:
git pull
-
Update the all the submodules:
git submodule update --init --recursive
Note that to be on the safe side, you should run git submodule update with the --init flag in case the Lithosphere commits you just pulled added new submodules, and with the --recursive flag if any submodules have nested submodules.
If you encounter issues or have suggestions for improvements, please open an issue on the Thunder GitHub issue tracker. Contributions, such as bug fixes or new features, are always welcome. Please review our contribution guidelines before submitting a pull request.
Lithosphere is provided under the Apache License 2.0. Please review the LICENSE file for more details. Note that this license only covers the files provided by buildroot-submodule. It does not cover buildroot (which is GPLv2 or later) nor any software installed by buildroot (they have their own licenses) nor your own code (which you are free to license as you want).