Building Gideros

MoKaLux

FYI: Qt asked me to update so I did and now C:\Qt6\Tools\mingw900_64 folder has only the share folder in it, all the rest is gone
I have a working folder C:\Qt6\Tools\mingw1120_64 with everything in it.

I couldn't build gideros anymore so I changed Makefile.def to this:

QTBASEDIR=/c/Qt6 MAKEJOBS=-j8   QT_ARCH=mingw_64 #QT_TOOLSARCH=mingw900_64 QT_TOOLSARCH=mingw1120_64 QTVER=6.2.2 QT5ICUVER=54

And now I can build gideros again

Please note that Qt 6.2.3 (which is LTS) should work too (see hito9 post on Linux build), you just need to write QTVER=6.2.3 (and maybe QT5ICUVER=56).

Viva Gideros </b>

SinisterSoft

Can you update the wiki?

MoKaLux

MoKaLux said:

I had another idea, if we have already working export for all the platforms with the official release, then we don't need to do it!?
We copy templates from original installed gideros and put them in our gideros templates? sounds too easy!
EDIT: tested and that works! (tested with html export). The problem is I think we need to build new templates if we make changes to them?

So I built latest gideros but only for windows:

#QTBASEDIR=/c/Applications/Qt QTBASEDIR=/c/Qt6 MAKEJOBS=-j8   QT_ARCH=mingw_64 #QT_TOOLSARCH=mingw900_64 QT_TOOLSARCH=mingw1120_64 QTVER=6.2.2 QT5ICUVER=54

and as in the quote I simply had to copy the win32, html5, ... templates from the original gideros to my build and that works (tested with html5, win32, not working for android export for now).

I am learning Qt and c++ with gideros

EDIT: you can see my build working for html5 https://mokatunprod.itch.io/gideros-tests
EDIT2: @SinisterSoft the wiki describes the steps I take on my windows 10 machine, tested today but only the win part not all the platforms.

Viva Gideros

SinisterSoft

All the plugins are built at the same time as the editor, no?

MoKaLux

SinisterSoft said:

All the plugins are built at the same time as the editor, no?

EDIT: I meant not the platforms

yes but you have to install their sdk on your computer (steam sdk, android, emscripten, ...) and set up their path in Makefile.def. I tried with a couple of them but couldn't compile them correctly

MoKaLux

hgy29 said:

@MoKaLux, to build Gideros for win32, you don’t need any external tool beside MinGW64 environment. I have updated the wiki with the new list of packages needed for MinGW64. And yes, win32 has nothing to do with QT or UWP.

What I tried:
$ pacman -S mingw-w64-i686-toolchain
:: There are 19 members in group mingw-w64-i686-toolchain:
:: Repository mingw32

I installed most of them and some had the error:
error: failed to commit transaction (invalid or corrupted package)
but I believe they are for other os than windows with extension .pkg.tar.zst

Building Gideros OK
make -f scripts/Makefile.gid prep.repo
make -f scripts/Makefile.gid qscintilla
make -f scripts/Makefile.gid qlexilla
make -f scripts/Makefile.gid versioning

make –f scripts/Makefile.gid qtapp.install

Everything work and I have my Gideros Studio. Inside gideros I try to export to win32 but I got "template is missing"

So I run:
$ make -f scripts/Makefile.gid win32.install

and I have these errors:
/bin/sh: line 1: /c/msys64/mingw32/bin/gcc: No such file or directory
make[1]: *** [/c/dev/gideros_hgy29/scripts//GidWin32.mk:81: win32_example/build/libgvfs/findfp.o] Error 127
/bin/sh: line 1: /c/msys64/mingw32/bin/g++: No such file or directory

My makefile.def:

#QTBASEDIR=/c/Applications/Qt QTBASEDIR=/c/Qt6 MAKEJOBS=-j8   #WIN32_BIN=/mingw32/bin #C:\msys64\mingw32\bin WIN32_BIN=/c/msys64/mingw32/bin export WIN32_BIN   QT_ARCH=mingw_64 #QT_TOOLSARCH=mingw900_64 QT_TOOLSARCH=mingw1120_64 QTVER=6.2.2 QT5ICUVER=54

and effectively there are no gcc nor g++ in my bin folder:


Somebody any idea? Thank you

hgy29

No you don’t need qt things, but you should have gcc installed by the toolchain package. Maybe that was the one in error ? You could try to update your Mingw pacman repository or they keys if that’s what is failing

hgy29

If your MINGW install is a bit old, you may hit a key issue described here https://www.msys2.org/news/#2020-06-29-new-packagers and also https://github.com/msys2/MSYS2-packages/issues/2343.
I just had this issue on my home PC, and I solved it by:
- editing /etc/pacman.conf and changing the SigLevel to Never (there was one line to uncomment and the line below to comment)
- running pacman -S msys2-keyring
- reverting the changes to pacman.conf
- running pacman -Sy to update the database

And then pacman was happy about the keys and packages

BTW, libpng package is no longer necessary

EDIT: I have update my repo, it wouldn't build from a clean repo

MoKaLux

yes that was a signature issue https://www.msys2.org/news/#2020-06-29-new-packagers, to fix it I did:
rm -r /etc/pacman.d/gnupg/
pacman-key --init
pacman-key --populate msys2

and I redid:
pacman -Syu
pacman -S mingw-w64-i686-toolchain (download ALL)
pacman -S mingw-w64-i686-glew
pacman -S mingw-w64-i686-curl
pacman -S mingw-w64-i686-libpng

and that almost worked

Thank you for updating your repo, I will get it and try again and I think that will work

MoKaLux

that almost worked


I think I need to redo those again because I had some errors?
pacman -S mingw-w64-i686-toolchain

Thank you very much hgy29 for the help you provided, much appreciated
I will try to understand those .dlls issues
EDIT: looks like a curl thing, back to pacman again
EDIT2: I found them in my msys64/mingw32/bin folder and copied them over to the exported win32 app and this is working but I had a little surprise

VIVA GIDEROS

hgy29

That’s a ssl thing, I guess it worked for me because I had them installed already. They are the same as for qt ssl (win32 OpenSSL build)

MoKaLux

@hgy29 we cross-posted, please see updated post above
I will update the wiki asap...DONE