Re: [yocto] How to specify a different kernel for an image

[Gabriele Zampieri]

Hi,

you could define two machines, where the manufacturing one is just an
overlay of the production one. If the two kernels differs only for their
config, you can specify different defconfig based on machine. If you need a
completely different kernel, just specify
PREFERRED_PROVIDER_virtual/kernel in manufacturing overlay

Best regards,
Gabriele

Il giorno gio 18 lug 2019 alle ore 23:27 Patrick Doyle 
ha scritto:

> Hello All,
> I have a situation where I need to build an image for my machine with
> a different kernel than is specified by
> PREFERRED_PROVIDER_virtual/kernel.  But I also need to build the
> default kernel.  This is for a "manufacturing" image which will
> include the full production image, and then some (and, possibly,
> without some).  The kernel configuration needs to be different for the
> manufacturing image.
>
> What is the recommended mechanism to override the value of
> PREFERRED_PROVIDE_virtual/kernel in my manufacturing-image.bb recipe?
>
> --wpd
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to specify a different kernel for an image

[Patrick Doyle]

Hello All,
I have a situation where I need to build an image for my machine with
a different kernel than is specified by
PREFERRED_PROVIDER_virtual/kernel.  But I also need to build the
default kernel.  This is for a "manufacturing" image which will
include the full production image, and then some (and, possibly,
without some).  The kernel configuration needs to be different for the
manufacturing image.

What is the recommended mechanism to override the value of
PREFERRED_PROVIDE_virtual/kernel in my manufacturing-image.bb recipe?

--wpd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Minutes: Yocto Project Monthly Meeting 7/16/2019

[Reyna, David]

Yocto Project Monthly Meeting
MINUTES: 7/16/2019

Attendees: Richard, Armin, JoshuaW, Bruce, Michael,  Frederic, Tim, Vineela, 
David, Trevor

RP:
  * Status update will go out later today: 
https://lists.yoctoproject.org/pipermail/yocto/2019-July/046042.html
  * Richard will not be at ELC San Diego (limited conference budget)

Tim: Python 3.4 is on Debian 8, wants to move YP to Python 3.5 as minimum

Armin: Will we move to Kernel 5.2? Bruce: we will follow the published YP 
policy on kernel updates.  LTS release timing has been close and/or after YP 
release dates so will probably miss again this year. The version is usually 
picked after Linux Plumbers.

Armin: LSB versus LTS? Richard: there are two tests, (a) Poky LSB and (b) 
Kernel X.Y, and we propose to drop the Poky LSB test.

Bruce: Kernel 5.3 will not be ready for our release, so probably 5.2 will be 
the number.

Richard: considering to number YP release as 3.0 instead of 2.8, because of 
many changes (especially runqueue). Tim noted also the major transition to 
Python 3, and Michael noted we did a similar jump for YP-2.0. Question: will 
there be a functional change with this numbering transition? Richard: no.

Richard: question to Joshua about hash state equivalency? Runqueue could 
support it. Joshua: currently there are issues in the persistent state. 
Richard: would like this feature for 3.0, and are there any implications? 
Joshua: cannot complete this and reproducibility by himself. Richard: might 
help with this effort since these changes can “put us on the map”.

Trevor: will move to hash equivalency reduce runqueue time? Richard: potential 
gains. Even local set can receive a huge speed gain, for example a 
non-impacting change to “core-native” would no longer trigger unneeded global 
rebuilding.

Trevor: LSB removal. LTP like LSB? Richard: LTP supported, LSB dead.

Michael: Mailing list transition still in progress. Lists will become 
“list.project.org”.

Joshua: Zoom links for this meeting are wrong. Michael: there are several links 
for this time slot for the two overlapping meetings. Will try to consolidate on 
the more popular link (or may cancel both and create a new one). Will also need 
to update Google Calendar.

- David


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-mingw][PATCH] bzip2: Remove bbappend

