On Monday, 29 July 2019 09:33:41 PDT maitai wrote:
> Hi all,
>
> I have some Windows 10/64 bits users reporting "TLS initialization
> failed" when running our app, built with Qt 5.13.0 MSVC 2017/64 bits
>
> I have found this page:
>
> https://doc.qt.io/qt-5/windows-requirements.html
>
> But
On Monday, 29 July 2019 13:28:04 PDT Nikos Chantziaras wrote:
> > This is only required when referring to it by name, such as in old-style
> > signal-slot connection, QML, D-Bus, etc.
>
> They're new-style connections, but are sometimes of QueuedConnection
> type since some connections are used
On Monday, 29 July 2019 09:25:04 PDT Tomasz Olszak wrote:
> What's is the cons of putting something like that in anonymous namespace
> instead of constructor?
It's run on program load, before main(), even if the type is never used.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software
po 29. 7. 2019 v 21:00 odesílatel Nikos Chantziaras
napsal:
> The linker might remove it from the executable when linking statically,
> because 'registerHelper' is not referenced anywhere.
>
>
> On 29/07/2019 19:25, Tomasz Olszak wrote:
> > What's is the cons of putting something like that in
On 28/07/2019 07:15, Thiago Macieira wrote:
On Friday, 26 July 2019 17:35:03 PDT Nikos Chantziaras wrote:
I didn't (although I use Q_ENUM, but it does the same job.) But there's
no constructor to put qRegisterMetaType() in. It's an enum. There's no
constructor. Some enums are in a namespace,
The linker might remove it from the executable when linking statically,
because 'registerHelper' is not referenced anywhere.
On 29/07/2019 19:25, Tomasz Olszak wrote:
What's is the cons of putting something like that in anonymous namespace
instead of constructor?
namespace {
struct
Ah, my mistake, I misunderstood.
According to this comment, on Windows, PATH is traversed when looking for
shared libs: https://stackoverflow.com/a/7148123/57290
Might be worth checking out.
/René
On Mon, 29 Jul 2019 at 19:59, maitai wrote:
> Thanks René,
>
> I may be wrong but these
Thanks René,
I may be wrong but these variables look like build variables in case you
want to build Qt.
I am looking for a runtime variable to indicate where the libs are, and
I hope to be able to set it from inside main with qputenv, otherwise
it's back to 5.12.3
Philippe.
Le 29-07-2019
This archived 5.11 page might be what you're looking for:
https://doc.qt.io/archives/qt-5.11/ssl.html
I don't know if pkg-config is available to Windows users, but in case it
is, this would do as well:
QT_CONFIG -= no-pkg-config
CONFIG += link_pkgconfig
PKGCONFIG +=
seconded
> On Jul 29, 2019, at 9:33 AM, maitai wrote:
>
> Hi all,
>
> I have some Windows 10/64 bits users reporting "TLS initialization failed"
> when running our app, built with Qt 5.13.0 MSVC 2017/64 bits
>
> I have found this page:
>
> https://doc.qt.io/qt-5/windows-requirements.html
>
Hi all,
I have some Windows 10/64 bits users reporting "TLS initialization
failed" when running our app, built with Qt 5.13.0 MSVC 2017/64 bits
I have found this page:
https://doc.qt.io/qt-5/windows-requirements.html
But the interesting part is missing, i.e. what variable should I set to
What's is the cons of putting something like that in anonymous namespace
instead of constructor?
namespace {
struct RegisterHelper
{
RegisterHelper()
{
qRegisterMetaType();
qRegisterMetaType();
qRegisterMetaTypeStreamOperators();
}
};
static RegisterHelper
On Mon, 29 Jul 2019 at 20:36, praveen kumar wrote:
>
> Hi team,
>
> please suggest a suitable/ customized Qt version for my low end hardware
> configuration.
>
> Please find below my hardware configuration details:
>
> RAM - 32MB/64MB
> FLASH - 64 MB XIP
> Processor - ARM CORTEX A9 @ 400MHz
>
Hi team,
please suggest a suitable/ customized Qt version for my low end hardware
configuration.
Please find below my hardware configuration details:
RAM - 32MB/64MB
FLASH - 64 MB XIP
Processor - ARM CORTEX A9 @ 400MHz
Display resolution: 3 variants(1280×800, 800×480, 480×272)
Regards,
14 matches
Mail list logo
