meta-arago.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: Chirag Shilwant <c-shilwant@ti.com>
To: <detheridge@ti.com>, <meta-arago@lists.yoctoproject.org>,
	<reatmon@ti.com>, <denys@konsulko.com>
Cc: <rs@ti.com>, Gyan Gupta <g-gupta@ti.com>, Khasim <khasim@ti.com>
Subject: Re: [EXTERNAL] [meta-arago][oe-layersetup][PATCH] oe-layersetup: add a new kirkstone config for chromium support
Date: Fri, 9 Feb 2024 15:24:51 +0530	[thread overview]
Message-ID: <72b4e178-daea-464d-be46-6affdb80a74f@ti.com> (raw)
In-Reply-To: <20240208190259.6445-1-detheridge@ti.com>

LGTM!

On 09/02/24 00:32, Etheridge, Darren via lists.yoctoproject.org wrote:
> From: Darren Etheridge <detheridge@ ti. com> Add 
> arago-kirkstone-chromium-config. txt. If this config is instantiated, 
> chromium v111 and clang12 layers will be pulled into the yocto build. 
> Signed-off-by: Darren Etheridge <detheridge@ ti. com>
> ZjQcmQRYFpfptBannerStart
> This message was sent from outside of Texas Instruments.
> Do not click links or open attachments unless you recognize the source 
> of this email and know the content is safe.
> ZjQcmQRYFpfptBannerEnd
> From: Darren Etheridge <detheridge@ti.com>
>
> Add arago-kirkstone-chromium-config.txt.
>
> If this config is instantiated, chromium v111 and clang12 layers will
> be pulled into the yocto build.
>
> Signed-off-by: Darren Etheridge <detheridge@ti.com>


Acked-by: Chirag Shilwant <c-shilwant@ti.com>


