Re: [Interest] equivalent of python glob

I always use '/' for my path, I use to native path only when doing command or when needed. I also have toWindowsPath toUnixPath functions when doing cross platform request (non native call). The cleanPath() could be useful indeed, but if i remeber well I had some special edge case I wanted to co

Re: [Interest] equivalent of python glob

On 27/8/19 12:33 am, Jérôme Godbout wrote: This is what I did for pathJoin const QString SEPARATOR("/"); QString FileSystemUtil::pathJoin(const QStringList& paths) Thanks. You could do that simpler with QDir::cleanPath() and QDir::toNativeSeparators() I think (and not have to hardcode the se

Re: [Interest] Q_NAMESPACE is not portable?

That's what I was attempting to point out.  I think "for instance" should be written out in this case, or use an established abbreviation, or dropped entirely:   "This is useful if the object needs to be exported from a dynamic library." "This is useful for intance, if the object needs to be

Re: [Interest] Static build of Qt - debug mode and plugins

Correct! Somewhat. I’m using VS under Windows configured to use ‘Unix Makefiles’ as generator when I’m connected to remote Linux boxes. Under Windows I use Ninja. Narolewski Jakub From: Elvis Stansvik Sent: 26 August 2019 18:54 To: Matthew Woehlke Cc: interest@qt-project.org Interest; Jakub Naro

Re: [Interest] Static build of Qt - debug mode and plugins

Den mån 26 aug. 2019 kl 18:49 skrev Matthew Woehlke : > > On 26/08/2019 12.18, Elvis Stansvik wrote: > > Den mån 26 aug. 2019 17:32Matthew Woehlke skrev: > >> ...or just run `make VERBOSE=1`. > > > > I didn't know if he was using ninja or make, so suggested the solution that > > I believe will work

Re: [Interest] Static build of Qt - debug mode and plugins

On 26/08/2019 12.18, Elvis Stansvik wrote: > Den mån 26 aug. 2019 17:32Matthew Woehlke skrev: >> ...or just run `make VERBOSE=1`. > > I didn't know if he was using ninja or make, so suggested the solution that > I believe will work with both (with recent versions of CMake) :) Fair point. I'm pret

Re: [Interest] Q_NAMESPACE is not portable?

On 26/08/2019 11.56, Giuseppe D'Angelo wrote: > On 26/08/2019 17:29, Matthew Woehlke wrote: >> BTW, what happened to the doc? Macros aren't class members... > > I'm thinking it's still https://bugreports.qt.io/browse/QTBUG-76822 Could be. >> (Relatedly, any word on lifting the implied dependenc

Re: [Interest] Static build of Qt - debug mode and plugins

Den mån 26 aug. 2019 17:32Matthew Woehlke skrev: > On 25/08/2019 03.09, Elvis Stansvik wrote: > > Den sön 25 aug. 2019 kl 02:56 skrev Thiago Macieira: > >> On Saturday, 24 August 2019 10:53:45 PDT Jakub Narolewski wrote: > >>> [ 1%] Linking CXX executable mrserver_debug > >> > >> Please expand t

Re: [Interest] Q_NAMESPACE is not portable?

Not trying to start a "thing", but I am curious where "f.i." comes from. Is this a new thing? I've honestly never seen it before. --- Andy Maloney // https://asmaloney.com twitter ~ @asmaloney On Mon, Aug 26, 2019 at 12:07 PM Giuseppe D'Angelo via Interest < i

Re: [Interest] Q_NAMESPACE is not portable?

On 26/08/2019 18:04, Jason H wrote: "This is useful f.i. if the object needs to be exported from a dynamic library." what's "f.i."? "For instance"? Isn't that "e.g." (but definitely not i.e.) "For instance" / "for example" are precisly the English translations of exempli grati-a... Cheers, -

Re: [Interest] Q_NAMESPACE is not portable?

> Sent: Friday, August 23, 2019 at 7:02 PM > From: "Giuseppe D'Angelo via Interest" > To: interest@qt-project.org > Subject: Re: [Interest] Q_NAMESPACE is not portable? > > On 24/08/2019 00:10, Matthew Woehlke wrote: > > Am I doing something wrong, or is it impossible to use Q_NAMESPACE > > corr

Re: [Interest] Q_NAMESPACE is not portable?

On 26/08/2019 17:29, Matthew Woehlke wrote: Okay... that's both good and bad news... good that it's fixed, bad that it isn't available in a released version. BTW, what happened to the doc? Macros aren't class members... I'm thinking it's still https://bugreports.qt.io/browse/QTBUG-76822 (

Re: [Interest] Static build of Qt - debug mode and plugins

Although all these examples look nice the CMAKE_VERBOSE_MAKEFILE is good enough for me as I currently develop my software remotely using VS Studio and it's remote CMake integration. I just modify CMakeSettings.json and there comes more stuff to read :) On Mon, 26 Aug 2019, 17:32 Matthew Woehlke,

Re: [Interest] Q_NAMESPACE is not portable?

On Monday, 26 August 2019 17:29:31 CEST Matthew Woehlke wrote: > On 23/08/2019 19.02, Giuseppe D'Angelo via Interest wrote: > > On 24/08/2019 00:10, Matthew Woehlke wrote: > >> Am I doing something wrong, or is it impossible to use Q_NAMESPACE > >> correctly without platform-specific PP conditional

Re: [Interest] Static build of Qt - debug mode and plugins

On 25/08/2019 03.09, Elvis Stansvik wrote: > Den sön 25 aug. 2019 kl 02:56 skrev Thiago Macieira: >> On Saturday, 24 August 2019 10:53:45 PDT Jakub Narolewski wrote: >>> [ 1%] Linking CXX executable mrserver_debug >> >> Please expand this line. > > Jakub, to do this you can pass -DCMAKE_VERBOSE_M

Re: [Interest] Q_NAMESPACE is not portable?

On 23/08/2019 19.02, Giuseppe D'Angelo via Interest wrote: > On 24/08/2019 00:10, Matthew Woehlke wrote: >> Am I doing something wrong, or is it impossible to use Q_NAMESPACE >> correctly without platform-specific PP conditionals? > > I've fixed this in 5.14, see > >> https://doc-snapshots.qt.io/

Re: [Interest] equivalent of python glob

This is what I did for pathJoin const QString SEPARATOR("/"); QString FileSystemUtil::pathJoin(const QStringList& paths) { QString rv; for(const QString& s : paths) { if(!rv.isEmpty() && !rv.endsWith(SEPARATOR)) { rv += SEPARATOR; } if(!rv.is

Re: [Interest] Static build of Qt - debug mode and plugins

Thanks again for starting it : ) > On 26. Aug 2019, at 16:01, Kyle Edwards wrote: > > On Sun, 2019-08-25 at 18:07 +, Alexandru Croitor wrote: >> Note that Qt 5.14 will come with support for importing static plugins >> from CMake, and you won't have to bother with the dependency order >> anym

Re: [Interest] Static build of Qt - debug mode and plugins

On Sun, 2019-08-25 at 18:07 +, Alexandru Croitor wrote: > Note that Qt 5.14 will come with support for importing static plugins > from CMake, and you won't have to bother with the dependency order > anymore. Thanks again for finishing that off for me! Kyle

Re: [Interest] Static build of Qt - debug mode and plugins

On 8/26/19 5:00 AM, Thiago Macieira wrote: It's also interesting that QtCore and QtNetwork are listed three times. Multiple inclusions has been happening for a long time. I butted heads with that when creating that "Explore this computer" app which had to install on Ubuntu 12, 13, 14, and 15 b