On Friday 29 January 2016 10:42:17 Hausmann Simon wrote:
> You're right, the can is open right now. Apple is working on closing that
> can under our feet (see the DYLD_* variable unsetting upon exec in 10.11).
> I wouldn't be surprised if that trend continues elsewhere
ld-linux.so ignores the LD_*
behalf of Koehne Kai
Sent: Friday, January 29, 2016 9:10
To: André Somers; development@qt-project.org
Subject: Re: [Development] Modify QLibraryInfo to support any default location
of qt.conf
> -Original Message-
> From: Development [mailto:development-boun...@qt-project.org] On
&
> -Original Message-
> From: Development [mailto:development-boun...@qt-project.org] On
> Behalf Of Andre Somers
> Sent: Friday, January 29, 2016 9:05 AM
> To: development@qt-project.org
> Subject: Re: [Development] Modify QLibraryInfo to support any default
>
Op 28/01/2016 om 13:00 schreef Maximilian Hrabowski:
Why isn't this first ?
I would generally expect an environment variable to take precedence over
all other configuration options except command-line options.
You are right, that an environment variable should be considered first. But I
think
>>> 2. Also lookup qt.conf in all of QLibraryInfo::libraryPaths() (this is
>>> how we got the plugins found)
>>
>> Potentially problematic if plugins might install a qt.conf that isn't
>> what your application needs.
>
> I have full control of the content of my application bundle and the
> libraryP
> Am 28.01.2016 um 11:38:26 schrieb Oswald Buddenhagen
> :
>
> 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
>> QSett
> Am 28.01.2016 um 11:54:02 schrieb Welbourne Edward
> :
>
> Maximilian Hrabowski (28 January 2016 10:47):
>> What we need is a way to look up the qt.conf at another location as well.
> [...]
>> I thought about the following ways (order gives my personal opinion’s
>> priority):
>>
>> 1. Add a
Hi,
this is the same problem that the Qt installation program has, it solves
it by binary patching your copy of Qt5Core.dll when it installs Qt onto
your computer (e.g. set qt_prfxpath="C:\Qt\5.5\msvc2013").
Maybe you can to the same?
Or perhaps a more viable long-range solution is to introd
Maximilian Hrabowski (28 January 2016 10:47):
> What we need is a way to look up the qt.conf at another location as well.
[...]
> I thought about the following ways (order gives my personal opinion’s
> priority):
>
> 1. Add a new public API: static void QLibraryInfo::setQtConfFilePath(
> const QSt
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-co
Hi,
our application has an auto-update feature that allows to download and install
a new version of the application. The update package includes everything, also
Qt. The only permanent files are a launcher executable and a config file that
points to the real application folder. The folder which
11 matches
Mail list logo
