On 21/11/2015 22:33, Greg Beam wrote: Hi Greg,
> checkout-wsjtx > build-wsjtx rconfig > cmake-gui C:\JTSDK\wsjtx\build\Release > > * edit whatever they like, generate to save > > cd /D .\wsjtx\build\Release > cmake --build . --target <X.Y.Z> > > The only thing that does not do is separate the output directory from > what a straight through build using : build-wsjtx rinstall, however, you > could, through the use of cmake-gui, change that. I never change the source or output directories when using cmake-gui. I'm not sure what happens if you do change the source directory, I guess it configures it using the existing CMakeCache variables. Changing the output directory could be handy if you want to do a series of build with different options. For WSJT-X I suspect that changing options only make most sense. > > If I'm not mistaken, that is what is needed. However, the user needs to > keep track of how the ^/build tree is configured, install locations, > options etc. I keep two pairs of build trees, one for Debug/Release configuration of the active release branch and the other for Debug/Release of the development branch. that seems to cover all eventualities for someone who does work on the trunk and release branches. For a non-developer a single build tree of a release configuration of development is probably enough. 73 Bill G4WJS. ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
