From: KI7MT <ki...@ya...> - 2014-10-01 18:03:16
|
Hi Joe, Setting to null would correct any inadvertent settings of the Path elsewhere I would think. The other question is, how is that getting in there to begin with if the env / build script is not, or should not, be picking up any of the local env variables. Can you add it to jtsdk-qtenv.bat, jtsdk-cmake.bat and jtsdk-wsjtxrc.bat then test it to see the results, as I would not be able to test it properly from my end? I remember when we were using G95, that was one thing it wanted was to set the Lib_PATH's, but I don't recall any such requirement for Qt5 Tool-Chains. I also used RapidEE from the ..\tools directory to ensure the system variables were clean. 73's Greg, KI7MT On 10/1/2014 17:41, Joe Taylor wrote: > Greg -- > > I finally spent the necessary time to find out why builds of WSJT-X on > one of my shack computers stopped working, a couple of weeks ago. > > Turns out that the machine in question has environment variable > LIBRARY_PATH set as follows, at login: > > LIBRARY_PATH=c:\mingw\lib;c:\mingw\lib\gcc-lib\i686-pc-mingw32\4.0.3 > > Obviously this is not good for builds in the JTSDKs! > > I suggest you put the following somewhere in jtsdk-qtenv.bat: > > SET LIBRARY_PATH="" > > Does this make sense? > > -- Joe > > ------------------------------------------------------------------------------ > 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 > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- 73's Greg, KI7MT |