Android error in my first 64-bit test in fpcupdeluxe on Windows
lazarus / 43-Android

----------------------------------------------------------------------
ADiV · 2019-08-02 11:54

Hello, I have been testing with fpcupdeluxe and arm64-v8a a simple
test program, with only one button in the center and said program
closes without even showing said button. What is happening?

It is installed correctly in the emulator, try "Clean and build ..."
with the same result.

----------------------------------------------------------------------
tetrastes · 2019-08-02 13:56

As I see on picture, you built shared object library, not executable.

----------------------------------------------------------------------
jmpessoa · 2019-08-02 16:01

Hi, TR3E2

Please,  test it into a real 64 bits device!!!

----------------------------------------------------------------------
Thaddy · 2019-08-02 16:09

Or run the emulator on a 64 bit system?

----------------------------------------------------------------------
ADiV · 2019-08-02 16:16

Quote from: Thaddy on August 02, 2019, 06:09:29 pmOr run the emulator
on a 64 bit system?

I tried a fpcupdeluxe compilation with the last [Trunk] versions and
got the same result.

The emulator is running on a Win64, apparently fpcupdeluxe does not
work well if the last [Trunk] versions are installed. I am now testing
with the Fpc fixes3.2 and Lazarus fixes2.0 versions and if an apk
"arm64-v8a" works.

----------------------------------------------------------------------
Thaddy · 2019-08-02 16:45

Mentioning trunk without mentioning the revision is, frankly, useless.
It should be forbidden and shows little understanding what trunk
really is. < grumpy mode on:      >

If you are brave enough to try trunk, be brave enough to always add
the revision number.
Example, when I compile, the revision is always included. Actually
fpcdeluxe could do something similar:
Code: Bash  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i $ fpc
-vFree Pascal Compiler version 3.3.1-r42554 [2019/08/01] for arm
Done with passing REVINC=force and REVSTR=42554 or from the svn
-revision output

----------------------------------------------------------------------
ADiV · 2019-08-02 16:59

Quote from: Thaddy on August 02, 2019, 06:45:19 pmMentioning trunk
without mentioning the revision is, frankly, useless.
It should be forbidden and shows little understanding what trunk
really is. < grumpy mode on:      >
The latest version tested today.

----------------------------------------------------------------------
Thaddy · 2019-08-02 17:08

That's not a revision number. You have to understand these can change
any second. These are essential. r42554 is the revision I used in my
example. At the moment of writing it is r42566

Both these revisions are from today and can - often do! - differ
greatly in functionality. If you do not understand that stick with at
most 3.2.0-fixes.

Examples a plenty:
https://wiki.freepascal.org/User_Changes_3.0.4
https://wiki.freepascal.org/User_Changes_3.2
https://wiki.freepascal.org/FPC_New_Features_Trunk

All of these are often single commits, so can break your existing code
in seconds. Always give the revision number when using trunk. That is
sound advice.

----------------------------------------------------------------------
ADiV · 2019-08-02 17:22

Ok, I will do that. I keep the 3.2fixed. Thanks so much for the
explanation.

----------------------------------------------------------------------
Thaddy · 2019-08-02 17:27

Good. That is also your only guarantee, because features may also be
removed again from trunk, but never from a release    And yes, that
happens.