Hi Bill, On 10/1/2014 18:35, Bill Somerville wrote:
<snip> >> So for the Debug builds, are you saying we don't need to copy the >> runtime .dll's over too the install\bin directory ? > Yes, that's the way it works for me. > > Yuck! I hate Windows. I've just checked using the dependency walker and > it is indeed using PATH to locate the Qt debug DLLs at run time. Yes, that's how I figured out what needed, so I copied them over. +1, I'm not a fan of Windows either :-). > > I have my Qt bin directory in my PATH when I debug or run debug builds > of WSJT-X. I think that is preferable to copying around the rather large > debug DLLs and plugins. Having said that, you must have the same on your > PATH at build time to get the Qt tools used by the build like moc, rcc, > uic, dumpcpp and, qmake. I use the same PATH settings for building, > running and, debugging. > > My initial statement is correct for Linux and Mac but on Windows it > appears some help for the image loader is required. >> >> 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. OK, We can do that with a batch file easy enough. >> >>> For Release configuration builds all shared libraries and Qt plugins are >>> either installed by the install phase or on Linux located from the >>> system directories in their "normal" place. Any fix ups needed to make >>> the resulting package portable are done by the build process. So no >>> setting of LIBRARY_PATH/LD_LIBRARY_PATH/DYLD_LIBRARY_PATH or similar >>> environment variables should ever be needed. This applies to RPATH >>> embedded in Linux executabes and shared libraries too. >>> >>> All of the above applies on all platforms. >>>> -- Joe >>> 73 >>> Bill >>> G4WJS. > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- 73's Greg, KI7MT ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
