<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Qt Contribution]]></title><description><![CDATA[Qt Contribution]]></description><link>https://forum.qt.io/category/48</link><generator>RSS for Node</generator><lastBuildDate>Thu, 13 Aug 2026 21:09:47 GMT</lastBuildDate><atom:link href="https://forum.qt.io/category/48.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 01 Oct 2025 13:25:52 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[New contribution or keep custom builds ?]]></title><description><![CDATA[I think it's worth asking on the bug report system to see whether they are too specific.
]]></description><link>https://forum.qt.io/topic/163398/new-contribution-or-keep-custom-builds</link><guid isPermaLink="true">https://forum.qt.io/topic/163398/new-contribution-or-keep-custom-builds</guid><dc:creator><![CDATA[SGaist]]></dc:creator><pubDate>Wed, 01 Oct 2025 13:25:52 GMT</pubDate></item><item><title><![CDATA[Questions about LTS maintenance]]></title><description><![CDATA[Hi,
AFAIK LTS branches do receive fixes otherwise there wouldn't be a sense to have them in the first place. At least they do in the Qt modules. For that particular case I think it might have been a glitch but I don't know how the branches are managed for Qt for Python.
]]></description><link>https://forum.qt.io/topic/162712/questions-about-lts-maintenance</link><guid isPermaLink="true">https://forum.qt.io/topic/162712/questions-about-lts-maintenance</guid><dc:creator><![CDATA[SGaist]]></dc:creator><pubDate>Wed, 16 Jul 2025 14:54:06 GMT</pubDate></item><item><title><![CDATA[configure gerrit userid for repository]]></title><description><![CDATA[It is all working now - I had to do some finagling using git remote to correct the entries for gerrit to use my userid rather than the email.
]]></description><link>https://forum.qt.io/topic/160025/configure-gerrit-userid-for-repository</link><guid isPermaLink="true">https://forum.qt.io/topic/160025/configure-gerrit-userid-for-repository</guid><dc:creator><![CDATA[Perdrix]]></dc:creator><pubDate>Tue, 03 Dec 2024 14:05:59 GMT</pubDate></item><item><title><![CDATA[trying to build release build of  Qt from repository]]></title><description><![CDATA[Have you followed the steps described here?
At the end of the day it doesn't matter how the project is configured, as long as you pass the right arguments and the build path is clean.
I don't know which version of Qt you are building on which operating system, but it looks like the build tree has been configured before with some flags that force it into a debug build.
]]></description><link>https://forum.qt.io/topic/159979/trying-to-build-release-build-of-qt-from-repository</link><guid isPermaLink="true">https://forum.qt.io/topic/159979/trying-to-build-release-build-of-qt-from-repository</guid><dc:creator><![CDATA[Axel Spoerl]]></dc:creator><pubDate>Sun, 01 Dec 2024 12:22:30 GMT</pubDate></item><item><title><![CDATA[Idea for not-null pointer type support in the Qt API]]></title><description><![CDATA[@Paul-Breeuwsma said in Idea for not-null pointer type support in the Qt API:

passing null would give undefined behaviour

