All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joshua Watt" <JPEWhacker@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe][meta-oe][PATCH] classes: Add Android sparse image class
Date: Mon, 8 Mar 2021 15:45:10 -0600	[thread overview]
Message-ID: <6e9926ca-3405-30bf-1b04-1a9f60cd3adb@gmail.com> (raw)
In-Reply-To: <CAMKF1sraAE4Y69=vnfnvhXoFRk=sHiOgyU+Ck3C12m1=FN_mFA@mail.gmail.com>


On 3/8/21 2:54 PM, Khem Raj wrote:
> On Fri, Mar 5, 2021 at 11:09 AM Joshua Watt <JPEWhacker@gmail.com> wrote:
>> Adds a class to create sparse image files using the Android tools
>> ---
>>   meta-oe/classes/image_types_simg.bbclass | 16 ++++++++++++++++
>>   1 file changed, 16 insertions(+)
>>   create mode 100644 meta-oe/classes/image_types_simg.bbclass
>>
>> diff --git a/meta-oe/classes/image_types_simg.bbclass b/meta-oe/classes/image_types_simg.bbclass
>> new file mode 100644
>> index 000000000..a53fafe5e
>> --- /dev/null
>> +++ b/meta-oe/classes/image_types_simg.bbclass
>> @@ -0,0 +1,16 @@
>> +inherit image_types
>> +
>> +CONVERSIONTYPES += "simg"
> I wonder if the name could be made sparse-img ?
> simg might indicate, signed image too.

Ya we can do that


>
>> +CONVERSION_CMD_simg() {
>> +    in="${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.${type}"
>> +    out="${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.${type}.simg"
>> +    case "${type}" in
>> +        ext*)
>> +            ext2simg "$in" "$out"
>> +            ;;
>> +        *)
>> +            img2simg "$in" "$out"
>> +            ;;
>> +    esac
>> +}
>> +CONVERSION_DEPENDS_simg = "android-tools-native"
>> --
>> 2.30.0
>>
>>
>> 
>>

  reply	other threads:[~2021-03-08 21:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 19:08 [oe][meta-oe][PATCH] classes: Add Android sparse image class Joshua Watt
2021-03-08 20:54 ` Khem Raj
2021-03-08 21:45   ` Joshua Watt [this message]
2021-03-08 21:51 ` [oe][meta-oe][PATCH v2] " Joshua Watt

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=6e9926ca-3405-30bf-1b04-1a9f60cd3adb@gmail.com \
    --to=jpewhacker@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.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.