Merge branch 'development'
* development: Make config ready for stable release Config beta build First adjustments for beta build Fixing issue with wrong development repo path Updated openwrt snapshot config enable piratebox feed inside openwrt Adjustments for migration from SVN to git first fixes First try to move over to new openwrt-piratebox-feed handling First changes for LibraryBox-Stable build integrated with PirateBox Try to exchange both versions of repository URL Integrating LibraryBox and Beta build for it Use updated beta branch of openwrt-piratebox-feed - Uses included pbxopkg - Uses new pbxmesh (formaer piratebox-mesh) package - Includes new config file for those packages - Sets environment to LC_ALL=C to support new grep that threads ISO files as binary
|3 years ago|
|configs||3 years ago|
|.gitignore||4 years ago|
|Makefile||3 years ago|
|README.md||4 years ago|
|auto_screenrc||5 years ago|
|ftp_config.sh.example||5 years ago|
|image_helper.sh||5 years ago|
|infos_about_PirateBoxScripts.txt||5 years ago|
|start_autobuild.sh||5 years ago|
This is a collection of scripts and documentation for developing on scratch on PirateBox-OpenWRT packages, images and related things. All of the commands in the Makefile are customized or assume, that you don’t rely on the current stable source.
This repository is intended to get you started with a development environment to build your own PirateBox images - no matter if you just want to enable an additional OpenWRT feature, remaster your PirateBox image or start developing for the PirateBox.
Make sure you have the loop kernel module loaded:
Make sure you have at least 8BG free disk space
Make sure you have the following packages installed:
There are two methods to build the image:
Use the local feed variant if you want to use other branches than the master or development branch or if you want to pull in your own packages.
The Makefile comes with four auto build targets, you start them, lean back and wait for the finished images. They at some point all require you to enter the root password, so you either need to wait until you are prompted to input your password or set your sudo timeout to unlimited, do some action as sudo in the current terminal and than start the build process.
Will build the stable release with the master branch of the openwrt-piratebox-feed.
Will build the beta release with the development branch of the openwrt-piratebox-feed.
Will build a snapshot release, using a local feed including the develompment branches of packages otherwise pulled in via the openwrt-piratebox-feed.
Will build a release using all the packages from the _localfeed folder, but without changing branches. It will use all the packages at the set branch and build from there. This is the best way to implement and test your own changes, using exactly the branches you want.
Find below the steps described each of the automated targets uses. The PirateBox feed variant is described in detail, other variants are described in how they differ from the PirateBox feed variant.
To build your PirateBox image with the master branch of the openwrt-piratebox-feed execute the following steps in order:
Clone and configure OpenWRT and clone the image build script
Detailed information about the OpenWRT build system may be found in the OpenWRT Wiki:
Apply the PirateBox OpenWRT feed
You can learn more about feeds on the feeds page in the OpenWRT wiki.
Update all feeds
Install the PirateBox OpenWRT feed
Create the piratebox script image
If you have more than four cores, do not forget to adjust the THREADS variable in the Makefile.
This will copy the default kernel config and start building OpenWRT.
The THREADS variable in the Makefile needs to be adjusted to your system, a good rule of thumb for the value is to use the amount of cores you have available on your build machine.
Building the OpenWRT image may take a long time, depending on your machine, up to a couple of hours.
Aquire missing packages
There are a couple of packages that did not make it in the OpenWRT repo yet, so you need to acquire them manually:
Start local repository
After building OpenWRT you can start your local repository:
This will start a python http server on port 2342. If you now surf to http://localhost:2342 you can verify that the repository is up and running. If you want to change the port of the local repository, set it in the Makefile.
Build the PirateBox image
To build the PirateBox image and install.zip run:
Stop the local repository After building the image you can stop your local repository:
Enjoy your build
You should now have a directory called target_piratebox in the openwrt-image-build directory. This directory contains all supported firmware images and the install_piratebox.zip
You can now continue with the auto installation step.
The local feed variant only differs in a couple of steps from the piratebox feed method. If you want to add your own repositories to the local feed, create a local feed directory
And add your repositories. Then run the steps from above.
Instead of Step 2 you run:
Instead of Step 4 you run:
make install install_local_feed
Skip Step 7, because the packages downloaded in this step are build from source when using the local feed variant.
There are two different clean targets:
Will clean the openwrt-image-build directory and the openwrt directory. It will however not delete the OpenWRT toolchain. It will also stop the local repository in case it is still running. This is also the first step executed when using any of the auto build targets.
Will do the same as clean, but will also delete all directories and files pulled in while building. The directory will basically look like after a fresh clone.
Run make in the openwrt folder single threaded and with the S=v flag to get detailed output:
This table is a short overview of build times on different systems. Initial is the time it took to build the first image, including toolchain. Following is the time it takes to build once the toolchain is available. Those values are by far not exact. Throughout the build process a lot of packages are fetched of the internet, so your speed also plays a big role. The times are intended to give you a bit of a feel of how long it will take you to build.
|Intel i7-4700MQ CPU @ 2.40GHz||8||8||8GB||45:46||28:22|