SuperTuxKart porting

[Keneda]

@kugiigi said in SuperTuxKart porting:

@antidroid Yeah I understand, I just think that the people who can help you on this are the opposite, not active here but active in telegram

This is quite a pity because he is right, only forums give persistence to the writing, and easy search, for anybody, even non-logged.

[AntiDroid]

The reason I can not find the information is because the people that know prefer to communicate in ways that do not get preserved. I do not want to contribute to that issue and even if I did join and ask the question I wouldn't understand the answer well enough to then post it for others in a comprehensible way.

The funny thing is it only really increases the work load for those people because it makes it harder for others to contribute because they can not find the information they need so they give up leaving only a few core people doing all the work. Then everyone wonders why more people don't roll up their sleeves and get to work fixing bugs rather than complaining.

No matter what I will keep working away and contribute in anyway I can. It does not look like it will be porting apps anytime soon which sadly is one of the big things UT needs to get more users.

[kugiigi]

@antidroid Sorry, I did not intend to make this thread about forum vs chat
I was just giving my guess why you haven't receive any response yet.

To be fair, there are of course cons and pros for both forums and chats. They both have their purpose and there are people who thinks the opposite as your opinion. For some, going to forums is more effort than in live chat.

Anyway, hopefully you get responses here I would suggest directly contacting the developers of similar apps/games in the store though, even just via email. Then if you get valuable discussion then you can just post here those information.

[lduboeuf]

@antidroid Saw on Telegram @qiangong2 who was already fighting for building STK, don't where it landed, see https://github.com/Qiangong2/stk-code

[AntiDroid]

@kugiigi No worries and I do agree 100%. I Started by asking for help on Github in the STK code repo and it was only after a week without any response I reluctantly signed up here.

I am an old aspie and all this social stuff is not for me. I have an email account, github account and now this one. When involved with opensource hardware/software projects I've had accounts on those forums too until I get a new obsession and move on. But I have never had and never will have a facebook, twitter, instagram or other social media account.

