|jravetch f4f660d032 Merge pull request #4 from jravetch/fix-dockerfile||3 years ago|
|config||4 years ago|
|custom-files||4 years ago|
|files||4 years ago|
|include||4 years ago|
|package||4 years ago|
|release||4 years ago|
|scripts||4 years ago|
|target||4 years ago|
|toolchain||4 years ago|
|tools||4 years ago|
|.config||4 years ago|
|BSDmakefile||4 years ago|
|CHANGELOG.md||3 years ago|
|Config.in||4 years ago|
|DISCLAIMER.md||4 years ago|
|Dockerfile||3 years ago|
|LEDE-README.md||4 years ago|
|LICENSE||4 years ago|
|Makefile||4 years ago|
|README.md||3 years ago|
|build.sh||4 years ago|
|build_info.json||4 years ago|
|feeds.conf||4 years ago|
|feeds.conf.default||4 years ago|
|first.txt||4 years ago|
|prepare.sh||4 years ago|
|rules.mk||4 years ago|
This buildsystem for the LEDE Linux distribution has been modified by Onion Corporation to build firmware for the Oboo Smart Clock
Onion Corporation is not responsible for any damage to your device caused by using custom firmware, custom packages, or any other customization activities.
CHANGELOG.mdfor a listing of the changes for each firmware version and build
DISCLAIMER.mdfor Onion’s disclaimer regarding this build system
This buildsystem can be used to create packages and firmware for the Oboo Smart Clock. There are two preferred ways to use the buildsystem:
The Docker image takes care of all environmental configuration and is the recommended method.Using this method creates a Docker image that can be used to compile the Oboo Smart Clock build system See this link for more details: https://docs.docker.com/get-started/part2/
System requirements for running this build system:
The better the specs of the computer (more CPU cores, more memory) the faster everything will compile. On an 8-core, 16 GB RAM machine the initial compile will take about half an hour.
Clone the repository by running:
git clone email@example.com:ObooSmartClock/Oboo-Source.git
Change into the
Build and tag the docker image by running:
docker build -t oboo-source/oboo-source -f Dockerfile .
This will produce a docker image with the following artifacts:
To access the the built artifacts, run and mount the docker image to your local filesystem:
docker run oboo-source/oboo-source \ -v ~source:bin/targets \ -v ~packages:bin/packages \ -it /bin/bash
Firmware binaries contain an image of the Oboo Smart Clock Linux Operating System. Incorrectly flashing firmware or flashing broken firmware can lead to a bricked device! Proceed with extreme caution! Onion Corporation is not responsible for any damage to your device caused by using custom firmware or packages not built and released by Onion Corporation.
Oboo package files can be installed on Oboo Smart Clock. Transfer the desired
*.ipk file to the target Oboo Smart Clock’s filesystem, and use
opkg install <IPK NAME HERE> to install/update the package.
This procedure must be done on an Ubuntu system, as it requires specific software packages in order for the build to succeed. System requirements for running this build system are similar to the Docker method:
Required additional software packages:
sudo apt-get update sudo apt-get install -y \ build-essential \ vim \ git \ wget \ curl \ time \ subversion \ build-essential \ libncurses5-dev \ zlib1g-dev \ gawk \ flex \ quilt \ git-core \ unzip \ libssl-dev \ python-dev \ python-pip \ libxml-parser-perl \ default-jdk
When run, the build system outputs firmware binaries and package files for the Oboo Smart Clock.
To setup and compile the build system, run the following command:
Each time a commit or Pull Request is pushed to the
master branch, the CD system will be automatically triggered to compile the build system.
The output ipk files from
bin/packages/mipsel_24kc/oboo/ will be made automatically available at: http://repo.getoboo.com/oboo-clock/packages/latest/