99.9999999% of the times passing null is segfault. QUndoGroup::addStack is a great example. Its an easy crash to debug
I feel like the concept of "not null pointer" already exists in C++, it's called a reference. Qt already uses references as never-null-pointers internally in the D-Pointer architecture (e.g. QObject::QObject(QObjectPrivate &amp;dd, QObject *parent) where the first argument is actually a pointer that is never null). It just turns out sometimes it's more confusing to use the reference than having an explicit pointer
]]></description><link>https://forum.qt.io/topic/158724/idea-for-not-null-pointer-type-support-in-the-qt-api</link><guid isPermaLink="true">https://forum.qt.io/topic/158724/idea-for-not-null-pointer-type-support-in-the-qt-api</guid><dc:creator><![CDATA[VRonin]]></dc:creator><pubDate>Sun, 15 Sep 2024 20:39:38 GMT</pubDate></item><item><title><![CDATA[compute]]></title><description><![CDATA[https://github.com/hypre-space/hypre may be interesting as well.
]]></description><link>https://forum.qt.io/topic/158520/compute</link><guid isPermaLink="true">https://forum.qt.io/topic/158520/compute</guid><dc:creator><![CDATA[JoeCFD]]></dc:creator><pubDate>Tue, 03 Sep 2024 07:58:53 GMT</pubDate></item><item><title><![CDATA[Improve &quot;Visualize Indent&quot; option]]></title><description><![CDATA[@Engelard there's no direct integration, so yes, you've to file things anew.
]]></description><link>https://forum.qt.io/topic/154360/improve-visualize-indent-option</link><guid isPermaLink="true">https://forum.qt.io/topic/154360/improve-visualize-indent-option</guid><dc:creator><![CDATA[kkoehne]]></dc:creator><pubDate>Tue, 06 Feb 2024 14:33:36 GMT</pubDate></item><item><title><![CDATA[Assessment of the difficulty in porting CPU architecture for QT5]]></title><description><![CDATA[@xxuan You could also ask on Qt Developers mailing list where you will find actual Qt developers. This forum is for Qt users.
]]></description><link>https://forum.qt.io/topic/149118/assessment-of-the-difficulty-in-porting-cpu-architecture-for-qt5</link><guid isPermaLink="true">https://forum.qt.io/topic/149118/assessment-of-the-difficulty-in-porting-cpu-architecture-for-qt5</guid><dc:creator><![CDATA[jsulm]]></dc:creator><pubDate>Thu, 07 Sep 2023 06:15:54 GMT</pubDate></item><item><title><![CDATA[Please provide ways of debugging internal errors in PyQt]]></title><description><![CDATA[@IDontKnowHowToCode
PyQt is produced by Riverbank Computing.  If you would like to see them implement something in PyQt which would help you debug you can ask them.  Or this might be a general issue in Python code which calls C libraries.
]]></description><link>https://forum.qt.io/topic/146098/please-provide-ways-of-debugging-internal-errors-in-pyqt</link><guid isPermaLink="true">https://forum.qt.io/topic/146098/please-provide-ways-of-debugging-internal-errors-in-pyqt</guid><dc:creator><![CDATA[JonB]]></dc:creator><pubDate>Thu, 29 Jun 2023 15:35:24 GMT</pubDate></item><item><title><![CDATA[Proposal for better JSON serialization control]]></title><description><![CDATA[I think this is a great idea. It would be great to have more control over the serialization of JSON data. It would make it easier to customize the output and make sure that the data is properly formatted. It would also make it easier to debug any issues that may arise. I think this would be a great addition to the Qt library.
]]></description><link>https://forum.qt.io/topic/142424/proposal-for-better-json-serialization-control</link><guid isPermaLink="true">https://forum.qt.io/topic/142424/proposal-for-better-json-serialization-control</guid><dc:creator><![CDATA[Chronal]]></dc:creator><pubDate>Tue, 24 Jan 2023 23:49:25 GMT</pubDate></item><item><title><![CDATA[Would Qt accept an official C binding?]]></title><description><![CDATA[Hello. I'm using a different account now.
What happened was I subscribed to the mailing list and sent the message, but I got a reply saying that I can't send messages to the mailing list because I'm not a Qt developer.  I don't know why but after that I just gave up on the idea and tried to create an external binding, and I completely forgot about this untill now. It's probably a good thing though, because I've gained a lot more experience in C++ since then and I think I wouldn't have been able to contribute anything without it.
I've created a gerrit account by following the "Contributing to Qt" wiki, and I'm going to try to send a message again. Just wanted to appologize for forgetting about the thread half-way through the discussion. I'll mark it as solved.
EDIT: I can't mark it as solved on this account, but I'll sign in later today and do that.
]]></description><link>https://forum.qt.io/topic/136257/would-qt-accept-an-official-c-binding</link><guid isPermaLink="true">https://forum.qt.io/topic/136257/would-qt-accept-an-official-c-binding</guid><dc:creator><![CDATA[sammonius]]></dc:creator><pubDate>Tue, 03 May 2022 14:27:10 GMT</pubDate></item><item><title><![CDATA[Typo found online]]></title><description><![CDATA[Hi, and welcome!
@Xarzu said in Typo found online:

Hello friends.  I want to help.  I found a typo online (https://wiki.qt.io/Building_Qt_5_from_Git#Getting_the_source_code) under the caption "Cloning specific Qt submodule", the first word "Ypu" should be "You".  I only want to help.

Thanks for reporting this. I have fixed it.
In the future, you can edit Wiki articles yourself. Just log in with your Qt Account.
@jsulm said in Typo found online:

You should file a bug report here: https://bugreports.qt.io/secure/Dashboard.jspa
This is user forum without many developers working on Qt/documentation.

This is true for articles at https://doc.qt.io/
]]></description><link>https://forum.qt.io/topic/135085/typo-found-online</link><guid isPermaLink="true">https://forum.qt.io/topic/135085/typo-found-online</guid><dc:creator><![CDATA[JKSH]]></dc:creator><pubDate>Wed, 16 Mar 2022 01:44:46 GMT</pubDate></item><item><title><![CDATA[Source code for pyside6-lupdate?]]></title><description><![CDATA[For future reference, I am going to answer my own question: pyside6-lupdate is the same thing as the main Qt Linguist lupdate, so its source is located at https://code.qt.io/cgit/qt/qttools.git, and more specifically https://code.qt.io/cgit/qt/qttools.git/tree/src/linguist/lupdate . This appears to be based on the original "pylupdate" code, though it's been refactored a fair bit.
]]></description><link>https://forum.qt.io/topic/133914/source-code-for-pyside6-lupdate</link><guid isPermaLink="true">https://forum.qt.io/topic/133914/source-code-for-pyside6-lupdate</guid><dc:creator><![CDATA[Chris Hennes]]></dc:creator><pubDate>Fri, 28 Jan 2022 04:11:20 GMT</pubDate></item><item><title><![CDATA[How is QSqlTableModel ok?]]></title><description><![CDATA[@SGaist said in How is QSqlTableModel ok?:

