Gideros 2023.8 Released

hgy29

This new Gideros release comes with Linux support, that means:
- Gideros Studio is now available for Linux
- Gideros Studio can now export to Linux (through QT)
- Gideros Studio can also, and this is great, export to Linux without QT

When I say Linux, it was actually tested on Debian 11, Debian 12 and Ubuntu 22.04. I am confident it should work on any Linux based on Debian.

Full list of changes:
New features

[platform] Now available on Debian based Linux (tested on Debian 11, Debian 12 and Ubuntu 22-04)
[export/linux] Initial non QT linux export code
[export] Add QT Linux target

Improvements

[export] Note about QT licensing
[plugin/rp3d] add Body:setSprite() so that rp3d can update Sprites after each physics simulation step
[addon] Scene builder: allow specifying asset folder and support capsule physics shapes
[Addon/SceneBuilder] Support GLTF files
[addon/scenebuilder] Support setting physics shape in library
[lib/3d] Improve GSCN handling

Fixes

[gfx/rt] Fix non POT option not accepted
[gfx/sprite] Fix invalid bound caching
[gfx/shape] Fix crash when omitting matrix in setFillType
[core/Buffer] keep a reference to the buffer object while opened as a file
[studio] Ensure output window shows last lines of 'print'
[export/win32] Avoid key repeating
[export/win32] backport linux http fixes to win32 code
[plugin/rp3d] Fix crash on some android
[plugin/ads] Add consent API
[plugin/ads/AdMob] Implement google consent flow
[Library/3d] Fix gltf loader and anim
[Samples] Fix controller demo


Download it from here:
http://giderosmobile.com/download

keszegh

Linux export option is amazing, will test

keszegh

does Linux export support the plugins?

hgy29

keszegh said:

does Linux export support the plugins?

Yes, but not every plugin. So far only platform independant plugins have been ported to Linux.

keszegh

hgy29 said:

keszegh said:

does Linux export support the plugins?

Yes, but not every plugin. So far only platform independant plugins have been ported to Linux.

sound good at first.

hgy29

A few core features not yet supported on Linux export:
- Native dialogs: TextInputDialog, AlertDialog and file/folders pickers aren't implemented
- Screen API not available either

MoKaLux

AWESOME BUILD captain hgy29
I get so excited with every new Gideros release
I cannot thank you enough sir

[studio] Ensure output window shows last lines of 'print'

kinrpg

Isso. Viva \o/
Linux APP export is here

hgy29

Linux Giderians: please test on your platforms and report your success or failure on the forum!

kinrpg

Hello, I'm testing the linux version and in all projects it is accusing the error "Malformed number" not only in the function shown in the attached image but in all that do not use integers.

hgy29

Hi @kinrpg you may need to set environment variable LC_ALL=C if your decimal point isn’t the dot

hgy29

By the way @kinrpg I am already pleased to see you managed to launch it

kinrpg

hgy29 said:

Hi @kinrpg you may need to set environment variable LC_ALL=C if your decimal point isn’t the dot

It makes sense, in my language (Brazilian Portuguese), the decimal point is the comma ",".

Taking the opportunity, I ran a program loading texture etc, using only integer numbers and both Studio and Player worked correctly and loaded the program on the screen.

OS -> Zorin OS 16.3 (Ubuntu based).

keszegh

let's discuss linux related things at https://forum.giderosmobile.com/discussion/8700/the-linux-thread#latest

keszegh

hgy29 said:

Hi @kinrpg you may need to set environment variable LC_ALL=C if your decimal point isn’t the dot

where/how to do that? i've run into the same issue too.

hgy29

keszegh said:

hgy29 said:

Hi @kinrpg you may need to set environment variable LC_ALL=C if your decimal point isn’t the dot

where/how to do that? i've run into the same issue too.

The best would be to add it to the Gideros Studio.sh file. There is already a export LD_LIBRARY_PATH=; inside it, just add another `export LC_ALL=C;`at the beginning and that should do the trick.

