* Re: [PATCH] poky: kirkstone: eSDK: fix build-in eSDK environment file generation
[not found] <20231122085438.7328-1-alb3rt0.m3rciai@gmail.com>
@ 2023-11-22 8:59 ` Alexander Kanavin
2023-11-22 9:18 ` Alberto Merciai
0 siblings, 1 reply; 10+ messages in thread
From: Alexander Kanavin @ 2023-11-22 8:59 UTC (permalink / raw)
To: Alberto Merciai; +Cc: openembedded-core
Can you please describe in the commit message how the issue can be
reproduced and observed, because otherwise I can't do a meaningful
review, and would have to say 'no' until I can?
Do we need to improve the tests? Do they miss something?
Alex
On Wed, 22 Nov 2023 at 09:54, Alberto Merciai <alb3rt0.m3rciai@gmail.com> wrote:
>
> From: amerciai <alb3rt0.m3rciai@gmail.com>
>
> - Following Setting up the Extensible SDK environment directly in a Yocto build
> https://docs.yoctoproject.org/4.0.14/sdk-manual/extensible.html#setting-up-the-extensible-sdk-environment-directly-in-a-yocto-build
> The generated environment file does not point to the
> correct sysroot folder, then the end user is not able
> to cross-compile by sourcing the file.
>
> - The same for kirkstone-4.0.10
>
> - By analyzing
> https://lore.kernel.org/all/20220622103312.1098389-3-alex@linutronix.de/T/#m7eadf6c722410f5b233ebba9fc700a895af9f052
> I found that changes apllied to
> meta/classes/toolchain-scripts.bbclass
> solve the issue.
>
> Suggested-by: Alexander Kanavin <alex.kanavin@gmail.com>
> Signed-off-by: Alberto Merciai <alb3rt0.m3rciai@gmail.com>
>
> diff --git a/meta/classes/toolchain-scripts.bbclass b/meta/classes/toolchain-scripts.bbclass
> index d735d434e6..ec50a1efa0 100644
> --- a/meta/classes/toolchain-scripts.bbclass
> +++ b/meta/classes/toolchain-scripts.bbclass
> @@ -70,15 +70,23 @@ toolchain_create_tree_env_script () {
> script=${TMPDIR}/environment-setup-${REAL_MULTIMACH_TARGET_SYS}
> rm -f $script
> touch $script
> + echo 'standalone_sysroot_target="${STAGING_DIR}/${MACHINE}"' >> $script
> + echo 'standalone_sysroot_native="${STAGING_DIR}/${BUILD_ARCH}"' >> $script
> echo 'orig=`pwd`; cd ${COREBASE}; . ./oe-init-build-env ${TOPDIR}; cd $orig' >> $script
> - echo 'export PATH=${STAGING_DIR_NATIVE}/usr/bin:${STAGING_BINDIR_TOOLCHAIN}:$PATH' >> $script
> - echo 'export PKG_CONFIG_SYSROOT_DIR=${PKG_CONFIG_SYSROOT_DIR}' >> $script
> - echo 'export PKG_CONFIG_PATH=${PKG_CONFIG_PATH}' >> $script
> +
> + echo 'export PATH=$standalone_sysroot_native/${bindir_native}:$standalone_sysroot_native/${bindir_native}/${TARGET_SYS}:$PATH' >> $script
> + echo 'export PKG_CONFIG_SYSROOT_DIR=$standalone_sysroot_target' >> $script
> + echo 'export PKG_CONFIG_PATH=$standalone_sysroot_target'"$libdir"'/pkgconfig:$standalone_sysroot_target'"$prefix"'/share/pkgconfig' >> $script
> +
> echo 'export CONFIG_SITE="${CONFIG_SITE}"' >> $script
> - echo 'export SDKTARGETSYSROOT=${STAGING_DIR_TARGET}' >> $script
> - echo 'export OECORE_NATIVE_SYSROOT="${STAGING_DIR_NATIVE}"' >> $script
> - echo 'export OECORE_TARGET_SYSROOT="${STAGING_DIR_TARGET}"' >> $script
> - echo 'export OECORE_ACLOCAL_OPTS="-I ${STAGING_DIR_NATIVE}/usr/share/aclocal"' >> $script
> +
> + echo 'export SDKTARGETSYSROOT=$standalone_sysroot_target' >> $script
> + echo 'export OECORE_NATIVE_SYSROOT=$standalone_sysroot_native' >> $script
> + echo 'export OECORE_TARGET_SYSROOT=$standalone_sysroot_target' >> $script
> + echo 'export OECORE_ACLOCAL_OPTS="-I $standalone_sysroot_native/usr/share/aclocal"' >> $script
> + echo 'export OECORE_BASELIB="${baselib}"' >> $script
> + echo 'export OECORE_TARGET_ARCH="${TARGET_ARCH}"' >>$script
> + echo 'export OECORE_TARGET_OS="${TARGET_OS}"' >>$script
>
> toolchain_shared_env_script
> }
> --
> 2.34.1
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* [PATCH] poky: kirkstone: eSDK: fix build-in eSDK environment file generation
@ 2023-11-22 9:04 Alberto Merciai
2023-11-22 9:13 ` Alexander Kanavin
0 siblings, 1 reply; 10+ messages in thread
From: Alberto Merciai @ 2023-11-22 9:04 UTC (permalink / raw)
To: openembedded-core; +Cc: alb3rt0.m3rciai, Alexander Kanavin
From: amerciai <alb3rt0.m3rciai@gmail.com>
- Following Setting up the Extensible SDK environment directly in a Yocto build
https://docs.yoctoproject.org/4.0.14/sdk-manual/extensible.html#setting-up-the-extensible-sdk-environment-directly-in-a-yocto-build
The generated environment file does not point to the
correct sysroot folder, then the end user is not able
to cross-compile by sourcing the file.
- The same for kirkstone-4.0.10
- By analyzing
https://lore.kernel.org/all/20220622103312.1098389-3-alex@linutronix.de/T/#m7eadf6c722410f5b233ebba9fc700a895af9f052
I found that changes apllied to
meta/classes/toolchain-scripts.bbclass
solve the issue.
Suggested-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Alberto Merciai <alb3rt0.m3rciai@gmail.com>
diff --git a/meta/classes/toolchain-scripts.bbclass b/meta/classes/toolchain-scripts.bbclass
index d735d434e6..ec50a1efa0 100644
--- a/meta/classes/toolchain-scripts.bbclass
+++ b/meta/classes/toolchain-scripts.bbclass
@@ -70,15 +70,23 @@ toolchain_create_tree_env_script () {
script=${TMPDIR}/environment-setup-${REAL_MULTIMACH_TARGET_SYS}
rm -f $script
touch $script
+ echo 'standalone_sysroot_target="${STAGING_DIR}/${MACHINE}"' >> $script
+ echo 'standalone_sysroot_native="${STAGING_DIR}/${BUILD_ARCH}"' >> $script
echo 'orig=`pwd`; cd ${COREBASE}; . ./oe-init-build-env ${TOPDIR}; cd $orig' >> $script
- echo 'export PATH=${STAGING_DIR_NATIVE}/usr/bin:${STAGING_BINDIR_TOOLCHAIN}:$PATH' >> $script
- echo 'export PKG_CONFIG_SYSROOT_DIR=${PKG_CONFIG_SYSROOT_DIR}' >> $script
- echo 'export PKG_CONFIG_PATH=${PKG_CONFIG_PATH}' >> $script
+
+ echo 'export PATH=$standalone_sysroot_native/${bindir_native}:$standalone_sysroot_native/${bindir_native}/${TARGET_SYS}:$PATH' >> $script
+ echo 'export PKG_CONFIG_SYSROOT_DIR=$standalone_sysroot_target' >> $script
+ echo 'export PKG_CONFIG_PATH=$standalone_sysroot_target'"$libdir"'/pkgconfig:$standalone_sysroot_target'"$prefix"'/share/pkgconfig' >> $script
+
echo 'export CONFIG_SITE="${CONFIG_SITE}"' >> $script
- echo 'export SDKTARGETSYSROOT=${STAGING_DIR_TARGET}' >> $script
- echo 'export OECORE_NATIVE_SYSROOT="${STAGING_DIR_NATIVE}"' >> $script
- echo 'export OECORE_TARGET_SYSROOT="${STAGING_DIR_TARGET}"' >> $script
- echo 'export OECORE_ACLOCAL_OPTS="-I ${STAGING_DIR_NATIVE}/usr/share/aclocal"' >> $script
+
+ echo 'export SDKTARGETSYSROOT=$standalone_sysroot_target' >> $script
+ echo 'export OECORE_NATIVE_SYSROOT=$standalone_sysroot_native' >> $script
+ echo 'export OECORE_TARGET_SYSROOT=$standalone_sysroot_target' >> $script
+ echo 'export OECORE_ACLOCAL_OPTS="-I $standalone_sysroot_native/usr/share/aclocal"' >> $script
+ echo 'export OECORE_BASELIB="${baselib}"' >> $script
+ echo 'export OECORE_TARGET_ARCH="${TARGET_ARCH}"' >>$script
+ echo 'export OECORE_TARGET_OS="${TARGET_OS}"' >>$script
toolchain_shared_env_script
}
--
2.34.1
^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: [PATCH] poky: kirkstone: eSDK: fix build-in eSDK environment file generation
2023-11-22 9:04 [PATCH] poky: kirkstone: eSDK: fix build-in eSDK environment file generation Alberto Merciai
@ 2023-11-22 9:13 ` Alexander Kanavin
0 siblings, 0 replies; 10+ messages in thread
From: Alexander Kanavin @ 2023-11-22 9:13 UTC (permalink / raw)
To: Alberto Merciai, Richard Purdie; +Cc: openembedded-core
There is still no description of how to observe the issue, no answer
to my question, and I did not suggest any of this at any point (I had
to go and check - some of my old patches were used as a reference,
this is not the same as Suggested-by).
NACK.
Alex
On Wed, 22 Nov 2023 at 10:04, Alberto Merciai <alb3rt0.m3rciai@gmail.com> wrote:
>
> From: amerciai <alb3rt0.m3rciai@gmail.com>
>
> - Following Setting up the Extensible SDK environment directly in a Yocto build
> https://docs.yoctoproject.org/4.0.14/sdk-manual/extensible.html#setting-up-the-extensible-sdk-environment-directly-in-a-yocto-build
> The generated environment file does not point to the
> correct sysroot folder, then the end user is not able
> to cross-compile by sourcing the file.
>
> - The same for kirkstone-4.0.10
>
> - By analyzing
> https://lore.kernel.org/all/20220622103312.1098389-3-alex@linutronix.de/T/#m7eadf6c722410f5b233ebba9fc700a895af9f052
> I found that changes apllied to
> meta/classes/toolchain-scripts.bbclass
> solve the issue.
>
> Suggested-by: Alexander Kanavin <alex.kanavin@gmail.com>
> Signed-off-by: Alberto Merciai <alb3rt0.m3rciai@gmail.com>
>
> diff --git a/meta/classes/toolchain-scripts.bbclass b/meta/classes/toolchain-scripts.bbclass
> index d735d434e6..ec50a1efa0 100644
> --- a/meta/classes/toolchain-scripts.bbclass
> +++ b/meta/classes/toolchain-scripts.bbclass
> @@ -70,15 +70,23 @@ toolchain_create_tree_env_script () {
> script=${TMPDIR}/environment-setup-${REAL_MULTIMACH_TARGET_SYS}
> rm -f $script
> touch $script
> + echo 'standalone_sysroot_target="${STAGING_DIR}/${MACHINE}"' >> $script
> + echo 'standalone_sysroot_native="${STAGING_DIR}/${BUILD_ARCH}"' >> $script
> echo 'orig=`pwd`; cd ${COREBASE}; . ./oe-init-build-env ${TOPDIR}; cd $orig' >> $script
> - echo 'export PATH=${STAGING_DIR_NATIVE}/usr/bin:${STAGING_BINDIR_TOOLCHAIN}:$PATH' >> $script
> - echo 'export PKG_CONFIG_SYSROOT_DIR=${PKG_CONFIG_SYSROOT_DIR}' >> $script
> - echo 'export PKG_CONFIG_PATH=${PKG_CONFIG_PATH}' >> $script
> +
> + echo 'export PATH=$standalone_sysroot_native/${bindir_native}:$standalone_sysroot_native/${bindir_native}/${TARGET_SYS}:$PATH' >> $script
> + echo 'export PKG_CONFIG_SYSROOT_DIR=$standalone_sysroot_target' >> $script
> + echo 'export PKG_CONFIG_PATH=$standalone_sysroot_target'"$libdir"'/pkgconfig:$standalone_sysroot_target'"$prefix"'/share/pkgconfig' >> $script
> +
> echo 'export CONFIG_SITE="${CONFIG_SITE}"' >> $script
> - echo 'export SDKTARGETSYSROOT=${STAGING_DIR_TARGET}' >> $script
> - echo 'export OECORE_NATIVE_SYSROOT="${STAGING_DIR_NATIVE}"' >> $script
> - echo 'export OECORE_TARGET_SYSROOT="${STAGING_DIR_TARGET}"' >> $script
> - echo 'export OECORE_ACLOCAL_OPTS="-I ${STAGING_DIR_NATIVE}/usr/share/aclocal"' >> $script
> +
> + echo 'export SDKTARGETSYSROOT=$standalone_sysroot_target' >> $script
> + echo 'export OECORE_NATIVE_SYSROOT=$standalone_sysroot_native' >> $script
> + echo 'export OECORE_TARGET_SYSROOT=$standalone_sysroot_target' >> $script
> + echo 'export OECORE_ACLOCAL_OPTS="-I $standalone_sysroot_native/usr/share/aclocal"' >> $script
> + echo 'export OECORE_BASELIB="${baselib}"' >> $script
> + echo 'export OECORE_TARGET_ARCH="${TARGET_ARCH}"' >>$script
> + echo 'export OECORE_TARGET_OS="${TARGET_OS}"' >>$script
>
> toolchain_shared_env_script
> }
> --
> 2.34.1
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] poky: kirkstone: eSDK: fix build-in eSDK environment file generation
2023-11-22 8:59 ` Alexander Kanavin
@ 2023-11-22 9:18 ` Alberto Merciai
2023-11-22 9:30 ` Alexander Kanavin
0 siblings, 1 reply; 10+ messages in thread
From: Alberto Merciai @ 2023-11-22 9:18 UTC (permalink / raw)
To: Alexander Kanavin; +Cc: openembedded-core
[-- Attachment #1: Type: text/plain, Size: 4559 bytes --]
Hello Alexander,
Of course
I'm following the guide
https://docs.yoctoproject.org/4.0.14/sdk-manual/extensible.html#setting-up-the-extensible-sdk-environment-directly-in-a-yocto-build
create environment file for cross compilation
$ bitbake meta-ide-support
$ bitbake -c populate_sysroot gtk+3
# or any other target or native item that the application developer would need
$ bitbake build-sysroots
then you can open a new terminal and sourcing the file generated by the
above steps using
source tmp/deploy/images/qemux86-64/environment-setup-core2-64-poky-linux
go inside the project you would like cross-compile and you get errors
Let me know if it is enough for you, thanks :)
On Wed, Nov 22, 2023 at 9:59 AM Alexander Kanavin <alex.kanavin@gmail.com>
wrote:
> Can you please describe in the commit message how the issue can be
> reproduced and observed, because otherwise I can't do a meaningful
> review, and would have to say 'no' until I can?
>
> Do we need to improve the tests? Do they miss something?
>
> Alex
>
> On Wed, 22 Nov 2023 at 09:54, Alberto Merciai <alb3rt0.m3rciai@gmail.com>
> wrote:
> >
> > From: amerciai <alb3rt0.m3rciai@gmail.com>
> >
> > - Following Setting up the Extensible SDK environment directly in a
> Yocto build
> >
> https://docs.yoctoproject.org/4.0.14/sdk-manual/extensible.html#setting-up-the-extensible-sdk-environment-directly-in-a-yocto-build
> > The generated environment file does not point to the
> > correct sysroot folder, then the end user is not able
> > to cross-compile by sourcing the file.
> >
> > - The same for kirkstone-4.0.10
> >
> > - By analyzing
> >
> https://lore.kernel.org/all/20220622103312.1098389-3-alex@linutronix.de/T/#m7eadf6c722410f5b233ebba9fc700a895af9f052
> > I found that changes apllied to
> > meta/classes/toolchain-scripts.bbclass
> > solve the issue.
> >
> > Suggested-by: Alexander Kanavin <alex.kanavin@gmail.com>
> > Signed-off-by: Alberto Merciai <alb3rt0.m3rciai@gmail.com>
> >
> > diff --git a/meta/classes/toolchain-scripts.bbclass
> b/meta/classes/toolchain-scripts.bbclass
> > index d735d434e6..ec50a1efa0 100644
> > --- a/meta/classes/toolchain-scripts.bbclass
> > +++ b/meta/classes/toolchain-scripts.bbclass
> > @@ -70,15 +70,23 @@ toolchain_create_tree_env_script () {
> > script=${TMPDIR}/environment-setup-${REAL_MULTIMACH_TARGET_SYS}
> > rm -f $script
> > touch $script
> > + echo 'standalone_sysroot_target="${STAGING_DIR}/${MACHINE}"' >>
> $script
> > + echo 'standalone_sysroot_native="${STAGING_DIR}/${BUILD_ARCH}"'
> >> $script
> > echo 'orig=`pwd`; cd ${COREBASE}; . ./oe-init-build-env
> ${TOPDIR}; cd $orig' >> $script
> > - echo 'export
> PATH=${STAGING_DIR_NATIVE}/usr/bin:${STAGING_BINDIR_TOOLCHAIN}:$PATH' >>
> $script
> > - echo 'export PKG_CONFIG_SYSROOT_DIR=${PKG_CONFIG_SYSROOT_DIR}'
> >> $script
> > - echo 'export PKG_CONFIG_PATH=${PKG_CONFIG_PATH}' >> $script
> > +
> > + echo 'export
> PATH=$standalone_sysroot_native/${bindir_native}:$standalone_sysroot_native/${bindir_native}/${TARGET_SYS}:$PATH'
> >> $script
> > + echo 'export PKG_CONFIG_SYSROOT_DIR=$standalone_sysroot_target'
> >> $script
> > + echo 'export
> PKG_CONFIG_PATH=$standalone_sysroot_target'"$libdir"'/pkgconfig:$standalone_sysroot_target'"$prefix"'/share/pkgconfig'
> >> $script
> > +
> > echo 'export CONFIG_SITE="${CONFIG_SITE}"' >> $script
> > - echo 'export SDKTARGETSYSROOT=${STAGING_DIR_TARGET}' >> $script
> > - echo 'export OECORE_NATIVE_SYSROOT="${STAGING_DIR_NATIVE}"' >>
> $script
> > - echo 'export OECORE_TARGET_SYSROOT="${STAGING_DIR_TARGET}"' >>
> $script
> > - echo 'export OECORE_ACLOCAL_OPTS="-I
> ${STAGING_DIR_NATIVE}/usr/share/aclocal"' >> $script
> > +
> > + echo 'export SDKTARGETSYSROOT=$standalone_sysroot_target' >>
> $script
> > + echo 'export OECORE_NATIVE_SYSROOT=$standalone_sysroot_native'
> >> $script
> > + echo 'export OECORE_TARGET_SYSROOT=$standalone_sysroot_target'
> >> $script
> > + echo 'export OECORE_ACLOCAL_OPTS="-I
> $standalone_sysroot_native/usr/share/aclocal"' >> $script
> > + echo 'export OECORE_BASELIB="${baselib}"' >> $script
> > + echo 'export OECORE_TARGET_ARCH="${TARGET_ARCH}"' >>$script
> > + echo 'export OECORE_TARGET_OS="${TARGET_OS}"' >>$script
> >
> > toolchain_shared_env_script
> > }
> > --
> > 2.34.1
> >
>
[-- Attachment #2: Type: text/html, Size: 7034 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] poky: kirkstone: eSDK: fix build-in eSDK environment file generation
2023-11-22 9:18 ` Alberto Merciai
@ 2023-11-22 9:30 ` Alexander Kanavin
2023-11-22 12:10 ` Alberto Merciai
2023-11-22 12:45 ` Alexander Kanavin
0 siblings, 2 replies; 10+ messages in thread
From: Alexander Kanavin @ 2023-11-22 9:30 UTC (permalink / raw)
To: Alberto Merciai
Cc: openembedded-core, Richard Purdie, Michael Opdenacker, docs
On Wed, 22 Nov 2023 at 10:18, Alberto Merciai <alb3rt0.m3rciai@gmail.com> wrote:
> Of course
> I'm following the guide
> https://docs.yoctoproject.org/4.0.14/sdk-manual/extensible.html#setting-up-the-extensible-sdk-environment-directly-in-a-yocto-build
>
> create environment file for cross compilation
>
> $ bitbake meta-ide-support
> $ bitbake -c populate_sysroot gtk+3
> # or any other target or native item that the application developer would need
> $ bitbake build-sysroots
>
> then you can open a new terminal and sourcing the file generated by the above steps using
> source tmp/deploy/images/qemux86-64/environment-setup-core2-64-poky-linux
>
> go inside the project you would like cross-compile and you get errors
Thanks, now I understand what happened. This feature was actually
never backported to kirkstone (and won't be because of LTS policy - no
new features), but documentation was (mistakenly) updated to state
that it was:
https://git.yoctoproject.org/yocto-docs/commit/?h=kirkstone&id=5e2ec35e3d63f9c73726122fe2b3dd6d6f85a77e
Michael, the bits about meta-ide-suppport/build-sysroots need to be
reverted, before more people get misled.
Alberto, can you check that this works as expected on master or any
more recent release where my commit is present, and the file is set
correctly?
Alex
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] poky: kirkstone: eSDK: fix build-in eSDK environment file generation
2023-11-22 9:30 ` Alexander Kanavin
@ 2023-11-22 12:10 ` Alberto Merciai
2023-11-22 12:12 ` Alexander Kanavin
2023-11-22 12:45 ` Alexander Kanavin
1 sibling, 1 reply; 10+ messages in thread
From: Alberto Merciai @ 2023-11-22 12:10 UTC (permalink / raw)
To: Alexander Kanavin
Cc: openembedded-core, Richard Purdie, Michael Opdenacker, docs
On Wed, Nov 22, 2023 at 10:30:49AM +0100, Alexander Kanavin wrote:
> Alberto, can you check that this works as expected on master or any
> more recent release where my commit is present, and the file is set
> correctly?
>
> Alex
Hi Alex,
Let me understand if we are both at the same page.
That feture will be not integrate in kirkstone, right?
Are you askin me to try that on a more recent version different from
kirkstone?
Thanks,
Alberto
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] poky: kirkstone: eSDK: fix build-in eSDK environment file generation
2023-11-22 12:10 ` Alberto Merciai
@ 2023-11-22 12:12 ` Alexander Kanavin
2023-11-22 13:46 ` Alberto Merciai
0 siblings, 1 reply; 10+ messages in thread
From: Alexander Kanavin @ 2023-11-22 12:12 UTC (permalink / raw)
To: Alberto Merciai
Cc: openembedded-core, Richard Purdie, Michael Opdenacker, docs
On Wed, 22 Nov 2023 at 13:10, Alberto Merciai <alb3rt0.m3rciai@gmail.com> wrote:
> > Alberto, can you check that this works as expected on master or any
> > more recent release where my commit is present, and the file is set
> > correctly?
> Let me understand if we are both at the same page.
> That feture will be not integrate in kirkstone, right?
> Are you askin me to try that on a more recent version different from
> kirkstone?
That's right. If you have to stay on kirkstone, then you have to
maintain a private backport.
Alex
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] poky: kirkstone: eSDK: fix build-in eSDK environment file generation
2023-11-22 9:30 ` Alexander Kanavin
2023-11-22 12:10 ` Alberto Merciai
@ 2023-11-22 12:45 ` Alexander Kanavin
2023-11-22 13:48 ` Alberto Merciai
1 sibling, 1 reply; 10+ messages in thread
From: Alexander Kanavin @ 2023-11-22 12:45 UTC (permalink / raw)
To: Alberto Merciai
Cc: openembedded-core, Richard Purdie, Michael Opdenacker, docs
On Wed, 22 Nov 2023 at 10:30, Alexander Kanavin <alex.kanavin@gmail.com> wrote:
> Thanks, now I understand what happened. This feature was actually
> never backported to kirkstone (and won't be because of LTS policy - no
> new features), but documentation was (mistakenly) updated to state
> that it was:
> https://git.yoctoproject.org/yocto-docs/commit/?h=kirkstone&id=5e2ec35e3d63f9c73726122fe2b3dd6d6f85a77e
>
> Michael, the bits about meta-ide-suppport/build-sysroots need to be
> reverted, before more people get misled.
I've now sent a patch for it to docs@ - needed only for kirkstone.
Alex
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] poky: kirkstone: eSDK: fix build-in eSDK environment file generation
2023-11-22 12:12 ` Alexander Kanavin
@ 2023-11-22 13:46 ` Alberto Merciai
0 siblings, 0 replies; 10+ messages in thread
From: Alberto Merciai @ 2023-11-22 13:46 UTC (permalink / raw)
To: Alexander Kanavin
Cc: openembedded-core, Richard Purdie, Michael Opdenacker, docs
On Wed, Nov 22, 2023 at 01:12:00PM +0100, Alexander Kanavin wrote:
> That's right. If you have to stay on kirkstone, then you have to
> maintain a private backport.
Understood thanks,
Alberto
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] poky: kirkstone: eSDK: fix build-in eSDK environment file generation
2023-11-22 12:45 ` Alexander Kanavin
@ 2023-11-22 13:48 ` Alberto Merciai
0 siblings, 0 replies; 10+ messages in thread
From: Alberto Merciai @ 2023-11-22 13:48 UTC (permalink / raw)
To: Alexander Kanavin
Cc: openembedded-core, Richard Purdie, Michael Opdenacker, docs
On Wed, Nov 22, 2023 at 01:45:28PM +0100, Alexander Kanavin wrote:
> I've now sent a patch for it to docs@ - needed only for kirkstone.
>
> Alex
Ok, regardig test you were asking for, I'm not able to do that right
now.
Is something that I will do in next weeks, in case I will share.
Regards,
Alberto
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2023-11-22 13:49 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-11-22 9:04 [PATCH] poky: kirkstone: eSDK: fix build-in eSDK environment file generation Alberto Merciai
2023-11-22 9:13 ` Alexander Kanavin
[not found] <20231122085438.7328-1-alb3rt0.m3rciai@gmail.com>
2023-11-22 8:59 ` Alexander Kanavin
2023-11-22 9:18 ` Alberto Merciai
2023-11-22 9:30 ` Alexander Kanavin
2023-11-22 12:10 ` Alberto Merciai
2023-11-22 12:12 ` Alexander Kanavin
2023-11-22 13:46 ` Alberto Merciai
2023-11-22 12:45 ` Alexander Kanavin
2023-11-22 13:48 ` Alberto Merciai
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox