(2015-08-29, 15:14)stevegal Wrote: I've just got the scripts from inside one of your builds. Is that the definitive place for them? or are they on github?
In addition to the scripts being included inside each build (a form of version control), they're also uploaded to
www.nmacleod.com/public/oebuild/oebuild.tar.gz whenever there is a bug fix or configuration change, and you could consider this latter archive to always be the "latest" version.
(2015-08-29, 15:14)stevegal Wrote: If I try and the scripts straight from your build tarball I get the following
stephen@stephen-VirtualBox:~/development/milhouse.0827$ PROFILE=pi2 ./autobuild.sh
Loading profile: pi2 (./autobuild.sh)
/home/stephen/development/milhouse.0827/functions: line 356: ./config/options: No such file or directory
thats why I though I needed to do the OpenELEC.tv repo clone. With that in place it progresses. So I'm definitely missing a step somewhere!
Sorry for being a pain, and thanks again for being so good!
You definitely need to clone the OpenELEC.tv repository, I'm just saying that once the repo has been cloned you don't need to make any further manual changes to it - any changes to the repo will be made by my scripts as they're designed to handle that side of things (switch branches, pull updates etc.).
I've noticed there is a small error in the tar file included in each build - the symlinks in the "packages" folder are not valid, and this will be corrected in the next release.
I'd recommend the following approach to setting up the environment when building with my scripts:
Code:
#Ubuntu 16.04 lacks the following dependencies, so add them:
sudo apt-get install curl g++ gawk gperf xsltproc xfonts-utils default-jre libncurses5-dev texinfo ccache u-boot-tools python python3 lzop libjson-perl
#Milhouse scripts have following dependencies:
sudo apt-get install pv pxz pigz pastebinit patchutils
# Create a working directory ("projects"), clone the LibreELEC repo and install scripts to automate the build
mkdir ~/projects
cd ~/projects
git clone git://github.com/LibreELEC/LibreELEC.tv.git
wget -q www.nmacleod.com/public/oebuild/oebuild.tar.gz -O - | tar xzf -
mv build.conf.sample build.conf
In order to avoid Github API rate limiting of 60 requests/hour, create ~/.git.conf with your Github username and password - this increases the rate limit to a much more reasonable 5000 requests/hour:
Code:
GIT_USERNAME="yourgithubusername"
GIT_PASSWORD="yourgithubpassword"
Without github authentication it is unlikely you will be able to access all patches for a build before being denied further access (until the limit is reset after 60 minutes). You can use a Github
Personal Access Token in place of your password if you have enabled two-factor authentication.
Now, once you've completed the above, the following should be sufficient to start a successful RPi2 master build:
Code:
PROFILE=pi2 ./autobuild.sh
(Use PROFILE=x86 to build Generic)
Also read the file README.1ST file which is included in oebuild.tar.gz (and will be included inside future tar releases). Other files you should read: profiles.README and README.
If you want to update your installed copy of the scripts (ie. pulling latest bug fixes etc.), then repeat the above wget statement although note this will overwrite control files such as ipatches.dat, lepull.dat and profiles.dat so if you're modifying those files you'll need to reapply your own changes.
. My guess is something with OpenElec scripts rather than yours.. but not sure.