Hi Greg, I refer to qtenv-build-wsjtx.cmd this is a my typo
The script is only partially evolved on problem. As manual modification of script do not full solve the problem some search bring me to CMakeLists.txt: # # decide if we are bundling kvasd (non-FOSS) # CMAKE_DEPENDENT_OPTION (WSJT_INCLUDE_KVASD "Include kvasd in the package." OFF "NOT is_debug_build" ON) So seems that in debug the kvasd is downloaded. Probably the kvasd full removing is a "next step" but the new decoder work better. 73's Sandro IW3RAB Il 18/11/2015 16:01, Greg Beam ha scritto: > Hi Sandro, > > First, KVASD is not longer needed for ^\branches\wsjtx (ex v1.6.1, now > v1.7.0), which is built with qtenv-wsjtx.cmd, so that need to be > removed, though I don't think it's hurting anything to have it download > in the meantime. That was an oversight on my part and will be removed on > the next update. > > This command / file: qtenv-build-wsprx.cmd has nothing to do with WSJTX. > Did you find a place where this is being called out in the WSJT-X build > scripts ? > > > 73's > Greg, KI7MT > > On 11/18/2015 04:10, Alessandro Gorobey wrote: >> Hi All, >> >> I have a misunderstanding on win32 build scripts. >> build-wsjtx (qtenv-build-wsprx.cmd) have reintroduced in cmake -D >> WSJT_INCLUDE_KVASD=ON >> It is something desired or a typo? >> >> 73 >> Sandro >> IW3RAB > > ------------------------------------------------------------------------------ > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
