Hi Bill, On 5/27/2015 3:59 PM, Bill Somerville wrote: > On 27/05/2015 22:50, KI7MT wrote: >> Hi Bill, > Hi Greg, >> Currently, we have the path to AsciiDoc & Python2 in the tool-chain >> file, which I think that is where it is supposed to go. The paths to >> Python2 and AsciiDoc are not in the JTSDK-QT ENV or Build script >> %PATH% to prevent potential collisions with Python3 native or JTSDK >> installations. > That's correct. >>> Currently the doc/CMakeLists.txt fails with a fatal error message if an >>> asciidoc executable cannot be located. What are you looking for over and >>> above that? >> That was what I was hoping to prevent, the fatal error, rather, simply >> display the message that it wasn't found, and continue to build the app, >> or if it was found, things are OK and display the found message. If the >> doc portion of the build is deemed critical, then I suppose it's OK as is. > The way I look at it is that the build script in its default form is > supposed to build the final product in its entirety. For things that are > deemed optional for developers there are CMake options that can be set > to change the way they are built or not built. In this case the > WSJT_GENERATE_DOCS option applies and builders have the option to turn > it off. > > I will change the fatal error message to make it clearer that the docs > build is optional and how to turn it off.
Ok, thank you. With you all moving the apps over to QT rather, that dramatically simplifies things for the Windows SDK. There are a few other itmes that I wanted to ask you about regarding the Tool Chain file but I can do that closer to the time when JTSDK v2.1 is being put together. > > 73 > Bill > G4WJS. 73's Greg, KI7MT ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