Hell I had a feature phone until a few months ago and would still have one if there were any decent ones compatible with the networks where I live. I wanted an Ubuntu phone back when canonical had their crowd funding campaign but they were not available in my Country and the networks were not compatible to import one. I maintain 16 different Android devices for my kids and family (TV's, Tablets and Phones) and honestly I personally can't believe people voluntarily use them. When my last feature phone died and before I found a OPO to flash UT on I simply didn't have a phone. I know it sounds strange to most people but as an aspie everything is black and white, no grey area where I do things that do not make logical sense in my mind.

Sorry for the wall of text. Again an aspie thing, we do not tend to express ourselves concisely.

[AntiDroid]

@lduboeuf Thank you very much. He at least has a start there and maybe if I can get it to at least complain about compiling I can figure it out.

[AntiDroid]

UPDATE Feb 28, 2021

I am making progress. You can find the repo here

There are still some issues. Maybe one of the people here that actually know what they are doing can spot what I am doing wrong. I also have an open dialog with the STK developers in github.

Clickable Arm64 build

This one builds completely and creates a clickable. I tried installing it on my OnePlus 6T which is running a GSI from a few months ago. It is the only arm64 device I have and is not a stable device.

I get

Fatal error: /home/phablet/Downloads/supertuxkart_1.2.0-ubports_arm64.click fail
WARNING:root:signiture check failed, but installing anyway as requested
Cannot install /home/phablet/Downloads/supertuxkart_1.2.0-ubports_arm64.click F

There may be more to the message but UT_tweak tools output window does not wrap and has no side scroll I could find.

Clickable Armhf build

Armhf builds all the object files and only fails at the last step creating the executable which fails at

Linking CXX executable bin/supertuxkart
lib/angelscript/projects/cmake/libangelscript.a(as_callfunc.cpp.o): In function `CallSystemFunction(int, asCContext*)':
as_callfunc.cpp:(.text+0x1e4): undefined reference to `CallSystemFunctionNative(asCContext*, asCScriptFunction*, void*, unsigned long*, void*, unsigned long long&, void*)'

I get the feeling

as_callfunc.cpp.o

should be a call to

as_callfunc_arm.cpp.o

and that means it is not detecting the architecture correctly?? It appears to be related to Anglescript (Again https://github.com/supertuxkart/stk-code/issues/2411 https://github.com/supertuxkart/stk-code/pull/2195 https://github.com/supertuxkart/stk-code/issues/2569 and others) and compiling for arm. Again I am not sure how I would do this without modifying STKs code. I would rather do it from the clickable build files.

Clickable desktop build

I can build all the object files and even build an executable but it fails at the very end with.

Installing /home/Projects/stk/stk-code/ubuntu_touch/manifest.json
Installing /home/Projects/stk/stk-code/ubuntu_touch/supertuxkart.apparmor
Installing /home/Projects/stk/stk-code/ubuntu_touch/supertuxkart.desktop
Installing /home/Projects/stk/stk-code/ubuntu_touch/icon.png
Successfully built package in './supertuxkart_1.2.0-ubports_amd64.click'.
/home/Projects/stk/stk-code/ubuntu_touch/build/x86_64-linux-gnu/app/supertuxkart_1.2.0-ubports_amd64.click: pass
non-network local connections being added to access control list
Mounting device home to /home/.clickable/home
[error  ] FileManager: Could not find file 'supertuxkart.git'in any standard location (esp. ../data).
[error  ] FileManager: Last location checked '/./share/supertuxkart/data/'.
[fatal  ] FileManager: Set $SUPERTUXKART_DATADIR to point to the data directory.
Command exited with non-zero exit status 1, see above for details. This is most likely not a problem with Clickable.

The solution is here I think https://forum.freegamedev.net/viewtopic.php?f=18&t=7595 but I would like to implement it from the clickable build files rather than modifying anything in the STK code or having to do it manually but I have not figured that one out yet.

[AntiDroid]

This post is deleted!

[AntiDroid]

Alpha testing

---

I have successfully built an Arm64 click package of SuperTuxKart. I am unable to test it due to my only arm64 device thinking it is armhf.

From talking with the people over at STK it may work out of the box without any other changes since this version uses sdl2 to interface with the touchscreen and sensors. :crossed_fingers:

If you would like to test it out you can download it here.
https://github.com/Intrinsically-Sublime/stk-code/releases/tag/V1.2.0-alpha

Download it directly on the phone to the downloads directory.

Then from the command line.

cd ./Downloads
sudo pkcon install-local ./supertuxkart_1.2.0-ubports_arm64.click --allow-untrusted

I honestly do not know if it will do anything at all.

[lduboeuf]

@antidroid congrats for your successful build ;-). Don't have an arm64 too, so can't test, maybe announce it on Telegram ?

[kugiigi]

@lduboeuf I tested it on my Xperia X and it won't open
The error is

WARNING **: Unable to exec `supertuxkart` in `/opt/click.ubuntu.com/.click/users/phablet/supertuxkart`: No such file or directory

Looks like you're executing on the wrong directory. The binary is at /opt/click.ubuntu.com/supertuxkart/current/bin/ in the current installation.

[kugiigi]

@kugiigi I tried to manually execute the binary and gets the error below

error while loading shared libraries: libvorbisfile.so.3: cannot open shared object file: No such file or directory

[aarontheissueguy]

@antidroid
Here are my logs.
http://paste.ubuntu.com/p/79GpQcg54G/

[AntiDroid]

@kugiigi Thank you. I will look into this. I should probably build it with the debug flag enabled so we get a little more information.

Just so I understand. The click installed but fails to run or it fails to install?

EDIT: Reread your message and understand now

[AntiDroid]

@aarontheissueguy Thanks

[AntiDroid]

@kugiigi said in SuperTuxKart porting:

I tried to manually execute the binary and gets the error below

Where did you find the binary installed? Was it where it was supposed to be?

/opt/click.ubuntu.com/.click/users/phablet/supertuxkart

[kugiigi]

@antidroid Well it seems that click files are located in multiple directories, most likely just symlinks. First is at /opt/click.ubuntu.com/supertuxkart/current/bin but it also exists at /opt/click.ubuntu.com/.click/users/phablet/supertuxkart/bin. The latter seems to be the path used in the desktop files of click apps. I honestly have no idea where your app is wrong. I compared it to other working apps and it seems correct.

[abmyii]

@AntiDroid You need to package the required libraries in the click. This is how I do it for Neverball: https://gitlab.com/abmyii/neverball-touch/-/blob/master/clickable.json#L43-58

The method I use to identify them is just trial-and-error. I assume it runs on your device because you have the libraries already installed, whereas most devices don't have those libraries preinstalled.

@kugiigi What you could try is to use the libraries packaged with Neverball when running the game manually, since it should have most (if not all) of the required libraries. To do that, run:

export LD_LIBRARY_PATH=/opt/click.ubuntu.com/neverball.abmyii/current/lib/aarch64-linux-gnu:/opt/click.ubuntu.com/*.abmyii/current/lib/*

And then run SuperTuxKart manually as you did before.

[kugiigi]

@abmyii I tried that but now it's looking for libopenal.so.1

[abmyii]

@kugiigi If you are up for it, you can just manually download all the required libs until it works - there shouldn't be too many more TBH. The process is a bit finicky, but doable. I can explain how to, if you are interested.

Unfortunately I don't have an arm64 device, else I would have tried it myself.