On 01/16/2014 01:07 AM, Artur Kozak wrote:
Hello,
Hi
with my colleagues we are attempting to run Tizen on RaspberryPi.
First, we installed Raspbian on the device. After a bit of tweaking
compiled and replaced its kernel. Then we managed to manually build
some light-dependency packages (like grep) from Tizen's repository and
install them on Raspbian. So, we have a working toolchain for the
proper architecture, exactly armv6j-hardfloat-linux-gnueabi. Now we'd
like to use GBS to build bigger parts of the system, and a few
questions arise:
(a) What is the difference between armv6j, armv6k, armv6l? I read that
RPi is armv6k, but some sources, e.g. gentoo forums, advised using
armv6j toolchain. In the v6 family only armv6l is supported by GBS,
will it be compatible?
As far as I know armv6j adds native java code execution support, armv6k
adds some new instructions.
I guess you should be fine with using armv6l - generated code won't use
all available features, but that's ok for basic bring-up.
(b) If yes, how to tell GBS to use our own toolchain for it?
(c) If not, how to add new architecture profile for armv6j/k with our
toolchain to the GBS?
GBS doesn't cross-compile, but rather sets up build environment and the
commands are invoked by qemu in chroot environment, so in fact gbs
compiles natively for ARM. I'm not sure armv6j-hardfloat-linux-gnueabi
would be compatible with gbs for that reason.
Major problem I see with GBS is that it needs set of RPM packages to
create its build environment and I don't know if they are available
somewhere for armv6l architecture on download.tizen.org ( I suppose they
don't ). This means you need to build and package them somehow. On the
other hand if gbs supports armv6l it was probably tested, so minimum set
of packages for performing build with gbs should be available somewhere.
Alternatively, you could modify build options in spec files so armv6l
code is generated, but with armv7l build environment used. But that's
just a quick idea and I even don't know if it's possible/reasonable.
gbs code pointed us to a script named 'depanneur', but after spending
*some* time above it we couldn't find the answer to (b) and (c). Any
tips (or directions where to get them) would be appreciated.
To my knowledge, depanneur is just for package dependency resolution.
I'd rather investigate "build" package - /usr/bin/build primarily to
some more information.
Thanks in advance & best regards,
Artur Kozak
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
Regards,
--
Jacek Bukarewicz
Samsung R&D Institute Poland
Samsung Electronics
[email protected]
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
