Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

[Bill S. <g4...@cl...>]

On 01/10/2014 19:35, Bill Somerville wrote:
> On 01/10/2014 19:18, KI7MT wrote:
>
>> I've been copying gcc & Qt5 runtime libs over because Qt5 is not in my
>> env %PATH% var (by design) otherwise I get Missing Lib errors when running.
> OK, I think you need to have the Qt bin directory in your path when you
> run Debug configured binaries. That's the way qt-project.org intend it
> to be.
Further to this: on Windows Qt installs, the reason Qt has all the Qt 
DLLs (debug and release) in the Qt bin directory along with the tools 
like moc, uic, rcc, qmake, dumpcpp, ... is that is their solution to 
testing Qt applications before deployment. You simply have the Qt bin 
directory on PATH and it all works without copying anything or setting 
any other environment variables.

I note that the JTSDK-QT adds the plugin directories to PATH as well. 
This has no effect because the plugins are located via hard coded paths 
in the Qt core DLL which are set up at install time (one of the reasons 
that moving the Qt install breaks it). This is necessary because the 
plugins are not loaded by the system loader, they are loaded explicitly 
by the Qt core library. Deployed applications have to be shipped with a 
qt.conf file which among other things is used to override the hard coded 
plugins path in the core library. We write a qt.conf file in Release 
configuration builds that refers to the plugin directory in the install 
destination.

<snip>

73
Bill
G4WJS.