difficult in
another.
> Does this sound good?
Yes.
For me, there's no such thing as LTS anyway, so I don't care about anything
6.5 beyond 6.5.3. This policy doesn't affect *me*.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Fleet Engineering and Quality
t you can throw through Cocoa frames, then it
would be worth having the unwind info, if nothing else to support the case of
"emergency save in main()".
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Fleet Engineering and Quality
smime.p7s
Descript
be something we support in the
> build system through a toggle.
That definitely needs fixing. At a minimum, the #recovering-from-exceptions
section is wrong, because we know the exception can't propagate through the
event loop.
The #signals-and-slots section is what I said above.
--
Thiago Macieir
as noexcept and
catch your own exceptions before they go back to Qt code. This is the reason
why we decided it was ok to disable exceptions in QtWidgets itself, because we
didn't think we could guarantee survivability in the first place.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Princi
at GDK isn't getting the reply it needs because
that reply was sent to our Display and connection and thus handled by our
thread.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Fleet Engineering and Quality
smime.p7s
Description: S/MIME cryptograph
nAtom didn't arrive. You need to deduce
a reason why the X server would fail to send that.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Fleet Engineering and Quality
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
De
Gtk3 theme is loaded (which means GDK is in
use in the main thread) and don't use your new technique.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Fleet Engineering and Quality
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailin
6. So things fail there, with positions for sub-menus or
windows not to correct.
Beyond that, both for kwin- and plasmashell-provided components (titlebar,
status bar), the icons were wrong because they were not scaled up. I think
those two override the scale factor somehow.
--
Thiago
On Tuesday 14 May 2024 13:24:12 GMT-7 Ilya Fedin wrote:
> On Tue, 14 May 2024 12:59:29 -0700
>
> Thiago Macieira wrote:
> > Assuming that Canonical did not patch libgdk,
>
> Well, that is a very optimistic assumption:
> http://archive.ubuntu.com/ubuntu/pool/main/g
On Tuesday 14 May 2024 12:30:42 GMT-7 Thiago Macieira wrote:
> Those may be inlines. If I try addr2line, then the frames are:
Using gdb instead of addr2line:
frame 6:
Line 116 of "x11/../../../../../gdk/x11/gdkproperty-x11.c" starts at address
0x773d8
and ends at 0x773eb .
On Tuesday 14 May 2024 12:30:42 GMT-7 Thiago Macieira wrote:
> Those may be inlines. If I try addr2line, then the frames are:
> gdk_x11_atom_to_xatom_for_display at ??:?
> gdk_x11_lookup_xdisplay at ??:?
> gdk_x11_display_broadcast_startup_message at ??:?
> gdk_x11_drag_c
On Tuesday 14 May 2024 12:13:29 GMT-7 Thiago Macieira wrote:
> #6 0x7fe3fc6e93d8 in gdk_x11_atom_to_xatom_for_display () at
> /lib/x86_64- linux-gnu/libgdk-3.so.0
773d3: e8 58 7f fb ff call 2f330
773d8: 4c 89 e6mov%r12,%rsi
That woul
On Tuesday 14 May 2024 11:44:24 GMT-7 Thiago Macieira wrote:
> Think in terms of side-effects. It doesn't care how Qt does it, but the
> side- effect of what we are doing could be important, since we're sharing
> libxcb internal state, the xcb_connection (I think), and the X11 server
her our dispatcher is QXcbGlibEventDispatcher. If it is, then don't use
the new feature.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Fleet Engineering and Quality
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt
er and it hangs... But I'm unable to
> reproduce that myself to debug.
Maybe the issue is something that you've stopped doing because you're now
doing this.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Fleet Engineering and Quality
smime.p7s
Description: S/
how
> as the CI doesn't print the relevant gtk frames in the trace to examine
> its code.
Please confirm that your changes require that you reply to something requested
from other applications. If so, make sure you can reply from the XCB event
thread.
--
Thiago Macieira - thiago.macieira (AT)
e from that separate thread.
The above isn't cmptest. It's tst_qsettings. But you can see other tests
having the same problem too, like tst_qguichronotimer.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Fleet Engineering and Quality
smime.p7s
Description:
s.
That assumes we will have something. I am not convinced yet that any
application exists where the three conditions I mentioned in another email are
met.
And besides, you've just said that the replacement may have a different API.
That implies we haven't finished designing it yet.
--
Thi
ve. You have to match.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
he non-UI component
doesn't want to use QCoreDesktopServices::openUrl in the first place: it wants
to communicate with its UI component through whichever communication mechanism
it has established.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Cloud Engin
On Tuesday 7 May 2024 10:03:21 GMT-7 Thiago Macieira wrote:
> So I want to know of a use-case where all of the following are true:
> * application is GUI-less (i.e., is a background service)
> * application has no GUI counterpart
> * application is definitely running in a GUI
io/cgit/qt/qtbase.git/tree/src/widgets/widgets/qtoolbutton.h?
h=v5.15.13-lts-lgpl
Therefore, your issue is that you've compiled something against the Qt 6
headers.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Cloud Engineering
smime.p7s
Description:
ok like the one you implemented, such
that the dependency isn't there. My request was about front-end API.
> The logical argument is that a) QUrl itself and b) QMimeTypeDatabase,
> which co-determines which program to run on openUrl(), are both in
> QtCore, so it makes sense that openUrl()
an API now that will work with intents/activities.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/li
I'd like an argument
why the API should be in QtCore, as opposed to QtNetwork (it's a browser after
all).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Cloud Engineering
# -*- conf -*-
[Unit]
Description=Service for the Microsoft365 OAuth2 proxying
Condition
or QDesktopServices, at least there is no
object and therefore no one is expecting to have functions with it as part of
the mangled name.
Those two platforms are:
- Darwin (macOS, iOS, etc.)
- Windows
So not insignificant. And moreover, the two platforms where no one EVER runs
without a GUI.
oblems and promised not to do it again.
So QDesktopServices can't be moved. You can add a new class to QtCore.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailin
DesktopServices is really just about GUI desktops. Further,
QPlatformIntegration *IS* QPA. You can't move that class to QtCore.
I suggest having a background hook that QPA registers with QtCore so that
QtNetwork can use to launch the browser if QPA has been loaded, but shall fail
if not
st. Don't wait months and years: you're
entitled to getting a review within one month. The worst that can happen are
that someone decides to make a permanent rejection because they can't justify
accepting.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Cloud En
ly no clue on reviewing XCB stuff, but I had to click every link to
make sure none of them was a QtCore issue I might have missed.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Develop
next
Qt minor release and include in the next release set.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-proje
On Thursday, 28 March 2024 01:06:37 PDT Björn Strömberg wrote:
> example on spectrum on the support on modules: [unmaintained, deprecated,
> life-support, full-maintenance, feature-development]
The .gitmodules file for qt5.git is that.
--
Thiago Macieira - thiago.macieira (AT) int
On Friday, 15 March 2024 11:03:19 PDT Thiago Macieira wrote:
> On Friday, 15 March 2024 10:09:31 PDT Marc Mutz via Development wrote:
> > I like simple rules. "Overrides should have the same access level as the
> > initial virtual function." is a simple rule.
>
> Am
I'm
ok. As you can still access by casting to a base, that had better be a good
reason.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-pr
est C++20 mode with 2019 for a day or so, and some changes that
trigger 2019's broken C++20 support went in. If we don't drop 2019 by 6.8
release, we should force it to only compile in C++17 mode.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Cloud En
and I trust that he will make a
> good approver for the Qt project.
+1
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
h
ed. One can always rebuild the binaries
if needed.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-pr
ss that just matches the linguistic baggage.)
It's an unnamed namespace, not anonymous namespace.
There's such a thing as anonymous union, though.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic
can help readability,
> particularly in reviews.
+1
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt
n
> an unnamed namespace [...]"
>
> Either I am missunderstanding something, or Qt Coding Conventions and
> C++ Core Guidelines strongly disagree on whether to use anonymous
> namespaces.
Fair.
But I disagree with SF22 and will continue to use statics. There's nothing
wrong with them.
-
imply
replace our wording to point to SF22 or am I missing something?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://li
On Friday, 9 February 2024 23:04:20 PST Thiago Macieira wrote:
> I added a fallback to C++17. I make no promises that it has the same level
> of compatibility as the C++20 official concept. In fact, I know it doesn't.
> It will reject some types and accept others that it shouldn't.
&g
I have absolutely no problem in making this feature only
accessible in C++20, if need be.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt
cf742ea23f4a30dcfc38a4988fe56 in 5.3.0.
commit ea8e48a6799cf742ea23f4a30dcfc38a4988fe56
Author: Thiago Macieira
Date: Thu Dec 19 23:32:04 2013 -0800
Update the qHash function for strings to use the CRC32 instruction
According to my profiling of Qt Creator, qHash and the SHA-1 ca
cussion in the change about whether this was
correct or not. It seems I just write it like that.
However, that was qHashBits(). The change I'm talking about is
qHash(QLatin1StringView), specifically so it won't call qHashBits().
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Softw
about instead we drop at an LTS+2 release? The next one is actually 6.7.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
On Sunday, 4 February 2024 06:12:18 PST Giuseppe D'Angelo via Development
wrote:
> Il 03/02/24 22:08, Thiago Macieira ha scritto:
> > But what about a zero seed? It's what we call a "deterministic hashing".
> > We
> > have changed the algorithms on .0 releases (in b
e non-zero seeds, but one couldn't rely on the
above unless it applied for every seed.f
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-p
On Tuesday, 2 May 2023 17:39:01 PST Thiago Macieira wrote:
> I don't have access to QNX and INTEGRITY toolchain information, so I'd like
> to request that they simply match the feature list above, with minimal
> workarounds.
What's the current state for those, for supporting Qt 6.8 or
ugreports.qt.io/browse/QTBUG-109361
> 3. C++20 is mandatory for users of Qt -
> https://bugreports.qt.io/browse/QTBUG-109362
Those tasks haven't got any updates recently. What's the status?
I'd like to ask that we go to #3 for 6.8 or 6.9.
--
Thiago Macieira - thiago.macieira (AT) intel
at time, I think it's time to drop.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On Wednesday, 17 January 2024 19:35:17 PST Thiago Macieira wrote:
> Alternatives:
> * move to a class that is not exported
>trick: add an empty base with the variable
> * change to enum (if primitive)
* change to an static (inline) constexpr function
Then there's always a copy,
On Wednesday, 17 January 2024 19:35:17 PST Thiago Macieira wrote:
> This appears to be a GCC bug/shortcoming. Clang and MSVC apparently
> automatically emit and export the variable for you:
> https://mingw.godbolt.org/z/q4dYdosjh
Reported at https://gcc.gnu.org/bugzilla/show_bug.cgi?
_M_realloc_insert(), which takes the integer by reference, so
the compiler emits an import from the DLL.
This appears to be a GCC bug/shortcoming. Clang and MSVC apparently
automatically emit and export the variable for you:
https://mingw.godbolt.org/z/q4dYdosjh
--
Thiago Macieira
appens to include the Gerrit Change-Id one).
So if there are any tools that are considered "should provide"[1] to
beginners, please port them to CMake.
[1] Gradation: "must provide", "should provide", "would be nice to provide"
--
Thiago Macieira - thiago.maci
ing into bitrot
is not a problem either.
So if anyone wants to port anything, get busy.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Developmen
ven me. As far
as I know, that removed the dependency on Perl to compile Qt or to contribute.
What's left that you're seeing?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic sig
e do need something.
In particular, we do need macros themselves, so we can perform proper
expansion in the classes we're trying to generate meta objects for. If this is
something that will never come from imports, great, it's a major barrier
removed.
The question is what else.
--
Thiago Maci
nd all other entities declared, which are part of the
translation unit. Moc does need that.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Developm
be no behaviour change at
all, anywhere. If that turns out to be a large change, we may want to
postpone; if it breaks something, then we've likely found a bug.
So, +1 for me on going ahead.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Enginee
ch to non-strict mode in
compiling those two libraries or we must ignore our own flag in them. Neither
option is appetising.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
De
the build I made yesterday.
[1] https://codebrowser.dev/gcc/gcc/c-family/c-cppbuiltin.cc.html#1224
[2] https://bugreports.qt.io/browse/QTCREATORBUG-30044
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME c
existing users may inform us in how much breakage we/they are willing to
accept.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-pr
w that this used to be "GENIVI Extras" does not help yet. "GENIVI
Extras" meant something; "interfaces" or even just "automotive interfaces" do
not.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
support in the same bucket as FreeBSD or HaikuOS or
Sparc processor support: whoever is using this[1] must supply patches.
I propose we re-review once a year.
[1] that may include the Qt Company if their commercial interests call for it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud
ave a use for a cross-platform #warning or the deprecation
> of a whole header, restore and stage
> https://codereview.qt-project.org/c/qt/qtbase/+/523363, it's already
> approved and just waits for a user.
QT_WARNING_MSG is useful in other contexts too, for example for deprecating
u're trying to get the information about the current item,
it's stat()ing the next. It's also hard to guess which element you're getting
and whether you're accidentally skipping the first entry, or missing the last
one.
All of which are caused by the fact that it *is* a Java-style iterator.
-
On Tuesday, 5 December 2023 08:54:29 PST Thiago Macieira wrote:
> Then why are you asking for a repository if it's already there? When was
> that module approved by the Qt Project? I can't find anything in the email
> archives.
>
> The first commit in this repository is
ed it?
That module is not in qt5.git/.gitmodules so it's *not* a Qt module right now.
Source- and binary-compatibility do not apply.
That Git repository is also not sync'ed to GitHub.
Anyway, I am exercising my right to vote to vote -1 on this repository request
so long as it is using thi
n when originally imported. There is no
source- or binary-compatibility guarantee offered against pre-Qt Project or
Labs implementations.
I insist: find a more precise name for the module. "Interface" is too generic,
you need one more word, at a minimum.
--
Thiago Macieira -
Neither QNetworkInterface nor QDBusInterface belong there, therefore there
must be a constraint of some sort.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
D
on't believe the BIC break between 6.6.0 and 6.6.1 was
> intentional.
It was intentional. We have to choose one of the two ELF versions so we chose
the one that restored compatibility with older 6.x.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cl
about whether we're going to have a replacement at all or not. If we're
not, if the replacement is simply QFile, then there's nothing stopping us from
deprecating.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Descripti
classes or providing a
replacement?
A: Sure. I'll be happy to review your code and offer my insight. I just won't
do the coding myself.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signa
pe of any exported function.
So I advise we just use the Qt types and come Qt 7 they become a typedef.
There's no need to use the Standard types right now.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Descriptio
id the conversions (specially if we use
> std::bit_cast).
Yes, but the impact only applies to when it needs to translate from out-of-
line to out-of-line. If either side is inline, it'll do the right thing on its
own.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Arch
ions can return one of these other types:
bool (for equality comparisons)
int (for non-partial ordering)
QPartialOrdering (for partial ordering)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIM
sn't have a
> `using std::...`, yet, so we're still ok, and QTestLib doesn't have BC
> constraints).
>
> The Qt::*ordering types, OTOH, are specifically _for_ use in the ABI.
This does mean those types won't be documented, right?
We forward to the C++ Standard Library documentation.
On Monday, 13 November 2023 09:38:43 PST Ivan Solovev via Development wrote:
> I really do not want to miss yet another FF.
Given that this is an API that is going to stay with us for at least a decade,
I'd rather get it right than getting it soon.
--
Thiago Macieira - thiago.macie
On Monday, 13 November 2023 09:15:10 PST Marc Mutz via Development wrote:
> On 13.11.23 17:15, Thiago Macieira wrote:
> > On Monday, 13 November 2023 01:34:08 PST Ivan Solovev via Development
wrote:
> > I don't think this minor thing is worth the hassle. It uglifies our API
>
is worth the hassle. It uglifies our API for
little gain.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On Friday, 10 November 2023 00:11:11 PST Marc Mutz via Development wrote:
> On 09.11.23 16:28, Thiago Macieira wrote:
> > But if the symbols are globally visible (ELF visibility STV_DEFAULT)
>
> That counts as "exported", doesn't it?
Yes.
> Which leaves us with:
>
ordering).
> Which is, probably, already true.
Because the types in the libraries seem to be made so it's very difficult to
get
the actual values into and out of them. But bit_cast throws that away and
allows us to see behind the scenes.
--
Thiago Macieira - thiago.macieira (AT) intel
s return type or the layout of the type it
does return.
But yes we should add to it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
ht be possible to massage the code in such a way that the compiler
realises that it is always idempotent. I haven't managed yet. We can also just
be evil and use bit_cast:
https://gcc.godbolt.org/z/e5zefKevP
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI C
o partial ordering, while the vast majority of types are fully
ordered. The impact of QAnyStringView in any API is greater.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
-
and improve Qt in several aspects, so I have no doubt
that they will do a great job with grpc as maintainers. I've worked with
Alexey more than with Tatiana, but this statement goes for both.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineer
ever Auto" applies and especially so for return types
(when used for deducing a type, not for syntactic brevity).
[1] https://codereview.qt-project.org/c/qt/qtbase/+/491119
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p
executable (= cmake
> target).
>
> This is probably the safest. If we allowed this instead, we'd need to
> review all of our APIs to see whether we have a similar issue already.
You must remove "cmake target" portion. This applies to the executable as
loaded into memory.
--
ay be merged from multiple independent libraries at runtime.
So don't violate ODR.
At worst, you can make them overload each other by having different parameters.
So the Qt functions can switch between the two return type families. But you
can't overload operators, so operators mus
hout waiting for
all its threads to exit.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
I looked
at the CMake output and didn't see anything wrong. The error was in the linker
command-line and I accidentally edited it out when pasting it into the email.
Now that you pointed out, yes, the path to librt.a was wrong.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software
it's a good idea to install the mingw64-postgresql package instead
and not depend on C:/Program Files.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing lis
ear to be import libraries, so I don't know why the linker thinks
there's a conflict.
I repeat that it works for me, but for Haowei it doesn't. I don't know why.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MI
;configure.bat" as your email subject said. You ran
the configure shell script. I don't know if that makes a difference, as I
haven't run either for 3 years.
If you want to run configure.bat, you must type:
cmd \ /c ../../configure -release [...]
--
Thiago Macieira - thiago.macieira (
-week pings I sent over Gerrit; they'll be here
next week if they aren't reviewed.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt
The 1st time happens when configuring 'qtbase'
>2. The 2nd time happens when configuring 'qttools'
>
> Let's why the 2nd time thinks the 'zstd::libzstd_static' target is already
> defined.
> If so, I wondered whether you have any solution to the cause of this
> zstd-relared
ic use in the
first place.
> I don't see how we can manage without an API for doing three-way
> comparisons in C++17.
>
> We can try without (4), but (1)-(3) must needs be "semi-public" API (not
> in _p.h's).
I'm ok with semi-public. That means I can change them or remove t
to C++20 or complain to their vendors. We are talking about
adding this to a Qt release to happen in 2024, nearly 4 years after the C++
edition was published.
I won't oppose it if it is simple, without imposing undue constraints. But it
need not be part of the initial design.
--
Thiago
dable by average C++ developers. It is not a good corner of C++.
(4) (the convenience function) is what users expect. Except that we don't need
it to be called qEquals, because we have an even better name for it:
operator==
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect
1 - 100 of 6011 matches
Mail list logo