the model shall be deleted before the QCoreApplication and thus its private part as well and thus the db object.

Not necessarily... for example
#include &lt;QApplication&gt;
#include &lt;QTableView&gt;
#include &lt;QSqlTableModel&gt;
#include &lt;memory&gt;
int main(int argc, char *argv[])
{
    std::unique_ptr&lt;QSqlTableModel&gt; model;
    QApplication a(argc, argv);
    QSqlDatabase db = QSqlDatabase::addDatabase(QStringLiteral("QSQLITE"));
    db.setDatabaseName(QStringLiteral("/path/to/mydb.sqlite"));
    Q_ASSUME(db.open());
    model = std::make_unique&lt;QSqlTableModel&gt;();
    model-&gt;setTable(QStringLiteral("MyTable"));
    Q_ASSUME(model-&gt;select());
    QTableView tableView;
    tableView.setModel(model.get());
    tableView.show();
    return a.exec();
}

Now we can agree that, in practice, it seldom happens but I still don't understand if the design choice opens up the problem without safeguards or warnings or if I'm just missing something that makes it ok.
]]></description><link>https://forum.qt.io/topic/132117/how-is-qsqltablemodel-ok</link><guid isPermaLink="true">https://forum.qt.io/topic/132117/how-is-qsqltablemodel-ok</guid><dc:creator><![CDATA[VRonin]]></dc:creator><pubDate>Thu, 18 Nov 2021 19:02:08 GMT</pubDate></item><item><title><![CDATA[How to have my .pro depend on qt.pro ?]]></title><description><![CDATA[Hi,
@davecotter said in How to have my .pro depend on qt.pro ?:

Third: what's the recommendation about -developer-build ? I understand that regardless of "-prefix" setting, it will build within the Src tree, which is exactly what you do NOT want assuming you're using Git to submit your changes?

Out of source builds are the key.
@davecotter said in How to have my .pro depend on qt.pro ?:

Fourth: the .pro.user file is created within the Src tree, which is not okay with Git. How do i force Qt Creator to put that somewhere else?

Usually ignored by the .gitignore file.
@davecotter said in How to have my .pro depend on qt.pro ?:

Fifth: assuming all the above gets straightened out, when i build in Qt Creator, note i do not do "make install". does that happen automatically? do i need a "post build step" on the "qtmultimedia/src" project to stage that into place for debug builds?

