RR, 4427 is OK.
But if LIBRARY_PATH defined to be a NULL string, why include it in PATH
at all?
-- Joe
On 10/1/2014 2:40 PM, KI7MT wrote:
> Hi Joe,
>
> Yes, it did here too. Had to move the %LIBRARY_PATH% to the end of the
> %PATH%
>
> Should be ok now, I just built WSPR and WSJT-X
>
> 73's
> Greg, KI7MT
>
>
>
>
> On 10/1/2014 18:34, Joe Taylor wrote:
>> Greg --
>>
>> SVN revisions 4425 and 4426 break everything here.
>>
>> I think all that's needed is
>>
>> SET LIBRARY_PATH=""
>>
>> in jtsdk-qtenv.bat, and possibly also in jtsdk-pyenv.bat. Don't put
>> LIBRARY_PATH into PATH... they're two different things. You don't use
>> LIBRARY_PATH anywhere in your scripts, but some of the tools do. We
>> want it defined as NULL, even if a user normally has it set otherwise
>> (for use in other environments).
>>
>> -- 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
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
