Hello.
I am yocto newbie.
Is there a variable associated with the release version available in
build/conf/local.conf(bitbake)?
I searched the yocto manual.
So I looked at "NATIVELSBSTRING" and it seems that the variable is not
appropriate in this case.
I'm wondering if there is a variabl
On Friday, 10 November 2017 8:32:36 AM NZDT Paul Eggleton wrote:
> On Thursday, 9 November 2017 9:36:26 PM NZDT Andreas Müller wrote:
> > did not find any heads up here so: Layer index stopped updating ~1,5 month.
> > Low priority - this is just notification & thanks in advance for taking
> > care
There are tags in git so I'd recommend building from the 0.3 tag instead of
a tarball. I'll make a note to try and roll a release this week.
Ross
On 19 November 2017 at 22:11, Petr Cvek wrote:
> Hello,
>
> I was playing with libfakekey and I've found the source repository at
>
> http://downloa
Hi,
I would like to know if there exists a way to build a set of package
Developer documentation. For example, many of our package are written in C/C++
and use Doxygen to generate API reference. I understand that yocto/bitbake has
some support for user documentation such as info and man pag
This is not a typical use of variables in bitbake. I'm not sure whether it is
defined behavior or not, but I doubt you'll find many such examples in the
yocto layers.
You can write
EXTRA_OECONF_remove = "--with-term=rxvt --with-name=rxvt"
in your bbappend file.
The problem with this style
Hello,
I was playing with libfakekey and I've found the source repository at
http://downloads.yoctoproject.org/releases/matchbox/libfakekey/
is a very old one.
Is this repository the official source or is it obsolete? I'm using two
linux distributions (buildroot and Slackware) and bugs on v0.
A wrong spacing in Makefile.am generates a Makefile which will refuse
to compile. This patch fixes it.
Signed-off-by: Petr Cvek
---
Makefile.am | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile.am b/Makefile.am
index c95ea0a..7d2f517 100644
--- a/Makefile.am
+++ b/Mak
Hi Martin,
There is a warning with absolute path symlinking, I made a patch to replace
all occurence of
ln -sf ${JDK_HOME}/bin/*
by
ln -sf ../lib/jvm/${JDK_DIR}/bin/*
but didn't get integrated.
Best regards,
Vincent
2017-11-17 12:47 GMT+01:00 Martin Nordqvist :
> Create symlinks in bindir to ja
Current Dev Position: YP 2.5 Planning and M1 development
Next Deadline: YP 2.5 M1 cut off of 12/4/17
SWAT team rotation: Juro -> Paul on Nov.17, 2017.
SWAT team rotation: Paul -> Todor on Nov. 24, 2017.
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
·
During the build it wont/can't use the target python as that won't be
compatible (say x86-64 host, ARM target). This isn't a problem.
Ross
On 20 November 2017 at 14:52, Amit Gondaliya
wrote:
> Hello All,
>
>
> I am configuring one package and found the following error.
>
>
>
>
>
>
>
>
> * File
Hello All,
I am configuring one package and found the following error.
File "/usr/lib/python2.7/subprocess.py", line 567, in check_output
process = Popen(stdout=PIPE, *popenargs, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
File "/usr/lib/
在2017年11月20 22时16分, "Burton, Ross"写道:
> There's numerous u-boot recipes out there, including on in oe-core.
> Ideally customise the u-boot in oe-core instead of writing your own recipe
> from scratch.
>
> Ross
Thanks for your help, I finally solved this problem as below:
# u-boot_2017.09.bbap
There's numerous u-boot recipes out there, including on in oe-core. Ideally
customise the u-boot in oe-core instead of writing your own recipe from
scratch.
Ross
On 20 November 2017 at 12:07, cddatemp wrote:
> At 2017-11-20 19:35:31, "Burton, Ross" wrote:
>
> inherit native to make the recipe
hi,
I managed to customise it , using toaster interface. However, now I am
on cmdline.
What is the way to do the same thing from cmdline, which file to copy
and rewrite ?
Regards,
S.Ancelot
Le 20/10/2017 à 10:46, Stéphane Ancelot a écrit :
This works as expected, Thanks
Le 19/10/2017
Hello
Now I am able to build the Package "Y" as non native and I found the binary
under below path.
/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/Y/0.1.0-r1/package/usr/bin.
But my package "X" is not able to find the package "Y" It still shows me that
Package "Y" is missing.
please find th
At 2017-11-20 19:35:31, "Burton, Ross" wrote:
inherit native to make the recipe native.
It really help, when my recipe is just a helloworld python extension.
Unfortunately, this recipe is u-boot.
It will compile a native python extension named "libfdt", then use it to
compile u-boot.
So I cann
A good start would be to remove the inherits you don't need such as
autotools-brokensep. And the empty do_configure() do_compile() functions.
You're not telling install where to install which is why the files are
going into the sysroot and not packaged up. Just delete your do_install()
and let the
inherit native to make the recipe native.
Ross
On 20 November 2017 at 11:33, cddatemp wrote:
> Hi,
>
> I add "inherit distutils" in my recipe.
> It will make my recipe depends on "python-native" and "python".
> Finally it use arm-gcc to build the python extension.
> But I want to use x86-gcc to
Hi,
I add "inherit distutils" in my recipe.
It will make my recipe depends on "python-native" and "python".
Finally it use arm-gcc to build the python extension.
But I want to use x86-gcc to build a native python extension.
How to do this?
Best Regards
cddatemp--
__
Hello,
In our case the Package is "Y" but all the data falls into the
recipe-sysroot-native of "Y." any Idea what's wrong with Y.
is there any example of "Y-native" that help me to generate "Y-native"" from "Y"
Please find the attached file of Y.bb
Best Regards,
Amit Gondaliya
__
At 2017-11-20 18:18:42, "Amit Gondaliya" wrote:
> Hello,
>
> I am configuring one package "X" that is depended on other package "Y".
>
> the "Y" package is successfully build and I am able to find it into the below
> path.
>
> tmp/work/cortexa8hf-neon-poky-linux-gnueabi/"Y"/0.1.0-r1/recipe-sysr
Hello,
I am configuring one package "X" that is depended on other package "Y".
the "Y" package is successfully build and I am able to find it into the below
path.
tmp/work/cortexa8hf-neon-poky-linux-gnueabi/"Y"/0.1.0-r1/recipe-sysroot-native/usr/bin
As per my understanding if the package
22 matches
Mail list logo
