Last new thread for today, honest :-)
I'd like to be able to install the app-tools and rumprun toolchain on the
host system, i.e. provide a "make install". Again, this is about making
things work as people would expect them to. AFAICT from some of the recent
discussion on IRC about getting Xen OSStest working they would benefit from
this, the other obvious motivation is future distro packaging of prebuilt
toolchains.
Current best practice [1] for a toolchain is to install it to a directory
hierarchy located below $PREFIX (e.g. /usr/local/) and $ARCH (e.g.
arm-rumprun-netbsd). The hierarchy looks something like this:
. Toolchain root directory. Could contain a setup.sh script as
suggested by Antti, for instance.
./bin/ Toolchain tools, needs to be added to $PATH to use the
toolchain. Contains $ARCH-gcc, $ARCH-ld, etc.
This would also be where the 'rumprun' tool is installed, so
that multiple versions can be installed side by side (which
won't work if it just goes in $PREFIX/bin).
./include/ Toolchain headers. Would contain what we now have in
platform/$PLATFORM/rump/include after a build.
./lib/ Toolchain libraries. Would contain what we now have in
platform/$PLATFORM/rump/lib after a build.
./libexec/ This would be where I would put the remaining components
needed for linking (mini-os.o, rumprun.o, ldscript).
Does this work for everyone? Any toolchain experts on the list please speak
up!
For in-tree and development use without installation, we could just make
$PREFIX = $SRCDIR or $SRCDIR/build.
Martin
[1] See e.g. the musl-cross toolchain, source repo at:
https://bitbucket.org/GregorR/musl-cross, prebuilt binaries at
http://musl.codu.org/
