t
like that? I can't find anything about that in Yocto docs.
I believe I'll be able to create the sdk with command like bitbake
-c populate_sdk. I added "inherit populate_sdk_base" to
.bb. Is that a correct way?
BR,
Marek Andrus
--
_
where preffered providers are set). Of course OVERRIDES variable
is not set either.
What do you recommend?
Of course I can change the toolchain layer manually but I wanted to
change machine/architecture in just one place. Is there any method?
BR,
Marek A
I've found a problem. TARGET_ARCH in fact isn't set but I can still use
conditional syntax. The problem was I was trying with ppc architecture
(TARGET_ARCH is later set to ppc) but here I had to use "powerpc" instead.
BR,
Marek Andrus
On 05.06.2014 13:02, Marek Andrus w
ysroot. So
probably the question should be like this: how to put anything into /usr
or / in sysroot?
BR,
Marek Andrus
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Hi,
I use external toolchain and 'm trying to do populate_sdk. I get a
strage output. First bitbake tells me, that:
DEBUG: providers for eglibc are: ['eglibc']
DEBUG: sorted runtime providers for eglibc are:
['/home/marek/yocto/poky/meta/recipes-core/eglibc/eglibc_2.19.bb']
(it is not the o
I've found the solution. I created a function (fun) and added it to the
functions called during populate_sysroot:
SYSROOT_PREPROCESS_FUNCS += "fun"
The function fun does the work: ln -s lib ${SYSROOT_DESTDIR}usr/lib64
BR,
Marek
On 11.06.2014 13:33, ext Marek Andrus wrote:
Hi,
I'd like to tell bitbake not to build python for target, but I still
want python-native.
If I add
ASSUME_PROVIDED += "python"
it stops building both python and python-native. If it add
ASSUME_PROVIDED += "python-native"
it stops building just python-native.
What to do to prevent b
