On 30/08/15 21:00, Dave Higton wrote:
In message <out-55e2334a.md-1.4.17.chris.yo...@unsatisfactorysoftware.co.uk>
"Chris Young" <chris.yo...@unsatisfactorysoftware.co.uk> wrote:
On Sat, 29 Aug 2015 21:07:47 +0100, Dave Higton wrote:
All of us on the NS users ML were reminded recently that there is no
maintainer of the RISC OS port of NS.
I have looked a couple of times at the docs for building the various
ports of NS, but, unless I've missed something, there don't seem to
be any instructions for building for RISC OS.
I understand that it's a cross compilation on a Linux machine (or a
very long wait for every build!). I really have very little idea
what I have to install on my Ubuntu box to build NS, nor what to do
when I have the build tools.
So, have I missed something?
This, maybe?
http://wiki.netsurf-browser.org/Documentation/BuildingForRISCOSQuickStart
Ah, thanks. Now I understand why I couldn't find it - the information
is in a completely different place from that for the other platforms,
and not linked in any meaningful way from the NS website front page.
Well, so far as building things is concerned, that wiki page contains
the exact same information as is in the QUICK-START guide in the source
tree. What it does do is add some background around installing the cross
compiler binaries for those who don't want to build it from source.
I have two Linux machines in the house, both of which run Ubuntu 14.04
32 bit. I don't believe either of them is 64 bit capable. Oh well...
You can always build the RISC OS toolchain from source for your system
-- we only provide binaries for amd64 as that happens to be what all the
CI buildslaves use. The toolchain binaries are a side effect of the CI
and are not meant as a fully supported deliverable of the project.
To build the toolchain:
git clone git://git.netsurf-browser.org/toolchains.git
Then follow the instructions in the README. Note that the toolchain
build will take a number of hours to complete and is particularly
fragile, so you will have to start from scratch in the event that
something goes wrong.
Given a Linux host, is it necessary or desirable to create a separate
VM for NS development?
Not if you don't want to, no.
J.
