Re: [OE-core] [PATCH 8/8] [PATCH v2] meta-toolchain: Added dnf-nativesdk into cross-development toolchain.
2018-07-31 13:15 GMT+02:00 : > 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 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 8/8] [PATCH v2] meta-toolchain: Added dnf-nativesdk into cross-development toolchain.
On Tue, 2018-07-31 at 02:18 +, 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 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 8/8] [PATCH v2] meta-toolchain: Added dnf-nativesdk into cross-development toolchain.
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.f...@cn.fujistu.com -Original Message- From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org] Sent: Monday, June 25, 2018 3:19 PM To: Zheng, Ruoqin/郑 若钦 ; 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 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 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
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 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 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 8/8] [PATCH v2] meta-toolchain: Added dnf-nativesdk into cross-development toolchain.
Add dnf-nativesdk and it's runtime dependence to make dnf work on
cross-development environment.
Signed-off-by: Zheng Ruoqin
---
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
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