[Joshua Watt]

The patch being applied by meta-mingw has been upstreamed as of 1.0.8,
so there is no need to have a bbappend anymore.

Signed-off-by: Joshua Watt 
---
 .../0001-Fix-include-path-separator.patch | 33 ---
 recipes-extended/bzip2/bzip2_1.0.7.bbappend   |  4 ---
 2 files changed, 37 deletions(-)
 delete mode 100644 
recipes-extended/bzip2/bzip2/0001-Fix-include-path-separator.patch
 delete mode 100644 recipes-extended/bzip2/bzip2_1.0.7.bbappend

diff --git a/recipes-extended/bzip2/bzip2/0001-Fix-include-path-separator.patch 
b/recipes-extended/bzip2/bzip2/0001-Fix-include-path-separator.patch
deleted file mode 100644
index 4c43b7a..000
--- a/recipes-extended/bzip2/bzip2/0001-Fix-include-path-separator.patch
+++ /dev/null
@@ -1,33 +0,0 @@
-From 84c8769b52c63cce8a8a413e5fcbad1a65681d46 Mon Sep 17 00:00:00 2001
-From: Joshua Watt 
-Date: Tue, 2 Jul 2019 13:06:30 -0500
-Subject: [PATCH] Fix include path separator
-
-Changes the include path separator for Windows builds to use "/" instead
-of "\". Windows has no problems with using a forward slash as a path
-separator, but using a backslash causes problems when attempting to
-cross compile for other platforms (for example, when trying to cross
-compile for MinGW from Linux).
-
-Signed-off-by: Joshua Watt 
-Upstream-Status: Submitted 
[https://sourceware.org/ml/bzip2-devel/2019-q3/msg4.html]

- bzip2.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/bzip2.c b/bzip2.c
-index e362c65..be3b3be 100644
 a/bzip2.c
-+++ b/bzip2.c
-@@ -128,7 +128,7 @@
- #if BZ_LCCWIN32
- #   include 
- #   include 
--#   include 
-+#   include 
- 
- #   define NORETURN   /**/
- #   define PATH_SEP   '\\'
--- 
-2.21.0
-
diff --git a/recipes-extended/bzip2/bzip2_1.0.7.bbappend 
b/recipes-extended/bzip2/bzip2_1.0.7.bbappend
deleted file mode 100644
index 3cc4b01..000
--- a/recipes-extended/bzip2/bzip2_1.0.7.bbappend
+++ /dev/null
@@ -1,4 +0,0 @@
-
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-SRC_URI_append_mingw32 = " file://0001-Fix-include-path-separator.patch"
-- 
2.21.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wpewebkit, cog and libgles2

[Andy Pont]

I wrote...

The conf/distro/poky-atmel.conf file in meta-atmel contains the 
following line:


DISTRO_FEATURES_remove ?= "opengl wayland x11 3g nfc pulseaudio”

Switching back to the regular DISTRO = “poky” seems to have got it 
building again.
Switching back to poky caused a whole host of other issues.  I have 
managed to create a configuration that fully builds cog and wpewebkit 
using poky-atmel with wpebackend-rdk, wayland and core-image-weston.


When I boot the board a desktop appears with an icon that opens a 
Wayland terminal.   I’m trying to find some information on how to 
replace that so that it starts Cog automatically at boot up but not 
finding anything helpful.  I know that Cog itself works as I can start 
it up using the debug terminal.


-Andy.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] RFC: dropping official support for Debian 8 / Opensuse 42.3

[Adrian Bunk]

On Thu, Jul 18, 2019 at 12:43:50PM +0100, Richard Purdie wrote:
> On Thu, 2019-07-18 at 12:31 +0100, Burton, Ross wrote:
> > > CentOS 7 is based on Fedora 19 from 2013.
> > > 
> > > This is the oldest currently supported distribution, and when to
> > > remove
> > > support for it (replacing it with the not yet existing CentOS 8)
> > > should
> > > IMHO be part of this discussion.
> > 
> > Centos 7 support is, I believe, already patchy - I think we mandate
> > the buildtools for that?  Any idea what the support plan for Centos 7
> > will be once 8 is released, whenever that is?
> 
> There is some kind of official feed to add python 3.6 to it which we
> use.

