Hello.
I am seeing some of the recipes contains lines like below.
> COMPATIBLE_MACHINE = "(-)"
Sorry being novice, but what is the intended effect of this line?
I can see submit comments that this is for blacklisting but I am not sure how
it works. It simply means a '-' letter?
--
Helli, thank you for your confirmation.
From: Burton, Ross <ross.bur...@intel.com>
Sent: Wednesday, August 2, 2017 8:47:00 PM
To: Takashi Matsuzawa
Cc: Khem Raj; yocto@yoctoproject.org
Subject: Re: [yocto] local file update vs rebuild
If you modify a
te to ).
From: Khem Raj <raj.k...@gmail.com>
Sent: Tuesday, August 1, 2017 3:42 AM
To: Takashi Matsuzawa; yocto@yoctoproject.org
Subject: Re: [yocto] local file update vs rebuild
On 7/31/17 4:39 AM, Takashi Matsuzawa wrote:
> Hello.
> I am uncertain about do_clean behavior with
Hello.
I am uncertain about do_clean behavior with local files.
Say, I have local files referred by my recipe, and I have made changes to the
files referred.
(Note, there is no change in my .bb file itself.)
>SRC_URI += "file://src/*;subdir=local"
What makes those changed files
Hello.
I recently purchased Terasic DE10-Nano Kit board, and I wonder how I can build
Linux image for it.
(Though it comes with binary SD card.)
I can see below, and I tried meta-de10-nano/REDME.md steps (priecisely it is
not yocto?), but I met errors during bitbake.
Hello.
>yes you can do that via a local.conf entry like
>
>PARALLEL_MAKE_pn-qtwebengine = "-j 8"
Thank you this seems to work very well.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Hello.
I am seeing issue with threads/parallel make. I wonder if anyone has
experience/suggestion.
My question: is if it is possible that I set parallel make numbers to lower
only for a few recipes that are known to resource hog?
I am building webkig/chrome related recipes (e.g. qtwebengine
.
From: Takashi Matsuzawa
Sent: Thursday, May 25, 2017 3:26 PM
To: yocto@yoctoproject.org
Cc: Nicolas Dechesne
Subject: Re: [yocto] dynamic-layers?
Hello.
I further did some debugging and BBFOLE_COLLECTION when used in the following
'for' expansion contains only subset of what is avilable
meta-freescale-3rdparty/recipes-*/*/*.bbappend
...
From: Nicolas Dechesne <nicolas.deche...@linaro.org>
Sent: Wednesday, May 24, 2017 11:19 PM
To: Takashi Matsuzawa
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] dynamic-layers?
On Wed, May 24, 2017 at 12:30 PM, T
Hello, Yocto.
I am a bit confused with dynamic-layers included in some of the recent layers
in various BSPs.
e.g.
https://github.com/Freescale/meta-freescale/blob/master/conf/layer.conf
># The .bbappend and .bb files are included if the respective layer
># collection is available.
>BBFILES +=
Hello.
>AAA_xxx_yyy = "true"
Thank you, I will try. I could not figure out but I feel it should work.
From: Paul Eggleton <paul.eggle...@linux.intel.com>
Sent: Thursday, April 13, 2017 2:23 PM
To: Takashi Matsuzawa
Cc: yocto@yoctoproj
Hello, Yocto.
I just wonder if there is convenient way of defining somthing in recipes based
on combination of two OVERRIDES variables.
Say, I have two variables xxx and yyy.
AAA = "false"
AAA_xxx = "true"
AAA_yyy = "true"
But what if I want to set AAA to be "true" only when xxx and yyy are in
Hello, Yocto.
I wonder which is the common / recommended way of preparing a recipe for the
following project?
I have a source tree with 2 subdirectories A, B.
Both A and B are cmake based source trees - each has CMakeLists.txt file of its
own.
Then, when I build I would:
- checkout sync source
I am sorry please ignore below.
I should put space after -D options so that cmake won't complain.
From: Takashi Matsuzawa
Sent: Friday, March 24, 2017 9:08 PM
To: yocto@yoctoproject.org
Subject: quoted string in a recipe variable?
Hello, Yocto.
I am a bit
Hello, Yocto.
I am a bit confused with recipe syntax for variable assignment.
I wanto embed double-quoted string within a variable.
And I tried below and looks like the whole part of the string (A to B) is
successfully assigned to EXTRA_OECMAKE variable.
EXTRA_OECMAKE = " \ <-- A
"-D
Hello, Yocto.
I have looked into recipes index, etc. but I so far I could not figure out
clear answer, so if you have status on this, I highly appreciate.
I am looking for a web browser that can (without much effort) be built and run
on Yocto based environment, with wayland-only window
Hello.
I found hddimg 4GB-1 bye restriction because it creates a file called
rootfs.img which is copied into FAT.
That means rootfs.img size must be below FAT max file size...
From: Takashi Matsuzawa
Sent: Thursday, March 9, 2017 1:51 PM
To: yocto
Hello, Yocto.
I have looked into hddimg file.
According to image-live.bbclass, it is hardcoded to maximum 4GB size.
But should not this more large?
hddimg is generated by mkdosfs -F 32 that means the filesystem capacity is
larger than 4GB.
I just hit this limit when generating an image
Hello, Yocto.
Maybe a basic question but I am being puzzled.
i) Recipe A builds module, and the module expects that xkbcommon.pc is
available (checked in autotool by calling pkg-config)
ii) module A build fails, since it cannot find xkbcommon.pc, according to the
config.log.
(in
com>
Sent: Thursday, February 16, 2017 11:53 AM
To: Takashi Matsuzawa
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] meta-efl build?
Takashi-san
On Wed, Feb 15, 2017 at 6:35 PM, Takashi Matsuzawa <tmatsuz...@xevo.com> wrote:
> Hello, Yocto.
>
>
> I am trying to build
Hello, Yocto.
I am trying to build EFL on top of my mayland environment (krogoth based).
I thought it would be easy since there is meta-openembedded/meta-efl recipes,
but now I am stuck.
Specifically, I am experiencing x11 dependency (the recipes erquire x11 to be
in DISTRO_FEATURES here
well with VM, other
thna its 'safe' behavior?
That is my concern.
From: Burton, Ross <ross.bur...@intel.com>
Sent: Saturday, February 4, 2017 8:20 AM
To: Takashi Matsuzawa
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] genericx86 vs qemux86
On 3 Februar
Hello, Yocto.
Sorry, I am still a bit confused with genericx86 and qemux86 targets. What is
their difference and which one to choose.
Both are x86 target and maybe genericx86 has more support for PC hardware?
qemux86 has v86d?
genericx86 is from poky and qemux86 is from openembeded?
I am
Hello, I just tried and the below seems to be the fix.
https://patchwork.openembedded.org/patch/11/
From: Takashi Matsuzawa
Sent: Thursday, February 2, 2017 3:25 PM
To: yocto@yoctoproject.org
Subject: Ruby and OpenSSL version mismatch?
Hello, Yocto.
I am
Hello Yoct.
Say, BSP defines something like this.
BBMASK .= "|msta-//.bb"
Then I want to cancel this within my local.conf. Should putting below in my
local.conf works? (Or within my bistro/.conf?)
BBMASK_remove = "|msta-//.bb"
--
Hello, Yocto.
I am trynig a build of fido based yocto image, with openssl 1.0.2j for security
reason.
The openssl recipe itself builds successfully, but later in the build I see
error in jscore.
In fact, ruby is complaining that 'OPENSSL_1.0.0' is not available.
|
Well, doing repo -diff and apply produced patch when I newly repo sync could
work.
https://groups.google.com/forum/#!topic/repo-discuss/43juvD1qGIQ
From: Takashi Matsuzawa
Sent: Monday, January 30, 2017 11:00 AM
To: yocto@yoctoproject.org
Subject: patching
system?)
From: Takashi Matsuzawa
Sent: Saturday, January 28, 2017 11:58 AM
To: yocto@yoctoproject.org
Subject: pkg_postinst shell?
Hello Yocto.
I am debugging my recipe, which uses pkg_postinst but does not seem to work as
expected.
It runs fine without $D detection
Hello Yocto
I am curious if there is a better way of doing this manually every time I
re-synch to Yocto based BSP.
Say, I have a patch or customization I want to try on .bbclass files (instead
of .bb or .bbappend, or the source files that are fetched.)
The reason for this is sometimes I want to
Hello Yocto.
I am debugging my recipe, which uses pkg_postinst but does not seem to work as
expected.
It runs fine without $D detection.
However, if I try to run it at first boot (skipping with exit 1 if $D is not
empty), the board boot seems to hang.
I think error (syntax error, etc.?)
Hello Yocto.
Though it may feel to me matter of taste, is there suggestion on when which of
these to use when you need to define your customized feature.
DISTRO_FEATURES seems to be more relaxed, you can define things in your distro
conf.
IMAGE_FEATURE seems to be more strict, and you need to
Hello.
I have following recipe files and want to remove .patch added to SRC_URI at
ii).
i) _git.bb - specifies RC_URI revision by SRCREV parameter
ii) _%.bbappend - adds several .patch to SRC_URI
iii) _%.bbappend - my recipe
I want to make it (removal) conditional to
Hello.
Thanks it worked for .iso files.
I have found that this really is a save for build time also.
From: Jussi Kukkonen <jussi.kukko...@intel.com>
Sent: Friday, December 16, 2016 6:22 PM
To: Takashi Matsuzawa
Cc: yocto@yoctoproject.org
Subject: Re:
Hello Yocto.
I am trying x86-64 BSP image (based on jethro version).
It has following root filesystem type, and it generats .hddimg file that I
am using.
> IMAGE_FSTYPES = "live"
The issue is that in addition to .hddimg, it produces following image files
and it sometimes cause lack of
Hello Yocto.
I recently encountered following issue with Python module cross-build.
(On Yocto 2.0 based build system, using distutils.bbclass)
http://bugs.python.org/issue28421
Firstly I believed it is a Python issue, but further looked into, Yocto build
environment has some cutomization
OK, I figured this out that I can add my BBMASK lines to my
conf/distro/xxx.conf fille.
So that I can append to what BSP defines and it seems to happen before
collect_bbbfiles() function.
Sorry for my confusion.
From: Takashi Matsuzawa
Sent: Friday, September
Well, I tried adding debug lines to poky/bitbake/lib/bb/cooker.py, and I think
what is happening is:
i) BSP has BBMASK = line.
ii) I add BBMASK_forcevariable = line to my local.conf
iii) If I check with -e option, I can see BBMASK variable is finally set to
""
iv) However, when
Hello, Yocto.
I am quite puzzled with this and spent a few hours today so far.
In case you have any comment or suggestion, it would be a great help.
I am trying to hide one of the .bbappend files from the tree, so that BB
won't complain "ERROR: No recipes available for:" error.
I did add
.ha...@windriver.com>
Sent: Friday, September 9, 2016 11:46 PM
To: Takashi Matsuzawa; yocto@yoctoproject.org
Subject: Re: [yocto] ac_cv_sizeof_long size definition by SDK
On 9/9/16 6:33 AM, Takashi Matsuzawa wrote:
> Hello, Yocto.
>
>
> I am now puzzled by this variable ste in $CONF
Hello, Yocto.
I am now puzzled by this variable ste in $CONFIG_SITE setup file in
Yocto-generated SDK.
I generated x86_64 host, arm (32bit) target SDK.
And if I invoke $CC (arm-poky-linux-gnueabi-gcc), using this SDK, sizeof (long)
is 4 (long = int)
However, if I look into $CONFIG_SITE's
Hello, Yocto.
I just want to confirm how pkg_postinst scripts are called.
Provided the following scripts are provided, in two bbappend recipes as below,
which of them are actually executed and which are not?
I have briefly tried and 'OK's below are called and 'NG's are not.
The yocto manual
Hello Yocto.
I am trying to build and run vlc on my fido based environment (genericx86
machine), but so far failing to play most of the multimedia files.
I just wonder any of you have similar experience and hopefully has a clue.
vlc player build OK without problem, by just adding vlc by
Hello Yocto.
This may be a novice question, but just in case you have suggestion:
Debugging pkg_postinst script is simply taking time for me, since I wait rootfs
creation to confirm its result.
This is a overkill since rpm creation is just a few min, but generating whole
rootfs takes hours.
Hello.
>Please note that BBMASK was changed in Krogoth to allow multiple regular
>expressions (see commit a948f5252 in Poky). Basically, with Krogoth and
>later you can do:
>
>BBMASK = "aaa bbb ccc"
>BBMASK += "ddd eee"
>BBMASK_append = " fff ggg"
This is good, since everyone can always do
Hello Yocto.
Now I am trying to customize an existing BSP to my need.
For this, I am adding following to my local.conf so that some of the recipes in
the BSP to be ignored.
(local.conf)
BBMASK = "aaa|bbb|ccc"
BBMASK .= "|ddd|eee"
However, it does not work since BSP itself has lines like below
Well, I could workaround below by patching configure.ac of the package.
May not really have been an yocto issue..
From: Takashi Matsuzawa
Sent: Friday, July 22, 2016 1:01 PM
To: yocto@yoctoproject.org
Subject: autotool __init_array_end not found
Hello Yocto.
I
Hello Yocto.
I am now trying to build autotool based (inherit autotool) recipe on Yocto 2.0
based environent.
Howerver, I am seeng following error.
I wonder if this is a known problem and you already have workaround?
It says __init_array_end/start is not found which is referred in
opy genericx86.conf to
build/conf/machines/generix86.conf (into local conf file folder) and do
necessary modification to it.
So that I can cancel whatever IMAGE_FSTYPES value set by x86-base.inc.
____
From: Takashi Matsuzawa
Sent: Friday, July 15, 2016 11:25 AM
To: Maxi
bbclass
should never interpreted?
> # $IMAGE_TYPE_live
> # set
> /mnt/ssd2/yocto/dev/wk/x86/wk3/build-root/sources/poky/meta/classes/image.bbclass:129
> # "${@build_live(d)}"
> IMAGE_TYPE_live=""
I tried BBMASK'ing image-live.bbclass, but it still
@intel.com>
Sent: Thursday, July 14, 2016 12:16 AM
To: Takashi Matsuzawa
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] image-vmdk with genericx86
Hi Takashi-san,
On Wed, Jul 13, 2016 at 10:51:34AM +, Takashi Matsuzawa wrote:
>Hello, Yocto.
>
>Should it be possible to simply chan
Hello, Yocto.
Should it be possible to simply change image class of genericx86 from
.hddimg to .hdddirect?
I have been successfully building genericx86 image (that is image-live.bbclass
based), and now trying to build it with directdisk (.hdddirect).
I thought it would be
s.l...@bmw-carit.de>
Sent: Thursday, July 7, 2016 4:45 PM
To: Takashi Matsuzawa
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] linux/limits.h: No such file or directory
Hi,
Takashi Matsuzawa <tmatsuz...@uievolution.com> wrote:
> >configure: error: C preprocessor "x86_
Hello Yocto.
I am seeing this error recently, and wonder if it is a known issue that has a
workaround.
It does not go even if I delete DL_DIR or SSTATE_CACHE, etc. It started to
happen, though previously the build ran well.
>configure: error: C preprocessor "x86_64-pokysdk-linux-gcc -E
;
Sent: Tuesday, July 5, 2016 3:50 AM
To: Marcelo E. Magallon
Cc: Takashi Matsuzawa; yocto@yoctoproject.org
Subject: Re: [yocto] Shorter build time?
On 4 July 2016 at 19:10, Marcelo E. Magallon
<marcelo.magal...@hpe.com<mailto:marcelo.magal...@hpe.com>> wrote:
That is true, but I'v
Thank you for your comment.
So they are. I will try to mask them one by one then.
From: Peter Bergin <peter.ber...@tritech.se>
Sent: Friday, July 1, 2016 1:05 PM
To: Takashi Matsuzawa; yocto@yoctoproject.org
Subject: Re: [yocto] ICECC build failures?
Hi,
faster.
From: Daniel. <danielhi...@gmail.com>
Sent: Saturday, July 2, 2016 2:13 AM
To: Burton, Ross
Cc: Takashi Matsuzawa; yocto@yoctoproject.org
Subject: Re: [yocto] Shorter build time?
So we have full parallelism :)
2016-07-01 14:01 GMT-03:00 Burton
Hello Yocto.
Well, this may not be a very new topic, but I wonder if you have recent
suggetions.
So far I have tried the followings and see some improvement, making the build
time to days to hours.
1) All of the directories, DL_DIR, SSTATE_CACHE, TMPDIR, DEPLOY_DIR are on SSD.
2) .repo and
Hello Yocto.
Recently I am trying icecc with bitbake and amd halfway satisfied.
Good to see batch of my compilation jobs consumed by my build machines on icemon
is not bad.
However, I can see my builds fail in certain condition eveytime and
wonder if it is a known issue and a workaround exists?
Hello yocto.
I have been successfully building several yocto based target trees,
but now trying qemux86-64 build and it is causing error. Familiar
with the below sympthom and maybe you have any suggestion?
I think this begain happening when I did -c populate_sdk, but not sure.
The other targets
59 matches
Mail list logo
