On Tuesday, 12 April 2022 16:32:42 PDT Dirk Hohndel wrote:
> That's exactly what it does. I'm surprised that no one else ran into this,
> though. After all, the Qt distribution binaries are all fat binaries.
Must be a combination of fat binaries and something about the paths
themselves. The code
> On Apr 12, 2022, at 06:20, Thiago wrote:
>
> On Monday, 11 April 2022 23:17:17 PDT Dirk Hohndel wrote:
>>> The error message is talking about how the same path was being removed
>>> more
>>> than once, which means your binary has it twice. I guess this had simply
>>> never occurred in the past
Ive Clean / Run CMake configuration and it works perfectly.
I should have done that before posting.
Sorry for the inconvenience.
Thank you so much.
Rémy
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/in
On Tuesday, 12 April 2022 01:33:13 PDT Tor Arne Vestbø wrote:
> In the case of ARM support, as Thiago said, the minimum Xcode version we
> support is effectively raised from Xcode 11 to Xcode 12, but I recommend
> Xcode 13.
For me, the problem with Xcode 13 is that it requires a newer version of m
On Monday, 11 April 2022 23:17:17 PDT Dirk Hohndel wrote:
> > The error message is talking about how the same path was being removed
> > more
> > than once, which means your binary has it twice. I guess this had simply
> > never occurred in the past. Deduplicating the paths is not a bad idea in
> >
Hi,
Since Qt Creator 6 that it seems impossible to launch an app selected as
executable under project run settings.
Today I have updated to Qt Creator 7 and the problems seems to persist.
When I launch the project, which is a plugin that will be loaded into an
application, I get:
Failed to la
Hi,
I've seen these kinds of error messages a lot also when not cross-compiling.
They always occurred after upgrading Qt 6.x.x packages (e.g. provided by TW),
especially when Qt 6 was still in the alpha/beta phase. I could always resolve
it by simply adapting my CMake config accordingly (or sim
Hi everyone,
I try to compile my project with the just released Qt 6.3.0 and I have this
CMake Error:
-
CMake Error at
C:/Qt/6.3.0/android_arm64_v8a/lib/cmake/Qt6/QtFeature.cmake:1249 (message):
Feature ssl is already defined to be "OFF" and should now be set to "ON"
when importing fea
I noticed that since some time iOS apps are really slow in debug mode
(not only at startup), but run fast in release mode (with compiler on)
(5.15.7 - will use 5.15.9 soon)
BTW: I never have situations where per ex at start-of-app a repeater
creates many objects, normaly first page the user wil
Hi,
I have a problem were all my apps take several seconds to become responsive.
The more complex the app is, the more time it takes to get responsive to touch.
This didn’t used to be this way.
I can easily demonstrate the issue happening with a simple example, which does
not happen in Windows
On 11/4/22 22:52, Alexander Carôt wrote:
Thus, I decided to continue using the minibrowser code which already is Qt6
ready and worked out fine for me so far. However, here I have the problem that
it does not store cookies. I did some research and found e.g.
https://stackoverflow.com/questions/
On 11/4/22 22:52, Alexander Carôt wrote:
Thus, I decided to continue using the minibrowser code which already is Qt6
ready and worked out fine for me so far. However, here I have the problem that
it does not store cookies. I did some research and found e.g.
https://stackoverflow.com/questions
Hey hey,
You generally want to use the latest Xcode/SDK.
In the case of ARM support, as Thiago said, the minimum Xcode version we
support is effectively raised from Xcode 11 to Xcode 12, but I recommend Xcode
13.
Tor Arne
> On 11 Apr 2022, at 21:51, Thiago Macieira wrote:
>
> On Monday, 1
13 matches
Mail list logo