Python is only a small part of the picture.

What I would be interested in would be to get rid of the 
ever-growing number of hacks and patches for supporting
the ancient gcc 4.8 in CentOS 7.

With support for Debian 8 removed, CentOS 7 will be two gcc major
versions behind all other supported host distributions.

Remember the nettle problems immediately before Yocto 2.7 was released, 
the root cause was a (bogus) workaround for supporting hosts with gcc < 5.

> Cheers,
> 
> Richard

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Missing service file

[JH]

Thanks Maciej,

On 7/18/19, Maciej Pijanowski  wrote:
>
> On 18.07.2019 12:01, JH wrote:
>> Hi,
>>
>> I set up a service file at following myapp.bb file, but that service
>> file was not installed to /lib/systemd/system. What could I be wrong
>> here?
> Not installed means it's not in the final image on the target? Which
> package gets installed into the
> image? I guess the ${PN} package.

It is in the package build:
sysroot-destdir/lib/systemd/system/myapp.service
package/lib/systemd/system/myapp.service
image/lib/systemd/system/myapp.service

> Have you inspected the recipe
> work/YOUR_TARGET/RECIPE_NAME/RECIPE_VERSION/image dir?
> Maybe it is present there, but not in the package you are installing
> (check the coThanks Maciej,ntent of the pacakges-split dir as well).

All installed files are in pacakges-split dir except that service file.

> You may use the:
>
> FILES_${PN} += "/lib/systemd/system/${PN}.service
>
> to force packaging the file into the ${PN} package.

Hmm, that caused an error unparsed line

Thank you.

- jh
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] RFC: dropping official support for Debian 8 / Opensuse 42.3

[Richard Purdie]

On Thu, 2019-07-18 at 12:31 +0100, Burton, Ross wrote:
> > CentOS 7 is based on Fedora 19 from 2013.
> > 
> > This is the oldest currently supported distribution, and when to
> > remove
> > support for it (replacing it with the not yet existing CentOS 8)
> > should
> > IMHO be part of this discussion.
> 
> Centos 7 support is, I believe, already patchy - I think we mandate
> the buildtools for that?  Any idea what the support plan for Centos 7
> will be once 8 is released, whenever that is?

There is some kind of official feed to add python 3.6 to it which we
use.

Cheers,

Richard

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] meta-mono updates

[Alexander Kanavin]

I don’t really know what’s the situation with meta-mono specifically, but if 
you’re willing to be the maintainer, that’d be great. Do keep in mind that 
yocto is almost entirely a volunteer project, contributors and maintainers come 
and go without long term promises.

Alex

> On 18 Jul 2019, at 9.49, MUGRIDGE Robin  wrote:
> 
> Hi,
>  
> I notice that meta-mono has not been updated for a while now (2018-11-06 for 
> the repo at git.yoctoproject.org, 2019-03-22 for the repo at 
> github.com/DynamicDevices).
>  
> Is this layer no longer being maintained?  Is there an alternative?
>  
> Thanks,
>  
> Robin
>  
> ___
> This e-mail is confidential and is for the addressee only.   Please refer to 
> www.oxinst.com/email-statement for regulatory information.
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] RFC: dropping official support for Debian 8 / Opensuse 42.3

[Burton, Ross]

On Thu, 18 Jul 2019 at 07:04, Adrian Bunk  wrote:
> > Now that both Debian 8 and OpenSuse 42.3 are end-of-life and no longer
> > formally supported, we think it's time to drop them from the supported
> > distribution list.
>
> Debian 8 is still LTS-supported for a year, unless there is urgency to
> drop support for it the right time for dropping would be after 2.8
> (2.9 release and Debian 8 LTS EOL will both be in Q2 2020).

