From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/mediacodec_wrapper: get api level via NDK method
Date: Mon, 09 Jan 2023 17:44:53 +0100
Message-ID: <b84e94d87d3c639baca3b6dc3722390e1758b505.camel@haerdin.se> (raw)
In-Reply-To: <tencent_E4AEAE563851C001B568690E00B96B167F0A@qq.com>
mån 2023-01-09 klockan 22:41 +0800 skrev Zhao Zhili:
>
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> > Tomas Härdin
> > Sent: 2023年1月9日 20:32
> > To: FFmpeg development discussions and patches <
> > ffmpeg-devel@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/mediacodec_wrapper:
> > get api level via NDK method
> >
> > tis 2023-01-10 klockan 00:36 +0800 skrev Zhao Zhili:
> > > From: Zhao Zhili <zhilizhao@tencent.com>
> > >
> > > android_get_device_api_level() is a static inline method before
> > > API
> > > level 29. It was implemented via __system_property_get(). We can
> > > do
> > > the same thing, but I don't want to mess up with
> > > __system_property_get.
> >
> > The code tests on API >= 24 not 29. Or do you mean that
> > android_get_device_api_level() is available since 24 but not used
> > until
> > 29?
>
> If android_get_device_api_level() is a global symbol instead of
> inline method, I would
> use dlsym() instead to make it works on build target api level < 24
> and device/runtime
> api level >= 24.
Perhaps a comment would be appropriate here as well then. A lot of the
NDK vs JNI vs versions of either isn't entirely obvious
/Tomas
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2023-01-09 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 16:36 Zhao Zhili
2023-01-09 12:32 ` Tomas Härdin
2023-01-09 14:41 ` Zhao Zhili
2023-01-09 16:44 ` Tomas Härdin [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=b84e94d87d3c639baca3b6dc3722390e1758b505.camel@haerdin.se \
--to=git@haerdin.se \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git