Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Frans de Jonge
    @Frenzie
    @ptrm @wangkaibule It looks like the same thing I mentioned in any case.
    Regarding the pointer size mismatch did you try the suggestion of -m32?
    Piotrek Marciniak
    @ptrm
    @Frenzie True, thought on some androids the menu disappears outside the whole screen
    And thanks for pointing to the makefile
    Martín Fernández
    @pazos
    On Android 6 there's currently some known slightly odd behavior that can be worked around by switching out of the program and back into it
    Ok, I will fix that
    But I can't reproduce the landscape issue...
    Martín Fernández
    @pazos
    The issue quoted happens from API 19 onwards.
    Piotrek Marciniak
    @ptrm
    @Frenzie when adding HOST_CC="gcc -m32" to the block you pointed to in Makefile.defs, nothing happens, added to C(XX)FLAGS suggests -mbe32: arm-linux-gnueabihf-gcc: error: unrecognized command line option ‘-m32’; did you mean ‘-mbe32’?. So I either g9t the wrong 0ackage for cross compiler, or misplace tue flag still
    *HOST_CC:=...
    Piotrek Marciniak
    @ptrm
    https://stackoverflow.com/questions/32658310/how-to-cross-compile-application-for-32-bit-arm-architecture-on-amd64-system-usi#32658728 - while tuis SO answer suggests there are difgerent toolchains for 32 and 64 bit, and the compiler above does not need to be informed by parameters :D
    NiLuJe
    @NiLuJe
    @pazos: I think that's safe (it certainly works on my H2O). I remember having issues with fractional sleeps somewhere though, but I'll be damned if I can remember where ;).
    @ptrm: That -m32 assumes an x86_64 host, I'm not familiar with native aarch64 toolchains, but, basically, you'll need a multilib-aware one, and pass it the flag necessary for it to target aarch32
    And the host probably also needs to be able to run aarch32 binaries
    That, or bypass the whole mess and tweak the buildsystem to ask it to use a native, full luajit interpreter instead of building minilua
    I don't recall if that's the only part of the buildsystem where this sort of trickery is involved, though (I would think so, but you never know... :D)
    NiLuJe
    @NiLuJe
    The whole luarocks in the later stages comes to mind, as that's generally a giant mess pretty much everywhere ^^
    As is usually the case with cross-compiling mixed with PMS for interpreted languages (I'm looking at you, Python.)
    @pazos: If you need a giant-screen tester, I have a 1080x2280 screen here...
    On Pie
    Martín Fernández
    @pazos
    @NiLuJe: cool
    does your device handle multiwindows / split view ¿?
    NiLuJe
    @NiLuJe
    Hmm, is that a stock thing?
    Martín Fernández
    @pazos
    I guess but I'm not sure
    It is a thing added in API24 and the reason why we need to tweak max aspect ratio from time to time
    NiLuJe
    @NiLuJe
    The "hold on the thumbnail in recents view" thingy?
    Never used it, but apparently, that's a thing, yeah
    Well, it's in a three dots menu in the reents view now, but, yeah, it's there
    And it indeed does what it says on the tin, yay.
    Martín Fernández
    @pazos
    but you shouldn't be able to use KOReader in split view
    NiLuJe
    @NiLuJe
    That was with GMail ;p
    I never installed KOReader on that device ;)
    Martín Fernández
    @pazos
    lol, better for your mental health!
    NiLuJe
    @NiLuJe
    ^^
    Martín Fernández
    @pazos
    If you install current version you'll be able to reproduce the issues @wangkaibule mentioned.
    NiLuJe
    @NiLuJe
    Already got my hands in too many pies ;p
    Martín Fernández
    @pazos
    @pazos: I think that's safe (it certainly works on my H2O). I remember having issues with fractional sleeps somewhere though, but I'll be damned if I can remember where ;).
    If is safe on kobos and safe on Kindles I will make the change.
    NiLuJe
    @NiLuJe
    With a bit of luck, that was on something like FW 2.x on Kindle, so, eh.
    I'm suspiciously using usleep in my old Kindle stuff, so that may be it
    The K2 is flat, so, more on that later ;)
    One could awlays use usleep if it's there and sleep otherwise, that'd make everything happy ;)
    Martín Fernández
    @pazos
    usleep 500000 || sleep 0.5 ?
    fine for me
    NiLuJe
    @NiLuJe
    Yeah, fractional sleep is an optional busybox feature, while usleep is an "all or nothing" applet
    So that'd make the most sense, compatibility-wise ;)
    Martín Fernández
    @pazos
    ok, since it is called recursively I would go for usleep 500000 2>/dev/null || sleep 0.5
    NiLuJe
    @NiLuJe
    Yup