I'm inclined to dropping 8 and just supporting 9 and 10.  We don't
*need* to exercise every distro.

> Should OpenSuse be dropped, or just the version upgraded to 15.1?

42.3 dropped.  15.1 should be it's replacement, yes.  This is already
being exercised on the autobuilder.

> Fedora 28 is also unsupported (but will be the basis of CentOS 8).

Good point, and we also don't have Fedora 30 in the list.  Again, this
is already being exercised on the autobuilder.

> CentOS 7 is based on Fedora 19 from 2013.
>
> This is the oldest currently supported distribution, and when to remove
> support for it (replacing it with the not yet existing CentOS 8) should
> IMHO be part of this discussion.

Centos 7 support is, I believe, already patchy - I think we mandate
the buildtools for that?  Any idea what the support plan for Centos 7
will be once 8 is released, whenever that is?

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Missing service file

[Maciej Pijanowski]

On 18.07.2019 12:01, JH wrote:
> Hi,
>
> I set up a service file at following myapp.bb file, but that service
> file was not installed to /lib/systemd/system. What could I be wrong
> here?
Not installed means it's not in the final image on the target? Which
package gets installed into the
image? I guess the ${PN} package.

Have you inspected the recipe
work/YOUR_TARGET/RECIPE_NAME/RECIPE_VERSION/image dir?
Maybe it is present there, but not in the package you are installing
(check the content of the pacakges-split dir as well).

You may use the:

FILES_${PN} += "/lib/systemd/system/${PN}.service

to force packaging the file into the ${PN} package.
>
>
> SYSTEMD_SERVICE_${PN} = "${PN}.service"
> SYSTEMD_AUTO_ENABLE_${PN} = "enable"
>
> do_install() {
> ..
> install -m 0644 ${S}/lib/systemd/system/${PN}.service
> ${D}/${systemd_system_unitdir}
> }
>
> Thank you.
>
> Kind regards,
>
> - jh

-- 
Maciej Pijanowski
Embedded Systems Engineer
https://3mdeb.com | @3mdeb_com




signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Missing service file

[JH]

Hi,

I set up a service file at following myapp.bb file, but that service
file was not installed to /lib/systemd/system. What could I be wrong
here?


SYSTEMD_SERVICE_${PN} = "${PN}.service"
SYSTEMD_AUTO_ENABLE_${PN} = "enable"

do_install() {
..
install -m 0644 ${S}/lib/systemd/system/${PN}.service
${D}/${systemd_system_unitdir}
}

Thank you.

Kind regards,

- jh
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Atmel device tree overlays

[Andy Pont]

Hello,

The meta-atmel layer includes a BSP recipe called dt-overlay-at91[1] 
that pulls in a number of .dtso files for various peripheral devices 
that can be connected to their reference boards.


I can’t figure out how to get the overlays into the FIT image that my 
board is booting from.  For the time being, if I have to include all of 
them then so be it but ideally I would like to be able to define which 
get used.


-Andy.

[1] https://layers.openembedded.org/layerindex/recipe/88706/

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-dpdk][PATCH] dpdk: Fix exmples and test _FORTIFY_SOURCE build failure

[He Zhe]

Kindly ping.

Zhe

On 7/10/19 4:45 PM, zhe...@windriver.com wrote:
> From: He Zhe 
>
> When building examples and tests with GCC9, the following errors come up,
>
>  error: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) 
> [-Werror=cpp]
>   382 | #  warning _FORTIFY_SOURCE requires compiling with optimization (-O)
>   |^~~
> cc1: all warnings being treated as errors
>
> dpdk itself already appends -O3 the EXTRA_CFLAGS for some of those cases, but
> dpdk.inc overwrites EXTRA_CFLAGS when evoking make. This patches adds it back.
>
> Signed-off-by: He Zhe 
> ---
>  recipes-extended/dpdk/dpdk.inc | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-extended/dpdk/dpdk.inc b/recipes-extended/dpdk/dpdk.inc
> index a0e081a..9dcec76 100644
> --- a/recipes-extended/dpdk/dpdk.inc
> +++ b/recipes-extended/dpdk/dpdk.inc
> @@ -106,12 +106,12 @@ do_compile () {
>  
>   cd ${S}/examples/
>   oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR} --hash-style=gnu 
> -fuse-ld=bfd" \
> -EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} 
> -I${STAGING_INCDIR}" \
> +EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} -O3 
> -I${STAGING_INCDIR}" \
>  CROSS="${TARGET_PREFIX}" O="${S}/examples/$@/"
>  
>   cd ${S}/test/
>   oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR} --hash-style=gnu 
> -fuse-ld=bfd" \
> -EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} 
> -I${STAGING_INCDIR}" \
> +EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} -O3 
> -I${STAGING_INCDIR}" \
>  CROSS="${TARGET_PREFIX}" O="${S}/test/$@/"
>  }
>  

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] List of Supported Python versions

[Maciej Pijanowski]

On 18.07.2019 09:34, jaymin.da...@vivaldi.net wrote:
> Hi Maciej,
>
> Thanks for the link.
> If I want to use different(updated) version of a particular function,
> e.g. Python, Is is possible?
> As per link Jethro is supporting Python version 2.7.9. I want to
> integrate Python version 2.7.16 and Python3 3.7.
> So, Do I need to use another branch which is supporting these versions
> or Is there any way to integrate these versions without changing
> current(Jethro) branch?
>
> In my case, I have limitation. Can't change to any other branch.
> I want to integrate Python3-Numpy, Python3-OpenCV, Python-Scipy and
> Python3-scipy modules in the build.
> Python3-Scipy is dependent on Python3-Numpy and Python3-Numpy is
> dependent on OpenBLAS, ATLAS and few other libraries. While these
> libraries are dependent on FORTRAN (libgfortran) compiler. Now, in my
> current (Jethro) branch, when I am trying to build libgfortran, it
> requires GCC version >=5. And, facing so many errors while building
> GCC 5.2 in the Yocto build. While GCC 5.2.0 is already supported in
> the Jethro.
Do you mind sharing the reason being tied to this old branch?
You could try to port newer recipes from more recent branches to the
Jehtro. But I believe
this may be more tedious and more time consuming than resolving the original
isssue of yours (upgrading from Jethro to more recent branch).
>
> In simple,
> How can I integrate Python3-Numpy, Python-Scipy, Python3-Scipy and
> Python3-OpenCV packages without changing the branch?
> What is the simplest way to integrate above packages?
>
> Please suggest.
>
> Regards,
> Jaymin
>
> On 18-07-2019 12:24 PM, Maciej Pijanowski wrote:
>> The link to the search engine:
>> https://layers.openembedded.org/layerindex/branch/master/recipes/
>>
>> On 18.07.2019 07:41, jaymin.da...@vivaldi.net wrote:
>>> Hello Team,
>>>
>>> Which Python, Python-OpenCV, Python-Numpy, Python-Scipy and OpenCV
>>> (max)versions are supported in Yocto 2.0.3 (Jethro) distro version?
>>>
>>> Can I get list of notes in which version of all supported modules have
>>> been mentioned?
>>>
>>>
>>> Please let me know.
>>>
>>> Regards,
>>> Jaymin
>>
>> -- 
>> Maciej Pijanowski
>> Embedded Systems Engineer
>> https://3mdeb.com | @3mdeb_com
>>
>>
>>
>> -- 
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto

-- 
Maciej Pijanowski
Embedded Systems Engineer
https://3mdeb.com | @3mdeb_com




signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] List of Supported Python versions

