9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Eli Cohen <echoline@gmail.com>
To: 9front@9front.org
Subject: [9front] Re: android drawterm build
Date: Sat, 29 Jan 2022 08:06:18 -0800	[thread overview]
Message-ID: <CAHwi9bzTzBrcJRTgnRobHxXibV1cMJFOaAe3NysYoD6U8iVVsA@mail.gmail.com> (raw)
In-Reply-To: <CAHwi9bxE-L-CJi=0YNuxCTHuS0-j8uOnB_9L_p2twu633OJkmw@mail.gmail.com>

as in:

drawable-hdpi/ic_small.png:     PNG image data, 36 x 36, 8-bit
gray+alpha, non-interlaced
drawable-mdpi/ic_small.png:     PNG image data, 24 x 24, 8-bit
gray+alpha, non-interlaced
drawable-xhdpi/ic_small.png:    PNG image data, 48 x 48, 8-bit
gray+alpha, non-interlaced
drawable-xxhdpi/ic_small.png:   PNG image data, 72 x 72, 8-bit
gray+alpha, non-interlaced
drawable-xxxhdpi/ic_small.png:  PNG image data, 96 x 96, 8-bit
gray+alpha, non-interlaced
mipmap-hdpi/ic_launcher.png:    PNG image data, 72 x 72, 8-bit
gray+alpha, non-interlaced
mipmap-mdpi/ic_launcher.png:    PNG image data, 48 x 48, 8-bit
gray+alpha, non-interlaced
mipmap-xhdpi/ic_launcher.png:   PNG image data, 96 x 96, 8-bit
gray+alpha, non-interlaced
mipmap-xxhdpi/ic_launcher.png:  PNG image data, 144 x 144, 8-bit
gray+alpha, non-interlaced
mipmap-xxxhdpi/ic_launcher.png: PNG image data, 192 x 192, 8-bit
gray+alpha, non-interlaced

I found all the ic_small.png files worked best on my phone by first
inverting black and white then setting black to be transparent.

I started all of them from the glenda-t.ico file


On Sat, Jan 29, 2022 at 8:03 AM Eli Cohen <echoline@gmail.com> wrote:
>
> I don't know of a way to send a patch that includes .png files... I've
> edited all the little tuttle icons to the right size etc...
>
> On Sat, Jan 29, 2022 at 7:59 AM Eli Cohen <echoline@gmail.com> wrote:
> >
> > for android drawterm to build, it needs this change to the Makefile
> > clean target:
> >
> > -       rm -f *.o */*.o */*.a *.a drawterm drawterm.exe
> > +       rm -f *.o */*.o */*/*.o */*.a *.a drawterm drawterm.exe
> >
> > because the libgui object files are nested that deep
> >
> > it also really needs all of these files to build:
> >
> > #       new file:   gui-android/bin/.keep
> > #       new file:   gui-android/gen/.keep
> > #       new file:   gui-android/obj/.keep
> > #       new file:   gui-android/res/drawable-hdpi/ic_small.png
> > #       new file:   gui-android/res/drawable-mdpi/ic_small.png
> > #       new file:   gui-android/res/drawable-xhdpi/ic_small.png
> > #       new file:   gui-android/res/drawable-xxhdpi/ic_small.png
> > #       new file:   gui-android/res/drawable-xxxhdpi/ic_small.png
> > #       new file:   gui-android/res/mipmap-hdpi/ic_launcher.png
> > #       new file:   gui-android/res/mipmap-mdpi/ic_launcher.png
> > #       new file:   gui-android/res/mipmap-xhdpi/ic_launcher.png
> > #       new file:   gui-android/res/mipmap-xxhdpi/ic_launcher.png
> > #       new file:   gui-android/res/mipmap-xxxhdpi/ic_launcher.png
> > #       new file:   lib/arm64-v8a/.keep
> > #       new file:   lib/armeabi-v7a/.keep
> > #       new file:   lib/x86/.keep
> > #       new file:   lib/x86_64/.keep
> >
> > those might not have made it onto my github before I was locked out by
> > the concept of passwords being obsoleted
> >
> > another thought, I will try to get to this, of having a separate
> > config file for android build paths with all the long toolchain names
> > would probably be nice

  reply	other threads:[~2022-01-29 16:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29 15:59 [9front] " Eli Cohen
2022-01-29 16:03 ` [9front] " Eli Cohen
2022-01-29 16:06   ` Eli Cohen [this message]
2022-01-30 15:11   ` ori
2022-01-31  2:02     ` Eli Cohen

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=CAHwi9bzTzBrcJRTgnRobHxXibV1cMJFOaAe3NysYoD6U8iVVsA@mail.gmail.com \
    --to=echoline@gmail.com \
    --cc=9front@9front.org \
    /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 NNTP newsgroup(s).