keszegh

hgy29 said:

keszegh said:

hgy29 said:

Hi @kinrpg you may need to set environment variable LC_ALL=C if your decimal point isn’t the dot

where/how to do that? i've run into the same issue too.

The best would be to add it to the Gideros Studio.sh file. There is already a export LD_LIBRARY_PATH=; inside it, just add another `export LC_ALL=C;`at the beginning and that should do the trick.

this worked.

keszegh

Which new mac export is the same as the old ones?

hgy29

keszegh said:

Which new mac export is the same as the old ones?

Apple export (non QT Mac export) is the same as before, but ‘Mac Desktop’ (QT) was merged with windows desktop in a more explicit QT export

keszegh

i think i never knew there is an 'apple mac' export option before, i thought that is only for ios. so can i assume that it supports most things? (as i don't have a mac to test my exports)

hgy29

Yes it supports most usual stuff, but not screens, file dialogs or application set/get API. It is basically an iOS export adapted to macOS. I suppose it can be expanded if one need so.

keszegh

trying to run qt linux export gives this error:
"error while loading shared libraries: libQt6DBus.so.6: cannot open shared object file: No such file or directory"

keszegh

hgy29 said:

Yes it supports most usual stuff, but not screens, file dialogs or application set/get API. It is basically an iOS export adapted to macOS. I suppose it can be expanded if one need so.

thanks for explaining

hgy29

keszegh said:

trying to run qt linux export gives this error:
"error while loading shared libraries: libQt6DBus.so.6: cannot open shared object file: No such file or directory"

You’ll need to set LD_LIBRARY_PATH to the directory containing the files, similarly to what is done by Gideros Studio.sh file

keszegh

hgy29 said:

keszegh said:

trying to run qt linux export gives this error:
"error while loading shared libraries: libQt6DBus.so.6: cannot open shared object file: No such file or directory"

You’ll need to set LD_LIBRARY_PATH to the directory containing the files, similarly to what is done by Gideros Studio.sh file

i've made such an .sh file and run it but then i got:
"error while loading shared libraries: libb2.so.1: cannot open shared object file: No such file or directory"

hgy29

keszegh said:

hgy29 said:

keszegh said:

trying to run qt linux export gives this error:
"error while loading shared libraries: libQt6DBus.so.6: cannot open shared object file: No such file or directory"

You’ll need to set LD_LIBRARY_PATH to the directory containing the files, similarly to what is done by Gideros Studio.sh file

i've made such an .sh file and run it but then i got:
"error while loading shared libraries: libb2.so.1: cannot open shared object file: No such file or directory"

Thanks, I’ll fix that. I included them in studio distribution but forgot on exported project.

kinrpg

YEAH Linux Guys ^_^

MoKaLux

Viva Gideros Linux

SimplesApps

Hi giderians,

I'm trying to export projects with Gideros Studio (2023.8 and previous) to Android using macOS Ventura and I'm stuck with the following error:

QIODevice::read (QProcess): device not open
QIODevice::read (QProcess): device not open

Going through and testing every instruction in the entire "APK.gexport" file for a few days I found the code snippet that causes the error:

"



bash
gradlew
[[[local.gradleTarget]]]
[[[local.gradleExtra]]]


"

I've tested everything I've found: changing the default shell to bash, changing Gideros Studio permissions, gradlew, etc., calling it with "./gradlew", using a shell script instead of the bash call, too I gave it Terminal and Gideros Full Disk Access, etc, etc. but nothing made it work.

I assume this was due to the way permissions are managed in the macOS Ventura.

Please could someone check it?

Thx,
David.

hgy29

Hi @SimplesApps, does it work if you export android project without building it from Gideros, I mean untick build apk/aab and open it with android studio ?

SimplesApps

Hi @hgy29, I've tried it and it works!

So I guess something has to be modified in the Gideros exporter for it to work directly from there.

Although with Android Studio I can now build it.

Thank you!