[PATCH 0/8] [PATCH v2]meta-toolchain: Added dnf-nativesdk into cross-development toolchain.

[PATCH 0/8] [PATCH v2]meta-toolchain: Added dnf-nativesdk into cross-development toolchain.

[Zheng Ruoqin]

1. To make dnf work on cross-development environment.

2. To enable runtime dependencies for dnf-nativesdk.

Zheng Ruoqin (8):
  [OE-core][PATCH v2] slang: add nativesdk
  [OE-core][PATCH v2] libnewt: Add nativesdk
  [OE-core][PATCH v2] libnewt-python: Add nativesdk
  [OE-core][PATCH v2] libnewt-python: Add PROVIDES for nativesdk.
  [OE-core][PATCH v2] createrepo-c: Add nativesdk
  [OE-core][PATCH v2] update-rc.d: Add nativesdk
  [OE-core][PATCH v2] rpm: Add DEPENDS for nativesdk.
  [OE-core][PATCH v2] meta-toolchain: Added dnf-nativesdk into
    cross-development toolchain.

 meta/classes/toolchain-scripts.bbclass                             | 1 +
 meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb | 4 ++++
 meta/recipes-core/update-rc.d/update-rc.d_0.7.bb                   | 2 +-
 meta/recipes-devtools/createrepo-c/createrepo-c_git.bb             | 7 ++++++-
 meta/recipes-devtools/file/file_5.32.bb                            | 2 ++
 meta/recipes-devtools/rpm/rpm_4.14.1.bb                            | 1 +
 meta/recipes-extended/newt/libnewt-python_0.52.20.bb               | 2 +-
 meta/recipes-extended/newt/libnewt_0.52.20.bb                      | 2 +-
 meta/recipes-extended/slang/slang_2.3.2.bb                         | 2 +-
 9 files changed, 18 insertions(+), 5 deletions(-)

-- 
2.7.4

[PATCH 1/8][PATCH v2] slang: add nativesdk

[Zheng Ruoqin]

Add nativesdk for slang.

Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
---
 meta/recipes-extended/slang/slang_2.3.2.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-extended/slang/slang_2.3.2.bb b/meta/recipes-extended/slang/slang_2.3.2.bb
index 87fd41a..e53c432 100644
--- a/meta/recipes-extended/slang/slang_2.3.2.bb
+++ b/meta/recipes-extended/slang/slang_2.3.2.bb
@@ -78,4 +78,4 @@ FILES_${PN} += "${libdir}/${BPN}/v2/modules/ ${datadir}/slsh/"
 PARALLEL_MAKE = ""
 PARALLEL_MAKEINST = ""
 
-BBCLASSEXTEND = "native"
+BBCLASSEXTEND = "native nativesdk"
-- 
2.7.4

[PATCH 2/8][PATCH v2] libnewt: Add nativesdk

[Zheng Ruoqin]

Add nativesdk for libnewt.

Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
---
 meta/recipes-extended/newt/libnewt_0.52.20.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-extended/newt/libnewt_0.52.20.bb b/meta/recipes-extended/newt/libnewt_0.52.20.bb
index 65ce70c..264ef3b 100644
--- a/meta/recipes-extended/newt/libnewt_0.52.20.bb
+++ b/meta/recipes-extended/newt/libnewt_0.52.20.bb
@@ -51,4 +51,4 @@ do_compile_prepend() {
 
 FILES_whiptail = "${bindir}/whiptail"
 
-BBCLASSEXTEND = "native"
+BBCLASSEXTEND = "native nativesdk"
-- 
2.7.4

[PATCH 3/8][PATCH v2] libnewt-python: Add nativesdk

[Zheng Ruoqin]

Add nativesdk for libnewt-python.

Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
---
 meta/recipes-extended/newt/libnewt-python_0.52.20.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-extended/newt/libnewt-python_0.52.20.bb b/meta/recipes-extended/newt/libnewt-python_0.52.20.bb
index 20369ef..433d184 100644
--- a/meta/recipes-extended/newt/libnewt-python_0.52.20.bb
+++ b/meta/recipes-extended/newt/libnewt-python_0.52.20.bb
@@ -25,4 +25,4 @@ PACKAGES_remove = "whiptail"
 
 FILES_${PN} = "${PYTHON_SITEPACKAGES_DIR}/*"
 
-BBCLASSEXTEND = "native"
+BBCLASSEXTEND = "native nativesdk"
-- 
2.7.4

[PATCH 4/8][PATCH v2] libnewt-python: Add PROVIDES for nativesdk.

[Zheng Ruoqin]

Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
---
 meta/recipes-devtools/file/file_5.32.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-devtools/file/file_5.32.bb b/meta/recipes-devtools/file/file_5.32.bb
index 5e15925..9b13261 100644
--- a/meta/recipes-devtools/file/file_5.32.bb
+++ b/meta/recipes-devtools/file/file_5.32.bb
@@ -43,6 +43,8 @@ do_install_append_class-nativesdk() {
 
 BBCLASSEXTEND = "native nativesdk"
 PROVIDES_append_class-native = " file-replacement-native"
+PROVIDES_append_class-nativesdk = " file-replacement-nativesdk"
+
 # Don't use NATIVE_PACKAGE_PATH_SUFFIX as that hides libmagic from anyone who
 # depends on file-replacement-native.
 bindir_append_class-native = "/file-native"
-- 
2.7.4

Re: [PATCH 4/8][PATCH v2] libnewt-python: Add PROVIDES for nativesdk.

[Richard Purdie]

On Sun, 2018-06-24 at 03:52 +0800, Zheng Ruoqin wrote:
> Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
> ---
>  meta/recipes-devtools/file/file_5.32.bb | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/meta/recipes-devtools/file/file_5.32.bb b/meta/recipes-
> devtools/file/file_5.32.bb
> index 5e15925..9b13261 100644
> --- a/meta/recipes-devtools/file/file_5.32.bb
> +++ b/meta/recipes-devtools/file/file_5.32.bb
> @@ -43,6 +43,8 @@ do_install_append_class-nativesdk() {
>  
>  BBCLASSEXTEND = "native nativesdk"
>  PROVIDES_append_class-native = " file-replacement-native"
> +PROVIDES_append_class-nativesdk = " file-replacement-nativesdk"
> +
>  # Don't use NATIVE_PACKAGE_PATH_SUFFIX as that hides libmagic from
> anyone who
>  # depends on file-replacement-native.
>  bindir_append_class-native = "/file-native"

The description is wrong, this isn't libnewt-python.

Also, the use case for file-replacement-native is very specific to file
from the host system verses file from file-native. Why would you ever
need this for nativesdk? I'm not sure you'd ever need this?

Cheers,

Richard

[PATCH 5/8][PATCH v2] createrepo-c: Add nativesdk

[Zheng Ruoqin]

Add nativesdk for createrepo-c.

Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
---
 meta/recipes-devtools/createrepo-c/createrepo-c_git.bb | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb b/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb
index 3176136..9be9f9e 100644
--- a/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb
+++ b/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb
@@ -21,7 +21,7 @@ inherit cmake pkgconfig bash-completion distutils3-base
 
 EXTRA_OECMAKE = " -DPYTHON_INSTALL_DIR=${PYTHON_SITEPACKAGES_DIR} -DPYTHON_DESIRED=3"
 
-BBCLASSEXTEND = "native"
+BBCLASSEXTEND = "native nativesdk"
 
 # Direct createrepo to read rpm configuration from our sysroot, not the one it was compiled in
 do_install_append_class-native() {
@@ -29,3 +29,8 @@ do_install_append_class-native() {
                 RPM_CONFIGDIR=${STAGING_LIBDIR_NATIVE}/rpm
 }
 
+do_install_append_class-nativesdk() {
+        create_wrapper ${D}/${bindir}/createrepo_c \
+                RPM_CONFIGDIR=${SDKPATHNATIVE}${libdir_nativesdk}/rpm
+        rm -rf ${D}/etc
+}
-- 
2.7.4

[PATCH 6/8][PATCH v2] update-rc.d: Add nativesdk

[Zheng Ruoqin]

Add nativesdk for update-rc.d.

Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
---
 meta/recipes-core/update-rc.d/update-rc.d_0.7.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb b/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb
index 76d4312..d3d3e2f 100644
--- a/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb
+++ b/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb
@@ -30,4 +30,4 @@ do_install() {
 	install -m 0755 ${S}/update-rc.d ${D}${sbindir}/update-rc.d
 }
 
-BBCLASSEXTEND = "native"
+BBCLASSEXTEND = "native nativesdk"
-- 
2.7.4

Re: [PATCH 6/8][PATCH v2] update-rc.d: Add nativesdk

[Burton, Ross]

As update-rcd is for managing init scripts, and init scripts make no
sense in a nativesdk environment, it would probably be best if the
update-rc.d class only added these dependencies for target packages.

Ross

On 23 June 2018 at 20:52, Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com> wrote:
> Add nativesdk for update-rc.d.
>
> Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
> ---
>  meta/recipes-core/update-rc.d/update-rc.d_0.7.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb b/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb
> index 76d4312..d3d3e2f 100644
> --- a/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb
> +++ b/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb
> @@ -30,4 +30,4 @@ do_install() {
>         install -m 0755 ${S}/update-rc.d ${D}${sbindir}/update-rc.d
>  }
>
> -BBCLASSEXTEND = "native"
> +BBCLASSEXTEND = "native nativesdk"
> --
> 2.7.4
>
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [PATCH 6/8][PATCH v2] update-rc.d: Add nativesdk

[Richard Purdie]

On Mon, 2018-06-25 at 10:43 +0100, Burton, Ross wrote:
> As update-rcd is for managing init scripts, and init scripts make no
> sense in a nativesdk environment, it would probably be best if the
> update-rc.d class only added these dependencies for target packages.

I had the same thought initially. I think this is being used by
postinstall scripts in the target rootfs from the SDK. Whether that is
a good idea or not I'm torn on. I did make my view clear about
preferring eSDK for this kind of tooling, as otherwise you end up
reinventing the rootfs code.

Cheers,

Richard

[PATCH 7/8] [PATCH v2] rpm: Add DEPENDS for nativesdk.

[Zheng Ruoqin]

Add DEPENDS for nativesdk.

Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
---
 meta/recipes-devtools/rpm/rpm_4.14.1.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/rpm/rpm_4.14.1.bb b/meta/recipes-devtools/rpm/rpm_4.14.1.bb
index e5e87d3..6ca5c94 100644
--- a/meta/recipes-devtools/rpm/rpm_4.14.1.bb
+++ b/meta/recipes-devtools/rpm/rpm_4.14.1.bb
@@ -52,6 +52,7 @@ S = "${WORKDIR}/git"
 
 DEPENDS = "nss libarchive db file popt xz bzip2 dbus elfutils python3"
 DEPENDS_append_class-native = " file-replacement-native bzip2-replacement-native"
+DEPENDS_append_class-nativesdk = " file-replacement-nativesdk"
 
 inherit autotools gettext pkgconfig python3native
 export PYTHON_ABI
-- 
2.7.4

Re: [PATCH 7/8] [PATCH v2] rpm: Add DEPENDS for nativesdk.

[Richard Purdie]

On Sun, 2018-06-24 at 03:53 +0800, Zheng Ruoqin wrote:
> Add DEPENDS for nativesdk.
> 
> Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
> ---
>  meta/recipes-devtools/rpm/rpm_4.14.1.bb | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/recipes-devtools/rpm/rpm_4.14.1.bb b/meta/recipes-
> devtools/rpm/rpm_4.14.1.bb
> index e5e87d3..6ca5c94 100644
> --- a/meta/recipes-devtools/rpm/rpm_4.14.1.bb
> +++ b/meta/recipes-devtools/rpm/rpm_4.14.1.bb
> @@ -52,6 +52,7 @@ S = "${WORKDIR}/git"
>  
>  DEPENDS = "nss libarchive db file popt xz bzip2 dbus elfutils
> python3"
>  DEPENDS_append_class-native = " file-replacement-native bzip2-
> replacement-native"
> +DEPENDS_append_class-nativesdk = " file-replacement-nativesdk"


file-nativesdk from the normal DEPENDS should be fine here? I don't
think you need file-replacement-nativesdk?

Cheers,

Richard

[PATCH 8/8] [PATCH v2] meta-toolchain: Added dnf-nativesdk into cross-development toolchain.

[Zheng Ruoqin]

Add dnf-nativesdk and it's runtime dependence to make dnf work on cross-development environment.

Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
---
 meta/classes/toolchain-scripts.bbclass                             | 1 +
 meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb | 4 ++++
 2 files changed, 5 insertions(+)

diff --git a/meta/classes/toolchain-scripts.bbclass b/meta/classes/toolchain-scripts.bbclass
index 0ff5301..63a7ee4 100644
--- a/meta/classes/toolchain-scripts.bbclass
+++ b/meta/classes/toolchain-scripts.bbclass
@@ -97,6 +97,7 @@ toolchain_shared_env_script () {
 	echo 'export CPPFLAGS="${TARGET_CPPFLAGS}"' >> $script
 	echo 'export KCFLAGS="--sysroot=$SDKTARGETSYSROOT"' >> $script
 	echo 'export OECORE_DISTRO_VERSION="${DISTRO_VERSION}"' >> $script
+        echo 'export MACHINE_ARCH=${MACHINE_ARCH}' >> $script
 	echo 'export OECORE_SDK_VERSION="${SDK_VERSION}"' >> $script
 	echo 'export ARCH=${ARCH}' >> $script
 	echo 'export CROSS_COMPILE=${TARGET_PREFIX}' >> $script
diff --git a/meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb b/meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb
index e2f6169..1370a82 100644
--- a/meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb
+++ b/meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb
@@ -25,6 +25,10 @@ RDEPENDS_${PN} = "\
     nativesdk-cmake \
     ${@bb.utils.contains('DISTRO_FEATURES', 'wayland', 'nativesdk-wayland', '', d)} \
     nativesdk-sdk-provides-dummy \
+    nativesdk-libnewt-python \
+    nativesdk-createrepo-c \
+    nativesdk-gpgme \
+    nativesdk-update-rc.d \
     "
 
 RDEPENDS_${PN}_darwin = "\
-- 
2.7.4

Re: [PATCH 8/8] [PATCH v2] meta-toolchain: Added dnf-nativesdk into cross-development toolchain.

[Richard Purdie]

On Sun, 2018-06-24 at 03:53 +0800, Zheng Ruoqin wrote:
> Add dnf-nativesdk and it's runtime dependence to make dnf work on
> cross-development environment.
> 
> Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>

I don't mind adding enough of the changes so that dnf-nativesdk is
buildable so some of your other patches can be merged.

I do not want to add dnf-nativesdk to meta-toolchain by default however
as there are many people who don't need this there. I'd suggest this is
a customisation you'll need to maintain yourselves.

I appreciate why you want to do this, I also believe we have a better
technique in the form of the eSDK, where we can use the same tools and
the same codebase to build for example a rootfs.

The eSDK use case (a locked sstate cache) is designed so that a user
doesn't need to worry about a whole build, or building from scratch.
They can use the same tools everyone else uses and the same workflow
and code to bulld a rootfs or a recipe or any workflow. This makes it
much more powerful and able to fulfil many different use cases compared
to meta-toolchain. In the long run I'd therefore prefer we promote this
and use the eSDK as I think it will become our preferred way of
handling problems like this.

Cheers,

Richard

Re: [PATCH 8/8] [PATCH v2] meta-toolchain: Added dnf-nativesdk into cross-development toolchain.

[Zheng, Ruoqin]

Hi Richard

      eSDK is actually a better technique for developers.  But it’s only suitable for those people who has experience on Yocto Project.

      In the other hand, using dnf-nativesdk in meta-toolchain to customize rootfs is easier fot those people who are familiar with dnf(I think most linux user known it).

      For example, developers finish the OSS build work and provide the toolchain and packages to users. In this case, users do not need to know any knowledge about yocto build system but just how to use dnf to install a rootfs.

      So it can reduce the workload of end-users who need to customize rootfs for their embedded device. At lease, they don’t need to maintain a yocto build server.

--------------------------------------------------
Zheng Ruoqin
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
ADDR.: No.6 Wenzhu Road, Software Avenue,
       Nanjing, 210012, China
MAIL : zhengrq.fnst@cn.fujistu.com


-----Original Message-----
From: Richard Purdie [mailto:richard.purdie@linuxfoundation.org] 
Sent: Monday, June 25, 2018 3:19 PM
To: Zheng, Ruoqin/郑 若钦 <zhengrq.fnst@cn.fujitsu.com>; openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 8/8] [PATCH v2] meta-toolchain: Added dnf-nativesdk into cross-development toolchain.

On Sun, 2018-06-24 at 03:53 +0800, Zheng Ruoqin wrote:
> Add dnf-nativesdk and it's runtime dependence to make dnf work on 
> cross-development environment.
> 
> Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>

I don't mind adding enough of the changes so that dnf-nativesdk is buildable so some of your other patches can be merged.

I do not want to add dnf-nativesdk to meta-toolchain by default however as there are many people who don't need this there. I'd suggest this is a customisation you'll need to maintain yourselves.

I appreciate why you want to do this, I also believe we have a better technique in the form of the eSDK, where we can use the same tools and the same codebase to build for example a rootfs.

The eSDK use case (a locked sstate cache) is designed so that a user doesn't need to worry about a whole build, or building from scratch.
They can use the same tools everyone else uses and the same workflow and code to bulld a rootfs or a recipe or any workflow. This makes it much more powerful and able to fulfil many different use cases compared to meta-toolchain. In the long run I'd therefore prefer we promote this and use the eSDK as I think it will become our preferred way of handling problems like this.

Cheers,

Richard

Re: [PATCH 8/8] [PATCH v2] meta-toolchain: Added dnf-nativesdk into cross-development toolchain.

[richard.purdie]

On Tue, 2018-07-31 at 02:18 +0000, Zheng, Ruoqin wrote:
> Hi Richard
> 
>       eSDK is actually a better technique for developers.  But it’s
> only suitable for those people who has experience on Yocto Project.

Remember that the eSDK can function just like the SDK. You can use more
of its tools but you don't have to.

>       In the other hand, using dnf-nativesdk in meta-toolchain to
> customize rootfs is easier fot those people who are familiar with
> dnf(I think most linux user known it).

Why not add some dnf like wrappers around the eSDK though? We have
tools like devtool and recipetool but there is a lot of potential to
add a simpler interface to enable these "customise rootfs" type of
workflows.

>       For example, developers finish the OSS build work and provide
> the toolchain and packages to users. In this case, users do not need
> to know any knowledge about yocto build system but just how to use
> dnf to install a rootfs.
> 
>       So it can reduce the workload of end-users who need to
> customize rootfs for their embedded device. At lease, they don’t need
> to maintain a yocto build server.

The eSDK behaves very much like the SDK and then you have access to
whichever tools the eSDK is providing, all the way up to the full build
system but only if you need that.

I still think there is the option of providing some simpler tooling to
the eSDK which would work for the kinds of users you're talking about.

Cheers,

Richard

Re: [PATCH 8/8] [PATCH v2] meta-toolchain: Added dnf-nativesdk into cross-development toolchain.

[Alexander Kanavin]

2018-07-31 13:15 GMT+02:00  <richard.purdie@linuxfoundation.org>:
> Why not add some dnf like wrappers around the eSDK though? We have
> tools like devtool and recipetool but there is a lot of potential to
> add a simpler interface to enable these "customise rootfs" type of
> workflows.

For what it's worth, I'm just now looking into an integration process
of one of automotive tier1s. They use a similar, custom developed ipk
tooling to add pre-built binaries to a pre-generated rootfs. So yes,
I'd also rather have a standard, common solution for this.

Alex