You need a custom build step indeed.
]]></description><link>https://forum.qt.io/topic/128107/how-to-have-my-pro-depend-on-qt-pro</link><guid isPermaLink="true">https://forum.qt.io/topic/128107/how-to-have-my-pro-depend-on-qt-pro</guid><dc:creator><![CDATA[SGaist]]></dc:creator><pubDate>Thu, 01 Jul 2021 19:00:14 GMT</pubDate></item><item><title><![CDATA[can&#x27;t debug hand-built Qt Frameworks]]></title><description><![CDATA[AFAIK, it should not.
Did you try to do a clean rebuild ?
]]></description><link>https://forum.qt.io/topic/128034/can-t-debug-hand-built-qt-frameworks</link><guid isPermaLink="true">https://forum.qt.io/topic/128034/can-t-debug-hand-built-qt-frameworks</guid><dc:creator><![CDATA[SGaist]]></dc:creator><pubDate>Tue, 29 Jun 2021 15:36:16 GMT</pubDate></item><item><title><![CDATA[build from source: contradictory instructions]]></title><description><![CDATA[yeah, kay. thanks for bearing with me, i've never done this before!
:D
]]></description><link>https://forum.qt.io/topic/128003/build-from-source-contradictory-instructions</link><guid isPermaLink="true">https://forum.qt.io/topic/128003/build-from-source-contradictory-instructions</guid><dc:creator><![CDATA[davecotter]]></dc:creator><pubDate>Mon, 28 Jun 2021 21:03:31 GMT</pubDate></item><item><title><![CDATA[Building Qt source: error right at end :(]]></title><description><![CDATA[the answer was i was building the wrong branch. switched to 5.15.2 and all is well.
]]></description><link>https://forum.qt.io/topic/127971/building-qt-source-error-right-at-end</link><guid isPermaLink="true">https://forum.qt.io/topic/127971/building-qt-source-error-right-at-end</guid><dc:creator><![CDATA[davecotter]]></dc:creator><pubDate>Sun, 27 Jun 2021 22:59:00 GMT</pubDate></item><item><title><![CDATA[GPush &quot;Please specify exact ranges&quot;]]></title><description><![CDATA[<p dir="auto">Posting here as it was requested recently and I myself struggled for a long time against this error, hoping future googlers won't have take that long to decrypt this error message.<br />
If after calling <code>gpush --branch dev</code> to push a change to gerrit you get an error asking you to "Please specify exact ranges" all you have to do is add <code>..</code> at the end: <code>gpush --branch dev ..</code></p>
]]></description><link>https://forum.qt.io/topic/127968/gpush-please-specify-exact-ranges</link><guid isPermaLink="true">https://forum.qt.io/topic/127968/gpush-please-specify-exact-ranges</guid><dc:creator><![CDATA[VRonin]]></dc:creator><pubDate>Sun, 27 Jun 2021 15:11:05 GMT</pubDate></item><item><title><![CDATA[Build Qt Source (mac): &#x27;make&#x27; immediately hits an error ?]]></title><description><![CDATA[yes, i upgraded to xcode 10 and it started working
]]></description><link>https://forum.qt.io/topic/127961/build-qt-source-mac-make-immediately-hits-an-error</link><guid isPermaLink="true">https://forum.qt.io/topic/127961/build-qt-source-mac-make-immediately-hits-an-error</guid><dc:creator><![CDATA[davecotter]]></dc:creator><pubDate>Sat, 26 Jun 2021 22:27:28 GMT</pubDate></item><item><title><![CDATA[blocked: cmake: command not found]]></title><description><![CDATA[@davecotter said in blocked: cmake: command not found:

cmake: command not found

here's what i ended up doing:

Launch "MaintenanceTool", and choose "Add or remove components" (next)
under "Qt -&gt; Developer and Design Tools", check "CMake" (next, and complete that)
in Terminal, ensure you add the folder containing cmake to your $PATH, eg: export PATH=$PATH:/path_to/Qt/Tools/CMake/CMake.app/Contents/bin

]]></description><link>https://forum.qt.io/topic/127960/blocked-cmake-command-not-found</link><guid isPermaLink="true">https://forum.qt.io/topic/127960/blocked-cmake-command-not-found</guid><dc:creator><![CDATA[davecotter]]></dc:creator><pubDate>Sat, 26 Jun 2021 20:57:26 GMT</pubDate></item><item><title><![CDATA[do i really need two SSH keys?]]></title><description><![CDATA[i think you should move steps 6 and 7 from the top, and integrate them into the bottom, or really just make it one list, no need for separate sections
]]></description><link>https://forum.qt.io/topic/127959/do-i-really-need-two-ssh-keys</link><guid isPermaLink="true">https://forum.qt.io/topic/127959/do-i-really-need-two-ssh-keys</guid><dc:creator><![CDATA[davecotter]]></dc:creator><pubDate>Sat, 26 Jun 2021 20:14:08 GMT</pubDate></item><item><title><![CDATA[branch from origin&#x2F;dev or gerrit&#x2F;dev?]]></title><description><![CDATA[No, you just need a remote repository called gerrit where gpush will push the changes to, you can ignore it and just work with code from origin
]]></description><link>https://forum.qt.io/topic/127958/branch-from-origin-dev-or-gerrit-dev</link><guid isPermaLink="true">https://forum.qt.io/topic/127958/branch-from-origin-dev-or-gerrit-dev</guid><dc:creator><![CDATA[VRonin]]></dc:creator><pubDate>Sat, 26 Jun 2021 20:09:25 GMT</pubDate></item><item><title><![CDATA[how to set the connect blocking time when use QSqlDatabase::open()?]]></title><description><![CDATA[i did a lot google，but maybe i ignore something.
thank you bro！it help
]]></description><link>https://forum.qt.io/topic/122688/how-to-set-the-connect-blocking-time-when-use-qsqldatabase-open</link><guid isPermaLink="true">https://forum.qt.io/topic/122688/how-to-set-the-connect-blocking-time-when-use-qsqldatabase-open</guid><dc:creator><![CDATA[boom stack]]></dc:creator><pubDate>Thu, 14 Jan 2021 03:17:17 GMT</pubDate></item></channel></rss>