[Development] Modify QLibraryInfo to support any default location of qt.conf

Maximilian Hrabowski hrabowski at clausmark.com
Thu Jan 28 13:13:52 CET 2016

> Am 28.01.2016 um 11:38:26 schrieb Oswald Buddenhagen <oswald.buddenhagen at theqtcompany.com>:
> On Thu, Jan 28, 2016 at 10:47:21AM +0100, Maximilian Hrabowski wrote:
>> 1. Add a new public API: static void QLibraryInfo::setQtConfFilePath( const QString& filePath) which defaults to ":/qt/etc/qt.conf“ and is used in QSettings *QLibraryInfoPrivate::findConfiguration() instead of the hard-coded path.
>> 2. Also lookup qt.conf in all of QLibraryInfo::libraryPaths() (this is how we got the plugins found)
>> 3. introduce an environment variable that points to the qt.conf similar to the one of QWebEngineProcess.exe
>> Please comment.
> you should contribute to
> https://bugreports.qt.io/browse/QTBUG-14150 getting fixed.
> that (specifically, subtask https://bugreports.qt.io/browse/QTBUG-15234)

QTBUG-15234 seems still be under discussion, right? 

> will make everything relative to the location of qtcore

This is indeed the best solution. I assume this solution could not be achieved before Qt 6?!

Maybe this would be another choice to get it to work with Qt 5.6 or at least Qt 5.7:
4. Determine the path from the current dll location as described in QtBUG-15234 at  Permalink <https://bugreports.qt.io/browse/QTBUG-15234?focusedCommentId=271523&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-271523>

> (or ideally,
> relative to the particular library which is doing the resource lookup).
> this will ultimately cause the disappearance of qt.conf, which sounds a
> lot better to me than either of your options.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160128/6bb56c01/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4293 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160128/6bb56c01/attachment.bin>

More information about the Development mailing list