Thanks, it seems to work, build is still running since almost 1h.
Now, i have a question.
In your setup_cross_compilation_env.sh you commented update_mingw_cross_env.
If i create my "own" mxe, from mosu version, in wich i include your modifications, put it on github, and in update_mingw_cross_env i link to it instead of mosu version, will it work in that case if i uncomment update_mingw_cross_env ?
The idea is to eventualy get mxe update mosu would make, without redoing the whole process of including your changes from a clean mxe clone, as it takes me more than 2h to build the whole toolchain from scratch.
Why did you switch the host name ?
Usualy i686 is for 32bits and x86_64 for 64bits...
Confirmed, it's switched, with Architecture=64 it builds a 32bits version.
+ Reply to Thread
Results 211 to 217 of 217
Last edited by jpsdr; 7th Feb 2024 at 15:23.
Yes, that should work. In fact you wouldn't even need to use my modified setup_cross_compilation_env.sh script because you would be updating from a repository with the correct source which wouldn't risk overwriting custom files locally.
The switch is a mistake on my part. Sorry about that.PB
Thanks again for your work and help.
I'm trying small step at a time.
Now, next eventualy step, out of curiosity, is building qtbase-everywhere-src-6.6.1.tar.xz difficult ?
If not to much (but everything is relative... ), where can i find how to build it (with the W7 patches) ?
Download the qtbase archive from official source.
The patches from https://github.com/crystalidea/qt6windows7 are stored in the correct folder structure used in the qtbase-everywhere-src-6.6.1.tar.xz archive.
So the simplest way would probably be to use a good archiver to open the qtbase archive and drag the patch folder(s) to the correct location in the archive and drop, overwriting the current files. The archive will be updated with the replacement files.
Then you can get the checksum for the new archive with this command:
cksum -a sha256 qtbase-everywhere-src-6.6.1.tar.xzPB
I thought you have to build thing. Didn't opened the qtbase-everywhere-src-6.6.1.tar.xz, so i thouht i was a build, didn't realised it was "just" the sources.
So... if for exemple there is an officiel 6.6.2 release, and qt6Windows7 update to this 6.6.2.
I just have to :
- Get official qtbase-everywhere-src-6.6.2.tar.xz
- Unpack it.
- copy the qtbase folder of qt6Windows7 in the official release.
- recreate the qtbase-everywhere-src-6.6.2.tar.xz file.
- Edit the qt6-qtbase.mk file to change just the version and the checksum, or just the checksum if eventualy mosu allready updated the version.
And that's all ?
You have it correct. That is the core of this simplified method; have mxe build modified qt6. Much better than the method I started with.PB
So, if i understand properly, in fact the idea is to "trick" mxe with another qtbase file, making it believed it allready downloaded the file.
I think this is indeed the best and very simple method, good one, thanks.