<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 19, 2022 at 11:02 AM James Abernathy <<a href="mailto:jfabernathy@gmail.com">jfabernathy@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 19, 2022 at 9:33 AM Peter Bennett <<a href="mailto:pb.mythtv@gmail.com" target="_blank">pb.mythtv@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p><br>
</p>
<div>On 8/18/22 16:11, James Abernathy
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Aug 18, 2022 at 3:57
PM Peter Bennett <<a href="mailto:pb.mythtv@gmail.com" target="_blank">pb.mythtv@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
On 8/17/22 16:15, James Abernathy wrote:<br>
> So I was testing out the updated Readme.md at <br>
> <a href="https://github.com/MythTV/packaging/tree/master/android" rel="noreferrer" target="_blank">https://github.com/MythTV/packaging/tree/master/android</a><br>
> by building a KVM VM using Ubuntu 20.04 and the
instructions including <br>
> the dependencies worked as documented. So I thought I'd
see if this <br>
> held true on Ubuntu 22.04. Well it did not. After I
built the VM <br>
> using Ubuntu 22.04 I followed the Readme.md again and
it failed <br>
> building the libs and the error seemed to indicate it
could not find <br>
> the command 'pkg-config'.<br>
><br>
> I checked the 20.04 VM and it had the command
pkg-config but 22.04 <br>
> didn't. I did sudo apt install pkg-config on the 22.04
VM and then <br>
> the libs were built. However, when I tried to build
the apk, I got an <br>
> error about not finding 'libmariadb.so'.<br>
><br>
> This made no sense to me. Anyone have any ideas?
Obviously, I could <br>
> update the Readme.md to say Ubuntu 20.04 only, but that
would seem odd.<br>
><br>
> Jim A<br>
><br>
><br>
> _______________________________________________<br>
<br>
I have built on 22.04 ever since I upgraded to 22.04 a
couple of months <br>
ago. I have not had any problems, although I did build the
libs on 20.04 <br>
and continued using the same ones on 22.04. Are you building
fixes/32 or <br>
master?<br>
<br>
Peter<br>
<br>
</blockquote>
<div><br>
</div>
<div>I think there must be something different about having
20.04 working and then upgrading in place to 22.04. I may
do an experiment if I have time. I'm doing fixes/32 only
when testing 22.04. </div>
<div><br>
</div>
<div>After I had 20.04 production arm and arm64 apks for
fixes/32, I did try master just to see since I have a master
FE/BE combo testing system working fine on Master, but while
libs built, apks failed hard and early. I didn't even try
to figure out what was missing. </div>
<div><br>
</div>
<div>Both the 20.04 and 22.04 android builder systems were
just VMs so they were fresh systems with just what it took
to run the android builds. My new Readme.md was
strictly 20.04, fresh VM and it's repeatable. Since I can
build a 20.04 VM as easily as 22.04, I really don't care,
but someone will try 22.04 naturally and it will fail. If I
could identify the problem that would be good to note the
changes, but otherwise I may want a 20.04 only warning in
the readme.<br>
</div>
<div><br>
</div>
<div>Jim A</div>
<div><br>
</div>
</div>
</div>
<br>
</blockquote>
<p>FWIW I never upgrade an operating system version in place. My
22.04 is a fresh install. After install I moved important stuff,
like the development libraries and android directory to the new
home directory of 22.04.</p>
<p>Peter</p></div></blockquote><div><br></div><div>I found where the build-tools 29.0.2 is coming from. In the directory workdir/packaging/android/android-utilities is a file called setenv.sh and there is some logic in there that hardcodes the version if a test fails:</div><div><br></div>ANDROID_ROOT=$HOME/Android<br>ANDROID_ROOT=`readlink -f "$ANDROID_ROOT"`<br>export ANDROID_SDK=$ANDROID_ROOT/Sdk<br>export ANDROID_NDK=$ANDROID_ROOT/android-ndk<br>export ANDROID_SDK_ROOT=$ANDROID_SDK<br>export ANDROID_NDK_ROOT=$ANDROID_NDK<br>if [ $(ls -1 "$ANDROID_SDK_ROOT/build-tools" | wc -l) == 1 ] ; then<br> export ANDROID_BUILD_TOOLS_REVISION=$(ls -1 $ANDROID_SDK_ROOT/build-tools | grep "^[0-9]" | tail -1)<br> echo "Using discovered tools version $ANDROID_BUILD_TOOLS_REVISION"<br>else<br> export ANDROID_BUILD_TOOLS_REVISION=29.0.2<br><div>echo "Using hardcoded tools version $ANDROID_BUILD_TOOLS_REVISION"</div></div></div></blockquote><div><br></div><div>Also during the apk build is when the build-tools 28.0.3 get installed, but don't appear to be accessed.</div><div><br></div><div>Jim A</div><div> </div></div></div>