[jaymin . dabhi]

Hi Maciej,

Thanks for the link.
If I want to use different(updated) version of a particular function, 
e.g. Python, Is is possible?
As per link Jethro is supporting Python version 2.7.9. I want to 
integrate Python version 2.7.16 and Python3 3.7.
So, Do I need to use another branch which is supporting these versions 
or Is there any way to integrate these versions without changing 
current(Jethro) branch?


In my case, I have limitation. Can't change to any other branch.
I want to integrate Python3-Numpy, Python3-OpenCV, Python-Scipy and 
Python3-scipy modules in the build.
Python3-Scipy is dependent on Python3-Numpy and Python3-Numpy is 
dependent on OpenBLAS, ATLAS and few other libraries. While these 
libraries are dependent on FORTRAN (libgfortran) compiler. Now, in my 
current (Jethro) branch, when I am trying to build libgfortran, it 
requires GCC version >=5. And, facing so many errors while building GCC 
5.2 in the Yocto build. While GCC 5.2.0 is already supported in the 
Jethro.


In simple,
How can I integrate Python3-Numpy, Python-Scipy, Python3-Scipy and 
Python3-OpenCV packages without changing the branch?

What is the simplest way to integrate above packages?

Please suggest.

Regards,
Jaymin

On 18-07-2019 12:24 PM, Maciej Pijanowski wrote:

The link to the search engine:
https://layers.openembedded.org/layerindex/branch/master/recipes/

On 18.07.2019 07:41, jaymin.da...@vivaldi.net wrote:

Hello Team,

Which Python, Python-OpenCV, Python-Numpy, Python-Scipy and OpenCV
(max)versions are supported in Yocto 2.0.3 (Jethro) distro version?

Can I get list of notes in which version of all supported modules have
been mentioned?


Please let me know.

Regards,
Jaymin


--
Maciej Pijanowski
Embedded Systems Engineer
https://3mdeb.com | @3mdeb_com



--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] List of Supported Python versions

[Maciej Pijanowski]

On 18.07.2019 07:41, jaymin.da...@vivaldi.net wrote:
> Hello Team,
Hello,
>
> Which Python, Python-OpenCV, Python-Numpy, Python-Scipy and OpenCV
> (max)versions are supported in Yocto 2.0.3 (Jethro) distro version?
>
> Can I get list of notes in which version of all supported modules have
> been mentioned?
You can use the search engine to look for the packages you are
interested in.
I would recommend to use one of the more recent releases instead of the
Jethro, which is almost
4 years old.
>
>
> Please let me know.
>
> Regards,
> Jaymin

-- 
Maciej Pijanowski
Embedded Systems Engineer
https://3mdeb.com | @3mdeb_com




signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] meta-mono updates

[MUGRIDGE Robin]

Hi,

I notice that meta-mono has not been updated for a while now (2018-11-06 for 
the repo at git.yoctoproject.org, 2019-03-22 for the repo at 
github.com/DynamicDevices).

Is this layer no longer being maintained?  Is there an alternative?

Thanks,

Robin

___
This e-mail is confidential and is for the addressee only.   Please refer to
www.oxinst.com/email-statement for 
regulatory information.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] List of Supported Python versions

[Maciej Pijanowski]

The link to the search engine:
https://layers.openembedded.org/layerindex/branch/master/recipes/

On 18.07.2019 07:41, jaymin.da...@vivaldi.net wrote:
> Hello Team,
>
> Which Python, Python-OpenCV, Python-Numpy, Python-Scipy and OpenCV
> (max)versions are supported in Yocto 2.0.3 (Jethro) distro version?
>
> Can I get list of notes in which version of all supported modules have
> been mentioned?
>
>
> Please let me know.
>
> Regards,
> Jaymin

-- 
Maciej Pijanowski
Embedded Systems Engineer
https://3mdeb.com | @3mdeb_com




signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto