[OE-core] [PATCH] python-pycurl: create python3-pycurl recipe

The python-pycurl recipe can be used with python2 only even though python3 is officially supported by upstream. Create python3-pycurl recipe enabling the pycurl module for python3. Signed-off-by: Dmitry Rozhkov --- meta/recipes-devtools/python/python-pycurl.inc

Re: [OE-core] [PATCH V2] kernel.bbclass: move in addtask kernel_link_images statement from linux-yocto.inc

On Thu, Mar 30, 2017 at 3:20 PM, wrote: > From: Ming Liu > > Add kernel_link_images task in kernel.bbclass instead of adding it in > linux-yocto.inc, or else the recipes inheriting kernel.bbclass might > run into implicit dependency

Re: [OE-core] [PATCH v2 4/8] logrotate: replace fedorahosted.org SRC_URI with github.com source

Thanks for the review. We will upstream the V3 patch once amended. Thanks and Regards Choong YinThong -Original Message- From: Alexander Kanavin [mailto:alexander.kana...@linux.intel.com] Sent: Tuesday, April 4, 2017 6:40 PM To: openembedded-core@lists.openembedded.org; Choong, Yin

Re: [OE-core] [PATCH v2] logrotate: Add systemd support

On 04/05/2017 10:58 AM, Romain Perier wrote: ping Is this available in newer upstream versions of logrotate? Should you send it there first? Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org

[OE-core] [meta-freescale]: 32be_rootfs boot from sdcard

32be_rootfs boot from sdcard (ls1046) I tried to put kernel and rootfs in SD card , and boot it follow the SDK note(ls1046), it was fail to mount the rootfs(while 64be kernel is good),and here is part of log: mmcblk0: mmc0:0007 SL32G 29.0 GiB mcblk0: p1 VFS: Mounted root (ext2 filesystem)

Re: [OE-core] [PATCH] openssl: Fix symlink creation

On 23 January 2017 at 15:59, David Vincent wrote: > Symlinking the openssl configuration file at install time results in > errors when overriding it using an external package which also provides > openssl-conf. This should be done as a postinstall task for such > packages.

Re: [OE-core] [PATCH v2] logrotate: Add systemd support

ping Le 24/03/2017 à 09:46, Romain Perier a écrit : > Currently, this recipe only supports daily scheduling via a cron job. > This commit adds support for systemd, including systemd service and > systemd timer. When the corresponding distro feature is enabled the > systemd variant will be used.

Re: [OE-core] time to get rid of FILESDIR?

On Tue, 2017-04-04 at 18:11 -0400, Robert P. J. Day wrote: >   the only references i see to the deprecated FILESDIR are > historical, > none actually being used. what about just tossing it? That has always been the intent, thanks for the reminder. Patches sent to do just that. Cheers, Richard

[OE-core] [PATCH] recipe_sanity: Drop now unused FILESDIR

FILESDIR is long dead and unreferenced pretty much anywhere now, drop these sanity references too. Signed-off-by: Richard Purdie --- meta/classes/recipe_sanity.bbclass | 17 - 1 file changed, 17 deletions(-) diff --git

Re: [OE-core] [meta-freescale]: 32be_rootfs boot from sdcard

32be_rootfs boot from sdcard (ls1046) I used source code provided by nxp QorIQ-Linux-SDK-v2.0-SOURCE.iso + SDK-V2.0-1701 to build the kernel and rootfs , then it can’t boot from sdcard. I tried to put kernel(32be) and rootfs(32be) in SD card , and boot it follow the SDK2.0, it was fail to

Re: [OE-core] [PATCH v2] logrotate: Add systemd support

Hello, Le 05/04/2017 à 10:25, Alexander Kanavin a écrit : > On 04/05/2017 10:58 AM, Romain Perier wrote: >> ping >> > > Is this available in newer upstream versions of logrotate? Should you > send it there first? > > Alex > No, not yet. Mhhh, we have variables specific to the recipe in the

Re: [OE-core] tainting other recipe's specific task

On 04-04-17 15:54, André Draszik wrote: Hi, Is it possible to invalidate one recipe's hash for a specific task from another recipe? I hope not... More specifically, I have an initramfs image recipe and a main image recipe where do_rootfs of the main image [depends] on do_deploy of

Re: [OE-core] [PATCH v2] logrotate: Add systemd support

Add yocto and Alexander to Cc: (sorry) Romain Le 05/04/2017 à 11:30, Romain Perier a écrit : > Hello, > > > Le 05/04/2017 à 10:25, Alexander Kanavin a écrit : >> On 04/05/2017 10:58 AM, Romain Perier wrote: >>> ping >>> >> Is this available in newer upstream versions of logrotate? Should you >>

Re: [OE-core] [PATCH 1/1] image.inc/qemu.inc: preserve directories to be used by runqemu

On 30 March 2017 at 15:12, Chen Qi wrote: > The 'recipe-sysroot' and 'recipe-sysroot-native' directories need to > be preserved for runqemu to work correctly. Otherwise, when 'rm_work' > is enabled, these directories are removed, thus causing errors when > using runqemu . >

Re: [OE-core] [PATCH] create-pull-request: add "-t in-reply-to" option

On Tue, 2017-04-04 at 16:45 -0500, Jose Lamego wrote: > The create-patch-request script creates patches as replies to a cover you mean create-pull-request, I believe > letter, in the form of an email thread. If further revisions are sent to > the mailing list without referencing to the first

[OE-core] [PATCH] busybox: Security Fix CVE-2016-6301

Signed-off-by: Andrej Valek Signed-off-by: Pascal Bach --- .../busybox/busybox/CVE-2016-6301.patch| 37 ++ meta/recipes-core/busybox/busybox_1.24.1.bb| 1 + 2 files changed, 38 insertions(+) create mode

Re: [OE-core] [PATCH] qemu arm/x86: drop linux-yocto preferred version

On Wed, 2017-04-05 at 08:39 -0400, Bruce Ashfield wrote: > We don't make a linux-yocto version available unless it boots > on all qemu targets, hence there is no reason to specify a > specific version .. the latest is always fine. > > Also, the other qemu machines don't have this specification,

[OE-core] ✗ patchtest: failure for busybox: Security Fix CVE-2016-6301

== Series Details == Series: busybox: Security Fix CVE-2016-6301 Revision: 1 URL : https://patchwork.openembedded.org/series/6173/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on

Re: [OE-core] [PATCHv2 3/3] base-files: profile: Simplify setting variables conditionally

On Wed, 2017-04-05 at 15:46 +0200, Peter Kjellerstedt wrote: > It is preferred to use `[ ] || ...` instead of > `[ ] && ...` as the latter leaves $? set to 1. Your patch and the description above don't match. There are changes here which aren't  and are stylistic changes instead afaict. We're

Re: [OE-core] ✗ patchtest: failure for python3: fix run-time deps for core python3 libraries

On Wed, 2017-04-05 at 13:02 +, Patchwork wrote: > == Series Details == > > Series: python3: fix run-time deps for core python3 libraries > Revision: 1 > URL : https://patchwork.openembedded.org/series/6164/ > State : failure > > == Summary == > > > Thank you for submitting this patch

[OE-core] [PATCH 3/3] yocto-compat-layer: include bitbake-diffsigs output

After filtering out potential false positives, it becomes feasible to include the output of bitbake-diffsigs for those tasks which definitely have a change. Depends on bitbake-diffsigs with the "--signature" parameter. Enhanced output now is: AssertionError: False is not true : Layer

[OE-core] [PATCH 2/3] yocto-compat-layer: limit report of signature changes

Typically a single change cascades through the entire task dependency chain. Developers had to figure that out themselves, based on hard to read and interpret output (not sorted, no indention, no explanations): $ yocto-compat-layer.py -n meta- ... AssertionError: True is not false :

[OE-core] [PATCH 1/3] yocto-compat-layer: fix also other command invocations

In commit 5b9ac62ab535d, one place was fixed where a command was invoked such that failures caused double stack traces and stderr was lost. The same problem also occurs elsewhere, triggered for example by a layer with parsing problems. Now a new utility method is used instead of repeating the

[OE-core] [PATCH 0/3] yocto-compat-layer: various enhancements + bitbake-diffsigs support

I started applying yocto-compat-layer to some real BSP layers and ran into some usability issues with the tool. I also didn't want to do the root cause analysis manually, so I automated the dependency analysis and the running of bitbake-diffsigs. This patch series is based on Mark's

Re: [OE-core] Fwd: Recipe [patch] modification to generate a static library instead of shared library

On Wed, Apr 5, 2017 at 10:18 AM, Ravi chandra reddy wrote: > Hi All, > I am using meta-oe to generate libxml2 library using AARCH64 > compiler. However it generates shared object [.so] library. > > is there any setting in recipe to modify this, to generate static

[OE-core] [PATCHv2 1/3] base-files: profile: Whitespace clean up

Signed-off-by: Peter Kjellerstedt --- meta/recipes-core/base-files/base-files/profile | 29 + 1 file changed, 15 insertions(+), 14 deletions(-) diff --git a/meta/recipes-core/base-files/base-files/profile

[OE-core] [PATCH 1/2] logrotate: Bump to 3.11.0

This commit updates the recipe to the last upstream tag. Then, as the tarball no longer contains the pre-generated Makefile, inherit from autotools Signed-off-by: Romain Perier --- .../{logrotate_3.9.1.bb => logrotate_3.11.0.bb}| 23 +++--- 1

[OE-core] [PATCH 0/2] logrotate: systemd support

SystemD is now supported by upstream logrotate. This set of patches first bumps the recipe to the last upstream version, that is 3.11.0. Then it adds support for systemd. This series is the continuety of the following patch: 1.

[OE-core] [PATCH 2/2] logrotate: Add systemd support

Currently, this recipe only supports daily scheduling via a cron job. This commit adds support for systemd in the recipe, as the feature is already supported on upstream. When the corresponding distro feature is enabled the systemd variant will be used. The timer granularity and its accuracy are

Re: [OE-core] [meta-freescale]: 32be_rootfs boot from sdcard

wrong list, you may have better luck at the meta-fsl mailing list. BTW, the kernel expects a filesystem on a partition and the latter must be defined in the kernel command line, using the root parameter. On Wed, 2017-04-05 at 09:25 +, Zheng, Ruoqin wrote: > 32be_rootfs boot from sdcard

[OE-core] Fwd: Recipe [patch] modification to generate a static library instead of shared library

Hi All, I am using meta-oe to generate libxml2 library using AARCH64 compiler. However it generates shared object [.so] library. is there any setting in recipe to modify this, to generate static library [instead of shared library] if so, please point me to the recipe/file to change.

Re: [OE-core] [PATCH 3/3] yocto-compat-layer: include bitbake-diffsigs output

On Wed, 2017-04-05 at 15:36 +0200, Patrick Ohly wrote: > After filtering out potential false positives, it becomes feasible to > include the output of bitbake-diffsigs for those tasks which > definitely have a change. > > Depends on bitbake-diffsigs with the "--signature" parameter. > > Enhanced

Re: [OE-core] [PATCH 1/1] image.inc/qemu.inc: preserve directories to be used by runqemu

On 5 April 2017 at 21:22, Richard Purdie wrote: > On Wed, 2017-04-05 at 20:06 +1000, Nathan Rossi wrote: >> On 30 March 2017 at 15:12, Chen Qi wrote: >> > >> > The 'recipe-sysroot' and 'recipe-sysroot-native' directories need >> > to >>

Re: [OE-core] ✗ patchtest: failure for python3: fix run-time deps for core python3 libraries (rev2)

On Thu, 2017-04-06 at 05:32 +, Patchwork wrote: > == Series Details == > > Series: python3: fix run-time deps for core python3 libraries (rev2) > Revision: 2 > URL   : https://patchwork.openembedded.org/series/6164/ > State : failure > > == Summary == > > > Thank you for submitting this

[OE-core] [PATCH v2] python3: fix run-time deps for core python3 libraries

The http.server module from python3-netclient imports the html module which is in python3-html. Also xmlrpc.server imports pydoc which is a part of python3-pydoc. But those run-time dependencies are missing from python3-netclient and python3-xmlrpc respectively. Add the missing run-time

[OE-core] ✗ patchtest: failure for python3: fix run-time deps for core python3 libraries (rev2)

== Series Details == Series: python3: fix run-time deps for core python3 libraries (rev2) Revision: 2 URL : https://patchwork.openembedded.org/series/6164/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several

Re: [OE-core] Fwd: Recipe [patch] modification to generate a static library instead of shared library

On Wed, 2017-04-05 at 10:33 -0500, Matthew McClintock wrote: > On Wed, Apr 5, 2017 at 10:18 AM, Ravi chandra reddy com> wrote: > > > > Hi All, > >   I am using meta-oe to generate libxml2 library using > > AARCH64 > > compiler. However it generates shared object [.so]

[OE-core] [PATCH] package.bbclass: add CONFFILES to pkgdata

Emit CONFFILES variable in pkgdata, or else the get_conffiles function will return 'None' for some packages instead of the expected value. This is especially true for optional module packages. Signed-off-by: David Vincent --- meta/classes/package.bbclass | 1 + 1 file

Re: [OE-core] Fwd: Recipe [patch] modification to generate a static library instead of shared library

Do you have the staticdev packages in your TMPDIR? E.g. tmp/work/cortexa15t2hf-neon-rdk-linux-gnueabi/libxml2/2.9.4-r0/deploy-ipks/cortexa15t2hf-neon/libxml2-staticdev_2.9.4-r0_cortexa15t2hf-neon.ipk -M On Wed, Apr 5, 2017 at 1:09 PM, Ravi chandra reddy wrote: > Hi, >

[OE-core] [PATCH 1/1] package_ipk.bbclass: Replace empty lines in DESCRIPTION with '.'

From: Mariano Lopez opkg uses empty lines as separator for next package and if an ipk file was packaged with empty lines in DESCRIPTION opkg won't be able to handle such ipk file, this happens at execution time. This commit will replace empty lines in DESCRIPTION

Re: [OE-core] Fwd: Recipe [patch] modification to generate a static library instead of shared library

Hi, in local/local.conf it [bitbake core-image-minimal] fails, if i use libxml2-staticdev # Specify the 32-bit libraries to be added to all images IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc lib32-libstdc++ libedit libxml2-staticdev" == i get the

Re: [OE-core] [PATCH 3/3] yocto-compat-layer: include bitbake-diffsigs output

On Wed, 2017-04-05 at 10:26 -0500, Leonardo Sandoval wrote: > > diff --git a/scripts/lib/compatlayer/cases/common.py > > b/scripts/lib/compatlayer/cases/common.py > > index b91da9b..d909d5b 100644 > > --- a/scripts/lib/compatlayer/cases/common.py > > +++ b/scripts/lib/compatlayer/cases/common.py

Re: [OE-core] Fwd: Recipe [patch] modification to generate a static library instead of shared library

Hi, is this what you are talking about root@polar:~/zcu_yocto/poky/build/tmp/sysroots/zcu102-zynqmp/pkgdata/runtime# ls -ltr *libxml* -rwxrwxrwx 2 root root 0 Nov 21 14:05 libxml2-ptest.packaged -rwxrwxrwx 2 root root 463307 Nov 21 14:05 libxml2-ptest -rwxrwxrwx 2 root root933 Nov

Re: [OE-core] Fwd: Recipe [patch] modification to generate a static library instead of shared library

Hi, Let me thank you guys for quick reply. let me put my email in correct steps 1. below local/local.conf changes makes bitbake fail. IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc lib32-libstdc++ libedit libxml2-*staticdev*" error:=

[OE-core] [PATCH 0/1] package_ipk.bbclass: Replace empty lines in DESCRIPTION with '.'

From: Mariano Lopez This will deal with empty lines in DESCRIPTION while creating ipk packages. Changes in v2: - Firts version of this patch would fail do_package_write_ipk task if found an empty line in DESCRIPTION, this version will replace an empty line with

Re: [OE-core] [PATCH] create-pull-request: add "-t in-reply-to" option

On 04/05/2017 09:00 AM, Leonardo Sandoval wrote: > On Tue, 2017-04-04 at 16:45 -0500, Jose Lamego wrote: >> The create-patch-request script creates patches as replies to a cover > > you mean create-pull-request, I believe > >> letter, in the form of an email thread. If further revisions are

[OE-core] [yocto][patchwork][PATCH v2] create-pull-request: add "-t in-reply-to" option

The create-pull-request script creates patches as replies to a cover letter, in the form of an email thread. If further revisions are sent to the mailing list without referencing to the first revision, these new revisions are not identified at the mailing list as part of the original thread, but

[OE-core] [PATCH v2] create-pull-request: add "-t in-reply-to" option

The create-pull-request script creates patches as replies to a cover letter, in the form of an email thread. If further revisions are sent to the mailing list without referencing to the first revision, these new revisions are not identified at the mailing list as part of the original thread, but

[OE-core] [PATCH 1/2] wpa-supplicant: Use systemd-tmpfiles to create volatiles files and dirs

Volatiles files are installed in different locations depending on distro feature update-rc.d or systemd. For update-rc.d volatiles configuration files are installed in /etc/default/volatiles and for systemd in /etc/tmpfiles.d/. So, we need to install volatiles files in correct location depending

[OE-core] [PATCH] ghostscript: CVE-2017-7207

The mem_get_bits_rectangle function in Artifex Software, Inc. Ghostscript 9.20 allows remote attackers to cause a denial of service (NULL pointer dereference) via a crafted PostScript document. Reference: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-7207 Upstream patch:

[OE-core] [PATCH 2/2] openssh: Use systemd-tmpfiles to create volatiles files and dirs

Volatiles files are installed in different locations depending on distro feature update-rc.d or systemd. For update-rc.d volatiles configuration files are installed in /etc/default/volatiles and for systemd in /etc/tmpfiles.d/. So, we need to install volatiles files in correct location depending

[OE-core] [PATCH 2/3] oeqa/utils/targetbuild: tmp dir improvements

Don't hard-code /tmp as the tmpdir, instead use WORKDIR as the tmpdir if the instantiater doesn't specify a value. Signed-off-by: Joshua Lock --- meta/lib/oeqa/utils/targetbuild.py | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git

[OE-core] [PATCH 3/3] oeqa/runtime/utils/targetbuildproject: use parent classes defaults tmpdir

Rather than hard-coding the tmpdir for TargetBuildProject to /tmp allow the parent's default handling to define an appropriate tmpdir. Signed-off-by: Joshua Lock --- meta/lib/oeqa/runtime/utils/targetbuildproject.py | 3 +-- 1 file changed, 1 insertion(+), 2

[OE-core] [PATCH 1/3] oeqa/utils/buildproject: create a more unique tmp dir

Rather than hardcoding /tmp as the default tmpdir make a more unique tmpdir with tempfile.mkdtemp() when the caller doesn't specify a tmpdir value. Signed-off-by: Joshua Lock --- meta/lib/oeqa/utils/buildproject.py | 7 +-- 1 file changed, 5 insertions(+), 2

Re: [OE-core] [PATCH] x86-base.inc, qemuarm.conf: prefer 4.10 version of linux-yocto

On Tue, Apr 4, 2017 at 11:48 AM, Burton, Ross wrote: > > On 4 April 2017 at 09:02, Martin Jansa wrote: > >> -PREFERRED_VERSION_linux-yocto ??= "4.8%" >> +PREFERRED_VERSION_linux-yocto ??= "4.10%" >> > > The qemuppc and qemumips machines don't have

Re: [OE-core] [PATCH 1/1] image.inc/qemu.inc: preserve directories to be used by runqemu

On Wed, 2017-04-05 at 20:06 +1000, Nathan Rossi wrote: > On 30 March 2017 at 15:12, Chen Qi wrote: > > > > The 'recipe-sysroot' and 'recipe-sysroot-native' directories need > > to > > be preserved for runqemu to work correctly. Otherwise, when > > 'rm_work' > > is enabled,

Re: [OE-core] [PATCH] qemu arm/x86: drop linux-yocto preferred version

On Wed, Apr 5, 2017 at 3:21 PM, Richard Purdie wrote: > On Wed, 2017-04-05 at 08:39 -0400, Bruce Ashfield wrote: > > We don't make a linux-yocto version available unless it boots > > on all qemu targets, hence there is no reason to specify a > > specific

[OE-core] [PATCH] selftest/wic: skip wic unit tests in case NLS is disable

From: Leonardo Sandoval WIC test case requires wic-tools which in turn depends on intltool-native and gettext-native. However, if NLS is disable, the gettext-minimal-native is used instead of gettext-native causing a failure on intltool-native as seen

Re: [OE-core] [PATCH] qemu arm/x86: drop linux-yocto preferred version

On Thu, 2017-04-06 at 00:33 +0200, Bruce Ashfield wrote: > On Wed, Apr 5, 2017 at 3:21 PM, Richard Purdie > wrote: > >  > > > @@ -16,5 +16,4 @@ QB_MACHINE = "-machine versatilepb" > > >  QB_KERNEL_CMDLINE_APPEND = "console=ttyAMA0,115200 console=tty" > > >  #

Re: [OE-core] [PATCH] qemu arm/x86: drop linux-yocto preferred version

On Thu, Apr 6, 2017 at 12:41 AM, Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Thu, 2017-04-06 at 00:33 +0200, Bruce Ashfield wrote: > > On Wed, Apr 5, 2017 at 3:21 PM, Richard Purdie > > wrote: > > > > > > > @@ -16,5 +16,4 @@ QB_MACHINE =

[OE-core] [PATCH] license.bbclass: improve reproducibility

Two identical builds can end up having deploy/licenses folders that differ. This is observed in cases where there are several different license files of the same name in different folders, i.e. "COPYING". In those case we have to differentiate the files somehow and we do it via file expensions

[OE-core] [PATCH] busybox: Security fix BUG9071

Signed-off-by: Martin Balik Signed-off-by: Pascal Bach --- .../busybox/BUG9071_buffer_overflow_arp.patch | 53 ++ meta/recipes-core/busybox/busybox_1.24.1.bb| 1 + 2 files changed, 54 insertions(+) create mode

[OE-core] [PATCHv2 2/3] base-files: profile: Do not assume that the tty command exists

This avoids the following error when logging in to a host that does not have the tty command: -sh: tty: not found Reported-by: Cristian Ionescu-Idbohrn Signed-off-by: Peter Kjellerstedt ---

[OE-core] [PATCHv2 3/3] base-files: profile: Simplify setting variables conditionally

It is preferred to use `[ ] || ...` instead of `[ ] && ...` as the latter leaves $? set to 1. Signed-off-by: Peter Kjellerstedt --- meta/recipes-core/base-files/base-files/profile | 14 ++ 1 file changed, 6 insertions(+), 8 deletions(-) diff --git

[OE-core] [PATCH] python3: fix run-time deps for core python3 libraries

The http.server module from python3-netclient imports the html module which is in python3-html. Also xmlrpc.server imports pydoc which is a part of python3-pydoc. But those run-time dependencies are missing from python3-netclient and python3-xmlrpc respectively. Add the missing run-time

[OE-core] [PATCH] qemu arm/x86: drop linux-yocto preferred version

We don't make a linux-yocto version available unless it boots on all qemu targets, hence there is no reason to specify a specific version .. the latest is always fine. Also, the other qemu machines don't have this specification, so this makes x86 and ARM consistent. Signed-off-by: Bruce Ashfield

Re: [OE-core] [PATCH v2] logrotate: Add systemd support

I have just realized, systemd service and timer is already present and supported on upstream (like cron, in examples/). At least in 3.11.0 and master. I will propose an update of this recipe to 3.11.0 (the last release) and then add support for systemd. Regards, Romain Le 05/04/2017 à 11:41,

[OE-core] [PATCH morty] e2fsprogs: Fix wrong error code after optimization

fsck.ext will return an error code of 1 if a file systems was checked and successfully repaired. Even when an optimization was performed it will return this error code. This patch will change the error code to 0 if only optimizations had changed the file systems. The reason for this patch is a

[OE-core] ✗ patchtest: failure for python3: fix run-time deps for core python3 libraries

== Series Details == Series: python3: fix run-time deps for core python3 libraries Revision: 1 URL : https://patchwork.openembedded.org/series/6164/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests

[OE-core] Fwd: Adding Static Library Support to the SDK or Rootfs

Hello, I'm try to build static library for SDK. Update the *build*/local.conf file with the following information SDKIMAGE_FEATURES = "staticdev-pkgs dev-pkgs" *INHERIT += "buildhistory" BUILDHISTORY_COMMIT = "0" BUILDHISTORY_FEATURES = "sdk"* *But cannot create static library for SDK. *