Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix windeployqt #60

Closed
Martchus opened this issue Mar 17, 2018 · 0 comments
Closed

Fix windeployqt #60

Martchus opened this issue Mar 17, 2018 · 0 comments
Labels
bug

Comments

@Martchus
Copy link
Owner

Currently windeployqt provided by the mingw-w64-qt5-tools package tries to parse the Windows binaries as ELF files instead of PE.

This is because my mkspec is called mingw-w64-g++ and not win32-g++. Patching the following piece of code would fix the issue: https://github.com/qt/qttools/blob/5.11/src/windeployqt/main.cpp#L196

However, considering #59 it might make sense just to switch back to win32-g++.
@Martchus Martchus added the bug label Mar 17, 2018
Martchus added a commit to Martchus/qtbase that referenced this issue Mar 17, 2018
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
ef02a56 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60
Martchus added a commit that referenced this issue Mar 17, 2018
@Martchus
Update mingw-w64-qt5-base-* packages
b026866 
* Improve documentation
* Switch back to patching win32-g++ rather than
  adding own mkspec to fix
    * #59
    * #60
* Not tested yet
Martchus added a commit to Martchus/qtbase that referenced this issue May 23, 2018
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
5e24eff 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60
Martchus added a commit to Martchus/qtbase that referenced this issue May 26, 2018
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
bd010d1 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60
Martchus added a commit to Martchus/qtbase that referenced this issue Jun 20, 2018
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
7fccb3d 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60
Martchus added a commit to Martchus/qtbase that referenced this issue Jun 24, 2018
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
955c447 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60
@Martchus Martchus closed this as completed Sep 8, 2018
Martchus added a commit to Martchus/qtbase that referenced this issue Sep 19, 2018
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
2658fe5 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60
Martchus added a commit to Martchus/qtbase that referenced this issue Dec 8, 2018
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
916b6a8 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60
Martchus added a commit to Martchus/qtbase that referenced this issue Dec 30, 2018
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
06ffb58 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60
Martchus added a commit to Martchus/qtbase that referenced this issue Dec 30, 2018
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
ebb6744 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60
Martchus added a commit to Martchus/qtbase that referenced this issue Feb 2, 2019
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
2ac4558 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60
Martchus added a commit to Martchus/qtbase that referenced this issue Mar 16, 2019
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
7b26289 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60
Martchus added a commit to Martchus/qtbase that referenced this issue Apr 20, 2019
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
9a22842 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60
Martchus added a commit to Martchus/qtbase that referenced this issue Jun 19, 2019
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
07a334d 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60
Martchus added a commit to Martchus/qtbase that referenced this issue Sep 6, 2019
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
a378fa3 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60
Martchus added a commit to Martchus/qtbase that referenced this issue Nov 1, 2019
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
e04f263 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60
Martchus added a commit to Martchus/qtbase that referenced this issue Dec 12, 2019
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
b9877c6 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I4c9b3c170ed13943abe0d8b397a8cb9e360538b6
Martchus added a commit to Martchus/qtbase that referenced this issue Jan 28, 2020
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
5a6b36b 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I4c9b3c170ed13943abe0d8b397a8cb9e360538b6
Martchus added a commit to Martchus/qtbase that referenced this issue Apr 1, 2020
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
c416378 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I4c9b3c170ed13943abe0d8b397a8cb9e360538b6
Martchus added a commit to Martchus/qtbase that referenced this issue May 29, 2020
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
8ecba79 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I4c9b3c170ed13943abe0d8b397a8cb9e360538b6
Martchus added a commit to Martchus/qtbase that referenced this issue Sep 10, 2020
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
14c0583 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Nov 5, 2020
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
c06d6c0 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Nov 20, 2020
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
ce90790 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Apr 13, 2021
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
c61fe93 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Apr 13, 2021
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
e598463 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Jun 1, 2021
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
72d9532 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Jun 1, 2021
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
ec51b8d 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Jun 27, 2021
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
7c9a1d9 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Aug 26, 2021
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
6637a06 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Aug 26, 2021
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
a418276 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Aug 26, 2021
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
94179ee 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Jan 2, 2022
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
927aade 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Mar 7, 2022
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
07e6639 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Apr 26, 2022
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
59ea6c2 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue May 16, 2022
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
23d804d 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Sep 9, 2022
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
28fc8a7 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Oct 4, 2022
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
e7efe15 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Oct 4, 2022
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
b536b4a 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Oct 31, 2022
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
0f1298e 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Jan 5, 2023
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
6a5eb2e 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Apr 10, 2023
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
a660177 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Jun 13, 2023
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
4b44fc8 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Aug 12, 2023
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
2858bbf 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Oct 8, 2023
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
ae03be9 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Oct 8, 2023
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
e1e2946 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Jan 7, 2024
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
880f978 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I127bb0516bd4acfea588a5d48c46811525a8fca8
Martchus added a commit to Martchus/qtbase that referenced this issue Jan 8, 2024
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
b6ccf3e 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I94f5a6c44c112bd44a84f802712077bc14782b4c
Martchus added a commit to Martchus/qtbase that referenced this issue Mar 15, 2024
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
c134da2 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I94f5a6c44c112bd44a84f802712077bc14782b4c
Martchus added a commit to Martchus/qtbase that referenced this issue May 28, 2024
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
e57a005 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I94f5a6c44c112bd44a84f802712077bc14782b4c
Martchus added a commit to Martchus/qtbase that referenced this issue May 28, 2024
@Martchus
Adjust win32-g++ profile for cross compilation with mingw-w64
5918544 
Adding a new, separate mkspec instead of patching the existing one
might be the cleaner solution. However, tools like windeployqt and
qbs do checks based on the hardcoded mkspec name to detect MinGW.
So for this to work, the mkspec must be called win32-g++.

Also see the following issues:
* Martchus/PKGBUILDs#59
* Martchus/PKGBUILDs#60

Change-Id: I94f5a6c44c112bd44a84f802712077bc14782b4c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Martchus