> ---
>   configs/arago-kirkstone-chromium-config.txt | 16 ++++++++++++++++
>   1 file changed, 16 insertions(+)
>   create mode 100644 configs/arago-kirkstone-chromium-config.txt
>
> diff --git a/configs/arago-kirkstone-chromium-config.txt b/configs/arago-kirkstone-chromium-config.txt
> new file mode 100644
> index 0000000..97d7849
> --- /dev/null
> +++ b/configs/arago-kirkstone-chromium-config.txt
> @@ -0,0 +1,16 @@
> +# This file takes repo entries in the format
> +# repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern]
> +
> +bitbake,https://urldefense.com/v3/__https://git.openembedded.org/bitbake,2.0,HEAD__;!!G3vK!RQ2qI2dJpTo-sk7NlFuKBU7Aj1wn9beMzHP5mF6iE7mRENB9cg5xbMvHx-Ha6BGc3diddFYw3I5whGPLUQ5CTe4dIT2Ku6Y89UBy$
> +meta-arago,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-arago,kirkstone,HEAD,layers=meta-arago-distro:meta-arago-extras:meta-arago-demos:meta-arago-test__;!!G3vK!RQ2qI2dJpTo-sk7NlFuKBU7Aj1wn9beMzHP5mF6iE7mRENB9cg5xbMvHx-Ha6BGc3diddFYw3I5whGPLUQ5CTe4dIT2Ku_W8Cyv9$
> +meta-browser,https://urldefense.com/v3/__https://github.com/OSSystems/meta-browser.git,master,d3d16b47e17dc899e5298cff698dc32e5e639ab4,layers=meta-chromium__;!!G3vK!RQ2qI2dJpTo-sk7NlFuKBU7Aj1wn9beMzHP5mF6iE7mRENB9cg5xbMvHx-Ha6BGc3diddFYw3I5whGPLUQ5CTe4dIT2Ku8EIk_Xk$
> +meta-qt5,https://urldefense.com/v3/__https://github.com/meta-qt5/meta-qt5.git,kirkstone,HEAD,layers=__;!!G3vK!RQ2qI2dJpTo-sk7NlFuKBU7Aj1wn9beMzHP5mF6iE7mRENB9cg5xbMvHx-Ha6BGc3diddFYw3I5whGPLUQ5CTe4dIT2Ku48praKL$
> +meta-virtualization,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-virtualization,kirkstone,HEAD,layers=__;!!G3vK!RQ2qI2dJpTo-sk7NlFuKBU7Aj1wn9beMzHP5mF6iE7mRENB9cg5xbMvHx-Ha6BGc3diddFYw3I5whGPLUQ5CTe4dIT2Ku4rZjPtT$
> +meta-openembedded,https://urldefense.com/v3/__https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems__;!!G3vK!RQ2qI2dJpTo-sk7NlFuKBU7Aj1wn9beMzHP5mF6iE7mRENB9cg5xbMvHx-Ha6BGc3diddFYw3I5whGPLUQ5CTe4dIT2Kuy0CvepO$
> +meta-ti,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-ti,kirkstone,HEAD,layers=meta-ti-extras:meta-ti-bsp__;!!G3vK!RQ2qI2dJpTo-sk7NlFuKBU7Aj1wn9beMzHP5mF6iE7mRENB9cg5xbMvHx-Ha6BGc3diddFYw3I5whGPLUQ5CTe4dIT2Ku4148xLn$
> +meta-arm,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain__;!!G3vK!RQ2qI2dJpTo-sk7NlFuKBU7Aj1wn9beMzHP5mF6iE7mRENB9cg5xbMvHx-Ha6BGc3diddFYw3I5whGPLUQ5CTe4dIT2Ku5pgD3tO$
> +meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=__;!!G3vK!RQ2qI2dJpTo-sk7NlFuKBU7Aj1wn9beMzHP5mF6iE7mRENB9cg5xbMvHx-Ha6BGc3diddFYw3I5whGPLUQ5CTe4dIT2KuweNwaI9$
> +oe-core,https://urldefense.com/v3/__https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta__;!!G3vK!RQ2qI2dJpTo-sk7NlFuKBU7Aj1wn9beMzHP5mF6iE7mRENB9cg5xbMvHx-Ha6BGc3diddFYw3I5whGPLUQ5CTe4dIT2Ku533jFYu$
> +OECORELAYERCONF=./sample-files/bblayers.conf.sample
> +OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
> +BITBAKE_INCLUSIVE_VARS=yes
> -- 
> 2.36.1
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#15137):https://urldefense.com/v3/__https://lists.yoctoproject.org/g/meta-arago/message/15137__;!!G3vK!RQ2qI2dJpTo-sk7NlFuKBU7Aj1wn9beMzHP5mF6iE7mRENB9cg5xbMvHx-Ha6BGc3diddFYw3I5whGPLUQ5CTe4dIT2Ku3xw7Gej$
> Mute This Topic:https://urldefense.com/v3/__https://lists.yoctoproject.org/mt/104244963/7030289__;!!G3vK!RQ2qI2dJpTo-sk7NlFuKBU7Aj1wn9beMzHP5mF6iE7mRENB9cg5xbMvHx-Ha6BGc3diddFYw3I5whGPLUQ5CTe4dIT2Ku6j02Tsx$
> Group Owner: meta-arago+owner@lists.yoctoproject.org
> Unsubscribe:https://urldefense.com/v3/__https://lists.yoctoproject.org/g/meta-arago/unsub__;!!G3vK!RQ2qI2dJpTo-sk7NlFuKBU7Aj1wn9beMzHP5mF6iE7mRENB9cg5xbMvHx-Ha6BGc3diddFYw3I5whGPLUQ5CTe4dIT2Ku33Vy82c$  [c-shilwant@ti.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>


      reply	other threads:[~2024-02-09  9:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08 19:02 [meta-arago][oe-layersetup][PATCH] oe-layersetup: add a new kirkstone config for chromium support detheridge
2024-02-09  9:54 ` Chirag Shilwant [this message]

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=72b4e178-daea-464d-be46-6affdb80a74f@ti.com \
    --to=c-shilwant@ti.com \
    --cc=denys@konsulko.com \
    --cc=detheridge@ti.com \
    --cc=g-gupta@ti.com \
    --cc=khasim@ti.com \
    --cc=meta-arago@lists.yoctoproject.org \
    --cc=reatmon@ti.com \
    --cc=rs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).