All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: t-lannynd@ti.com
Cc: meta-ti@lists.yoctoproject.org, reatmon@ti.com, rs@ti.com,
	detheridge@ti.com, b-brnich@ti.com
Subject: Re: [meta-ti][scarthgap][PATCH] meta-ti-bsp: flutter: fix nativesdk-flutter-engine-sdk build failures
Date: Wed, 14 Oct 2026 17:43:48 -0400	[thread overview]
Message-ID: <20261014214348.GS4190@denix.org> (raw)
In-Reply-To: <20261014204330.2837679-1-t-lannynd@ti.com>

On Wed, Oct 14, 2026 at 03:43:30PM -0500, Thorsten Lannynd via lists.yoctoproject.org wrote:
> Without BB_DEFER_BBCLASSES, :ti-soc is missing from OVERRIDES from a
> nativesdk context so DEPLOY_DIR_IMAGE results in an incorrect path.
> 
> Add :class-nativesdk to layer.conf and a flutter dynamic layer bbappend to
> skip file-rdeps on the bundled host binaries.
> 
> Signed-off-by: Thorsten Lannynd <t-lannynd@ti.com>
> ---
>  meta-ti-bsp/conf/layer.conf                                    | 2 ++
>  .../flutter-engine/flutter-engine-sdk_git.bbappend             | 3 +++
>  2 files changed, 5 insertions(+)
>  create mode 100644 meta-ti-bsp/dynamic-layers/flutter-layer/recipes-graphics/flutter-engine/flutter-engine-sdk_git.bbappend
> 
> diff --git a/meta-ti-bsp/conf/layer.conf b/meta-ti-bsp/conf/layer.conf
> index d87d040b..ef4d233f 100644
> --- a/meta-ti-bsp/conf/layer.conf
> +++ b/meta-ti-bsp/conf/layer.conf
> @@ -24,6 +24,7 @@ LAYERRECOMMENDS_meta-ti-bsp = " \
>  
>  BBFILES_DYNAMIC += " \
>      openembedded-layer:${LAYERDIR}/dynamic-layers/openembedded-layer/recipes*/*/*.bbappend \
> +    flutter-layer:${LAYERDIR}/dynamic-layers/flutter-layer/recipes*/*/*.bbappend \
>  "
>  
>  SIGGEN_EXCLUDERECIPES_ABISAFE += " \
> @@ -34,6 +35,7 @@ HOSTTOOLS_NONFATAL += "truncate xxd comm"
>  
>  TI_COMMON_DEPLOY ?= "${TOPDIR}/deploy-ti"
>  DEPLOY_DIR_IMAGE:ti-soc = "${TI_COMMON_DEPLOY}/images/${MACHINE}"
> +DEPLOY_DIR_IMAGE:class-nativesdk = "${TI_COMMON_DEPLOY}/images/${MACHINE}"

I don't think this is correct.
What nativesdk package are you trying to deploy to the target image deploy 
area?


>  SDK_DEPLOY:ti-soc = "${TI_COMMON_DEPLOY}/sdk"
>  PSEUDO_IGNORE_PATHS:append:ti-soc = ",${TI_COMMON_DEPLOY}"
>  
> diff --git a/meta-ti-bsp/dynamic-layers/flutter-layer/recipes-graphics/flutter-engine/flutter-engine-sdk_git.bbappend b/meta-ti-bsp/dynamic-layers/flutter-layer/recipes-graphics/flutter-engine/flutter-engine-sdk_git.bbappend
> new file mode 100644
> index 00000000..92e38f1e
> --- /dev/null
> +++ b/meta-ti-bsp/dynamic-layers/flutter-layer/recipes-graphics/flutter-engine/flutter-engine-sdk_git.bbappend
> @@ -0,0 +1,3 @@
> +# Pre-built x86-64 host binaries that link against libc/libm from the build
> +# host, not a packaged nativesdk dep.
> +INSANE_SKIP:class-nativesdk:append = " file-rdeps"
> -- 
> 2.34.1


  parent reply	other threads:[~2026-10-14 21:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 20:43 [meta-ti][scarthgap][PATCH] meta-ti-bsp: flutter: fix nativesdk-flutter-engine-sdk build failures Thorsten Lannynd
2026-10-14 20:51 ` PRC Automation
2026-10-14 21:43 ` Denys Dmytriyenko [this message]
2026-10-15  2:11   ` Lannynd, Thorsten

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261014214348.GS4190@denix.org \
    --to=denis@denix.org \
    --cc=b-brnich@ti.com \
    --cc=detheridge@ti.com \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=reatmon@ti.com \
    --cc=rs@ti.com \
    --cc=t-lannynd@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.