The problem is the JTSDK-Nix build script is pulling from the wrong location when constructing the release candidate branch, but I've not looked at it closely.
See comment below On 12/12/2015 05:32 AM, Bill Somerville wrote: > On 12/12/2015 12:26, Bill Somerville wrote: >> what does 'svn info' show for each of the source areas? > Hi again, > > sorry, that probably does make sense. > > Does the "Superbuild" option just make a source tarball or does it build > the application? It does both, to allow testing of the tarball the Superbuild script produces, however, this feature is going to get pulled out anyway, as it's just too much to keep up with when things change in the repositories, the same for JTSDK-Nix as a whole; its going to build the development branches and that is it. > > The superbuild is mostly used now to make a source tarball for use by > Linux users and packagers. The source tarball does not have svn revision > information as it is self-contained. In the build tree for each > superbuild there is a source tree at: > > .../wsjtx-prefix/src/wsjtx > > if you 'cd ' to there you can do 'svn info' to see exactly what has been > checked out for the build. > > The Hamlib component is similar but is a git checkout in: > > .../hamlib-prefix/src/hamlib > > use 'git status' to identify that one. > > 73 > Bill > G4WJS. > ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
