Forked from https://github.com/freifunk-gluon/gluon

Nils Schneider f9485b8c95 docs: initial sphinx project with very little content 10 years ago
docs f9485b8c95 docs: initial sphinx project with very little content 10 years ago
include ae46850d34 profiles: Add ubiquiti unifi ap outdoor 10 years ago
kernel 1c170c65f7 Update kernel config to 12.09 release 10 years ago
patches c12508ef57 Make jshn use 64bit integers 10 years ago
scripts 58584018de Add array support to the simple generate script (doesn't work with spaces) 10 years ago
.gitignore 7537464262 Nicer feed specification 10 years ago
LICENSE bfcc3d9149 Move package submodules to packages/ 10 years ago
Makefile a9eb44b41a Fix removal of old images 10 years ago
README.md 33151cd601 README.md: typo 10 years ago
modules a95a547130 Update gluon packages 10 years ago

README.md

To build Gluon, after checking out the repository change to the source root directory to perform the following commands:

git clone git://github.com/freifunk-gluon/site-ffhl.git site # Get the Freifunk Lübeck site repository - or use your own!
make update                                                  # Get other repositories used by Gluon
make                                                         # Build Gluon

When calling make, the OpenWRT build environment is prepared/updated. To rebuild the images only, just use:

make images

The built images can be found in the directory images.

For the build reserve 6GB of disk space. The building requires packages for subversion, ncurses headers (libncurses-dev) and zlib headers (libz-dev).`

There are three levels of make clean:

make clean

will only clean the Gluon-specific files;

make cleanall

will also call make clean on the OpenWRT tree, and

make dirclean

will do all this, and call make dirclean on the OpenWRT tree.

Development

Gluon IRC channel: #gluon in hackint

To update the repositories used by Gluon, just adjust the commit IDs in modules and rerun

make update

make update also applies the patches that can be found in the directories found in patches; the resulting branch will be called patched, while the commit specified in modules can be refered to by the branch base.

make unpatch

sets the repositories to the base branch,

make patch

re-applies the patches by resetting the patched branch to base and calling git am for the patch files. Calling make or a similar command after calling make unpatch is generally not a good idea.

After new patches have been commited on top of the patched branch (or existing commits since the base commit have been edited or removed), the patch directories can be regenerated using

make update-patches

If applying a patch fails because you have changed the base commit, the repository will be reset to the old patched branch and you can try rebasing it onto the new base branch yourself and after that call make update-patches to fix the problem.

Always call make update-patches after making changes to a module repository as make update will overwrite your commits, making git reflog the only way to recover them!