This is a multi-part message in MIME format. --------------7jN00w3fw0xcTjHBiVtv6sqn Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit ah, just to clarify one (major) point. What I am sharing in github is "just" the application file I see in the build-linux-64 directory (called "memory"). Is it correct or should I share the whole folder instead? Umberto On 5/2/24 17:58, Umberto Minora wrote: > > Thank you KC! :) > > Actually, a friend of mine told me he had to install something to make > it run. > > So I tried to download the executable from a linux machine different > from the one I used for the deployment, and found out I still have to > solve one issue. > > You can find it here: > https://github.com/umbe1987/memory/releases/tag/v0.1.0 (it's the file > called "memory" with no extension). > > The error I receive when trying to launch the game from the terminal is: > > ``` > > ./memory: error while loading shared libraries: libQt5Multimedia.so.5: > cannot open shared object file: No such file or directory > > ``` > > So, I think I might have made a mistake somewhere in the deployment > process, because what I wanted in the end was a single executable file > where all the needed libraries are bundled. Is this possible? If not, > how should I ship the final product so that the users will be able to > get and have it working without installing anything else? > > If I need to attach anything please let me know, I have already > attached my sysroot.toml and the ptd in the previous message. > > Thank you and hopefully I will be able to close this thread once and > for all anytime soon :) > > Umberto > > > On 5/1/24 09:49, Kaiser Chief wrote: >> Congratulations! >> >> The debugging paid off, >> >> This email thread might actually give us the keys to understand why >> the process was painful and how to improve it moving forward. >> >> It looks like some of the issues where bugs inherent to Qt or >> dependencies (hard to treat), but some others were configuration >> issues (easier to handle). >> >> Wishing you fun on your Android journey now! >> >> Best regards, >> >> KC >> >> On Tue, 30 Apr 2024, 21:56 umbertofilippo, >> wrote: >> >> As promised, here is: >> >> 1) the link to the linux release: >> https://github.com/umbe1987/memory/releases/tag/v0.1.0 >> >> 2) Instructions if you need: >> https://github.com/umbe1987/memory/blob/main/README.md >> >> 3) sysroot.toml and pdt (attached) >> >> >> Umberto >> >> >> On 4/30/24 20:55, Umberto Minora wrote: >>> Turns out I am dumb :/ >>> >>> Project built successfully!!!!!! >>> >>> I started from scratch. >>> Checked my sysroot.toml file and made sure I had multimedia in >>> pyqt and qt sessions. >>> Run pyqtdeploy-sysroot to create the sysroot dir (with the >>> caveat mentioned here >>> https://forum.qt.io/topic/136672/error-installing-qt-everywhere-src-5-15-2-on-ubuntu-22-04/2). >>> Took some attempts and a lot of time, as expected. >>> Created the pdt project. Built with pyqtdeploy-build, qmake and >>> make, and voilà! >>> >>> Everything went so smooth I couldn't believe it :) >>> >>> The issue I had is I has messed up the steps, configured the >>> sysroot improperly and probably I was using the sysroot folder >>> of pyqt-demo. >>> >>> I am thankful to all the feedback I have received in this mail >>> thread. >>> >>> Next step: build for android (wish me luck;) >>> >>> Ah and btw I will attach my sysroot and pdt files asap (typing >>> from my phone now). I will also add the Linux executable on my >>> repo as git release and link to it if you're curious. >>> >>> Thanks!!! >>> >>> Umberto >>> >>> Il 29 apr 2024 12:21, Umberto Minora >>> ha scritto: >>> >>> I am starting to wonder if I did something wrong in building >>> the sysroot. >>> >>> So far I have copied the one created for the pyqt-demo (if I >>> am not >>> mistaken) which I deployed successfully, and avoid >>> rebuilding it since >>> it was time consuming. >>> >>> But I am wondering if this has caused all my issues. Will >>> try to do it >>> as soon as I can and report back with my findings. >>> >>> Again, thanks for the feedback. >>> >>> Umberto >>> >>> On 4/26/24 17:30, Charles wrote: >>> > Actually for certain libraries like libssl, the dev >>> version usually >>> > provides a static library (.a) which should be fine with >>> > install_from_source = false, but AFAIK no OS provides a >>> static Qt >>> > library so Qt needs to be compiled from source. >>> >>> --------------7jN00w3fw0xcTjHBiVtv6sqn Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

