Which Android does your phone have? 12+? Not running with no reason sounds
a lot like the problem that was reported in discord caused by the missing
section.
On Tue, 26 Dec 2023 at 13:42, James Paige wrote:
> Arg, I am so close. I can build the debug apk now with no errors, and it
> seems
Arg, I am so close. I can build the debug apk now with no errors, and it
seems okay, but when I try to install it on my phone it won't run (and
gives me no hint as to why)
Maybe something is failing, but the build keeps going instead of stopping.
I'll figure it out eventually.
> Great... maybe.
Great... maybe. Is this a good time to bring up emscripten nightly builds?
:)
"Source option 5" means -source 1.5 meaning JDK 1.5 which is Java 5. My
distro, Slackware, doesn't have an official JDK package (rather telling,
since it includes toolchains for every other popular language) but there's
I have no idea how I managed to get platform version 31 installed in my
2012 Android SDK *shrug*
I also ran into a "Source option 5 is no longer supported." openjdk8 was
the last java to support whatever "option 5" means. And Debian 9 was the
last debian to support openjdk8
After a lot of messing
What do you actually need the "android" binary for, aside from installing
the SDK? In build.sh I only see one use:
[ -e project/local.properties ] || {
android update project -p project || exit 1
rm -f project/src/Globals.java
}
And I notice that block was modified in 4701548e0 ("SDL:
Well, you don't want the SDK that I have, because it no longer works!
Running "android" (a binary from 2018) I get Android SDK Manager revision
25.2.5 which shows the most recent "SDK Platform" available for install
being one for Android API 29 (Android 10). Which is the one I have
installed. I
TMC, Question! What version of the Android SDK do you have installed?
I think my version is probably from around 2012, and it is so old I don't
even know how to install it again (which makes it rough to create a Docker
image for it)
I tried with the latest SDK, but it doesn't even have the
Oh, I am pretty sure I know what is wrong. The nightly build vm for android
is still Debian 9. It has scons version 2.3, which is still python 2.7
based. The latest scons on my Debian 11 box is 4.0
On Tue, Dec 19, 2023 at 9:13 PM James Paige wrote:
>
>
> On Sat, Dec 16, 2023 at 7:40 PM Ralph
On Sat, Dec 16, 2023 at 7:40 PM Ralph Versteegen via Ohrrpgce <
ohrrpgce@lists.motherhamster.org> wrote:
> That's strange... works on my machine. The error is:
>
> jni/../jni/application/ohrrpgce/tmp//filelayer.cpp:7:24: fatal error:
> fb/fb_stub.h: No such file or directory
> #include
On Sun, 17 Dec 2023 at 13:39, Ralph Versteegen wrote:
> That's strange... works on my machine. The error is:
>
> jni/../jni/application/ohrrpgce/tmp//filelayer.cpp:7:24: fatal error:
> fb/fb_stub.h: No such file or directory
> #include "fb/fb_stub.h"
> ^
>
> And the
That's strange... works on my machine. The error is:
jni/../jni/application/ohrrpgce/tmp//filelayer.cpp:7:24: fatal error:
fb/fb_stub.h: No such file or directory
#include "fb/fb_stub.h"
^
And the reason for the error is that copy_source_actions() in ohrbuild.py
isn't
I forgot to mention, the android builds have been broken for a while (Since
October 27)
I haven't had time to narrow it down to the exact revision yet, but I'll
work on it when I have time.
I also want to work on the Android 12 fix, (I know what to do) and the .aab
format (Don't know what to do
I found RTLD_NOLOAD in the headers for android-21 (Android 5.0) but not
android-19, but I guess it's not available because of our low
minSdkVersion. Anyway, it's not needed at all on Android so I got rid of it
there.
While that fixed the Android libapplication.so compile, I'm not actually
able to
The android build VM was broken, but after I fixed it, looks like it is
still having trouble compiling recently nightlyies
ni/../jni/application/ohrrpgce/tmp//os_unix.c: In function 'dylib_noload':
jni/../jni/application/ohrrpgce/tmp//os_unix.c:237:42: error: 'RTLD_NOLOAD'
undeclared (first use
Oops. Probably because datafiles.c is generate under build/ so doesn't
get symlinked into android/tmp.
On Sun, 31 Oct 2021 at 12:40, James Paige wrote:
>
> Oh! I just noticed that the android build is broken. it fails with:
>
> jni/../jni/application/ohrrpgce/tmp//filelayer.cpp:702: error:
Oh! I just noticed that the android build is broken. it fails with:
jni/../jni/application/ohrrpgce/tmp//filelayer.cpp:702: error: undefined
reference to 'embedded_files_table'
collect2: error: ld returned 1 exit status
/home/james/misc/android-ndk-r12b/build/core/build-binary.mk:677: recipe
for
I know that there were other reasons to use a newer NDK, but I don't
remember what they are. I'm not bothered by it right now. A newer NDK
would also increase our min supported Android version, I think? But I
had to actually look up what it was (Android 2.3), because I'd
forgotten. It wouldn't be
Ah, I see. Is it worth us try to switch to a newer NDK?
I also just noticed that the 64 but linux builds have been failing since
last Wednesday. They say:
slices.bas(1788) error 97: Ambiguous call to overloaded function, LARGE()
in 'out_surf = surface_scale(in_surf, large(1, spr->w * .zoom),
Oh, that's not hard to fix.
But I notice that the versions of GCC used in the NDK versions you and
I are using don't support C++11 designated initializer syntax; we use
a GCC extension syntax instead. So it's not a C++11-compliant
compiler, a nuisance.
On Mon, 11 Mar 2019 at 07:15, James Paige
For the past week the Android build has been broken as a consequence of me
finally checking in the change to increase minSdkVersion without alos
installing the needed SDK package on the nightly build machine.
However, when I went to fix that today I realized there is a new build
failure on
It looks like one of the Surface related changes yesterday broke the
Android build.
My attempts to copy-paste the relevant error on my phone were met with
frustration ;P
See the cron mail
___
Ohrrpgce mailing list
ohrrpgce@lists.motherhamster.org
21 matches
Mail list logo
