On Thursday, 20 December 2018 06:48:25 -02 André Hartmann wrote:
> And while you are right, that MSVC is better compatible with most
> Windows libraries, MinGW e.g. provides pthreads and therefore makes
> porting easier.
And if you're not targetting base i386 or base x86-64, GCC generates better
On 20/12/2018 10:48, André Hartmann wrote:
And while you are right, that MSVC is better compatible with most
Windows libraries, MinGW e.g. provides pthreads and therefore makes
porting easier.
It appears to me that Qt's biggest use case is portability? I use it to
build the same codebases on
Hi Markus,
Is there any actual reason why you can't use the prebuilt MSVC
binaries for MSVC 2017?
E.g. the much simpler setup: With the Qt online installer, you can setup
Qt, the compiler and debugger in one go and start coding in Creator
afterwards.
For MSVC, you have to install
Am Mo., 17. Dez. 2018 um 08:37 Uhr schrieb Amr Kamal :
> when Downloading the last version of QT 5.12.0 it only provides MinGW 64bit
> for windows which makes some problem with previous projects that used 32bit
> version especially if there is any kind of third-party library, at the same
>
> -Original Message-
> From: Interest On Behalf Of Henry Skoglund
> Sent: Tuesday, 18 December 2018 19:26
> >> I think the point is not to switch, but to provide an additional
> >> build. I'm going to guess the requestors' argument is going to be
> >> that they still need to ship 32-bit
On 18/12/2018 13:56, Kai Koehne wrote:
Building Qt with a recent MinGW 32 bit toolchain yourself should still work
though.
Is the toolchain installed by the Qt Online Installer 32-bit capable? Or
do we have to set up another one?
___
Interest
On 2018-12-18 17:34, Frank Hemer wrote:
Indeed - working in medical IT this is the major issue for me.
Frank
On Tuesday, 18 December 2018 17:28:05 CET Thiago Macieira wrote:
On Tuesday, 18 December 2018 03:56:47 PST Kai Koehne wrote:
Anyhow, we don't want to maintain two different MinGW
Indeed - working in medical IT this is the major issue for me.
Frank
On Tuesday, 18 December 2018 17:28:05 CET Thiago Macieira wrote:
> On Tuesday, 18 December 2018 03:56:47 PST Kai Koehne wrote:
> > Anyhow, we don't want to maintain two different MinGW builds; there was
> > quite some popular
On Tuesday, 18 December 2018 03:56:47 PST Kai Koehne wrote:
> Anyhow, we don't want to maintain two different MinGW builds; there was
> quite some popular demand for 64 bits (see e.g.
> https://bugreports.qt.io/browse/QTBUG-35288), so we switched to 64 bit in
> Qt 5.12. I don't see us switching
Hi,
If you want to be heard please create a suggestion on bugreports.qt-project.org
. interest@qt-project.org isn't necessarily read by all relevant people.
Anyhow, we don't want to maintain two different MinGW builds; there was quite
some popular demand for 64 bits (see e.g.
+1
> Am 17.12.2018 um 13:30 schrieb André Hartmann :
>
> +1
>
>> Am 17.12.18 um 12:44 schrieb Frank Hemer:
>> +1
>>> On Monday, 17 December 2018 08:11:34 CET Amr Kamal wrote:
>>> Hello,
>>>
>>> when Downloading the last version of QT 5.12.0 it only provides MinGW 64bit
>>> for windows which
+1
Am 17.12.18 um 12:44 schrieb Frank Hemer:
+1
On Monday, 17 December 2018 08:11:34 CET Amr Kamal wrote:
Hello,
when Downloading the last version of QT 5.12.0 it only provides MinGW 64bit
for windows which makes some problem with previous projects that used
32bit version especially if
+1
On Monday, 17 December 2018 08:11:34 CET Amr Kamal wrote:
> Hello,
>
> when Downloading the last version of QT 5.12.0 it only provides MinGW 64bit
> for windows which makes some problem with previous projects that used
> 32bit version especially if there is any kind of third-party library,
Hello,
when Downloading the last version of QT 5.12.0 it only provides MinGW 64bit
for windows which makes some problem with previous projects that used
32bit version especially if there is any kind of third-party library, at
the same time the need of using one updated version from QT, because
14 matches
Mail list logo