ah, just to clarify one (major) point.

What I am sharing in github is "just" the application file I see in the build-linux-64 directory (called "memory").

Is it correct or should I share the whole folder instead?

Umberto

On 5/2/24 17:58, Umberto Minora wrote:

Thank you KC! :)

Actually, a friend of mine told me he had to install something to make it run.

So I tried to download the executable from a linux machine different from the one I used for the deployment, and found out I still have to solve one issue.

You can find it here: https://github.com/umbe1987/memory/releases/tag/v0.1.0 (it's the file called "memory" with no extension).

The error I receive when trying to launch the game from the terminal is:

```

./memory: error while loading shared libraries: libQt5Multimedia.so.5: cannot open shared object file: No such file or directory

```

So, I think I might have made a mistake somewhere in the deployment process, because what I wanted in the end was a single executable file where all the needed libraries are bundled. Is this possible? If not, how should I ship the final product so that the users will be able to get and have it working without installing anything else?

If I need to attach anything please let me know, I have already attached my sysroot.toml and the ptd in the previous message.

Thank you and hopefully I will be able to close this thread once and for all anytime soon :)

Umberto


On 5/1/24 09:49, Kaiser Chief wrote:
Congratulations!

The debugging paid off, 

This email thread might actually give us the keys to understand why the process was painful and how to improve it moving forward.

It looks like some of the issues where bugs inherent to Qt or dependencies (hard to treat), but some others were configuration issues (easier to handle). 

Wishing you fun on your Android journey now! 

Best regards, 

KC

On Tue, 30 Apr 2024, 21:56 umbertofilippo, <umbertofilippo@tiscali.it> wrote:

As promised, here is:

1) the link to the linux release: https://github.com/umbe1987/memory/releases/tag/v0.1.0

2) Instructions if you need: https://github.com/umbe1987/memory/blob/main/README.md

3) sysroot.toml and pdt (attached)


Umberto


On 4/30/24 20:55, Umberto Minora wrote:
Turns out I am dumb :/

Project built successfully!!!!!!

I started from scratch.
Checked my sysroot.toml file and made sure I had multimedia in pyqt and qt sessions.
Run pyqtdeploy-sysroot to create the sysroot dir (with the caveat mentioned here https://forum.qt.io/topic/136672/error-installing-qt-everywhere-src-5-15-2-on-ubuntu-22-04/2). Took some attempts and a lot of time, as expected.
Created the pdt project. Built with pyqtdeploy-build, qmake and make, and voilà!

Everything went so smooth I couldn't believe it :)

The issue I had is I has messed up the steps, configured the sysroot improperly and probably I was using the sysroot folder of pyqt-demo.

I am thankful to all the feedback I have received in this mail thread.

Next step: build for android (wish me luck;)

Ah and btw I will attach my sysroot and pdt files asap (typing from my phone now). I will also add the Linux executable on my repo as git release and link to it if you're curious.

Thanks!!!

Umberto

Il 29 apr 2024 12:21, Umberto Minora <umbertofilippo@tiscali.it> ha scritto:

I am starting to wonder if I did something wrong in building the sysroot.

So far I have copied the one created for the pyqt-demo (if I am not
mistaken) which I deployed successfully, and avoid rebuilding it since
it was time consuming.

But I am wondering if this has caused all my issues. Will try to do it
as soon as I can and report back with my findings.

Again, thanks for the feedback.

Umberto

On 4/26/24 17:30, Charles wrote:
> Actually for certain libraries like libssl, the dev version usually
> provides a static library (.a) which should be fine with
> install_from_source = false, but AFAIK no OS provides a static Qt
> library so Qt needs to be compiled from source.


--------------7jN00w3fw0xcTjHBiVtv6sqn--