Hi Bill, I've updated the jtsdk-wsjtx build script (not committed to svn yet) to use getopts and have enabled (4) options for command line use. This should cover most of the commonly used build constructs. I think I have my terminology correct now with how CMake views things.
Usage ...: jtsdk-wsjtx [-h] [-b] [-n] [-c] [-t] Example..: jtsdk-wsjtx -b dev -n wsjtx -c release -t install -h Displays the help message -b ( dev | gar ) dev = development branches ^/branches gar = GA and RC branches ^/tags -n Branch Name: wsjtx, wsjtx-1.6, wsjtx-1.6.0-rc1, etc -c Cmake Build Type: release | debug -t Cmake Target: install package docs | user-defined Details: -b will fail if the input is not one of two values ( dev | gar ). -n names are generated from svn directly for both ^/branchs and ^/tags. Validation will fail if the branch name is not in the lookup array. The user will then see a list of what is available to build based on their -b setting. -c will default to Release is not specified. Debug and Release have their own build trees as well as the accompanying install locations. -t install package and docs will run be installed locally, where User-Defined target built then left in the build tree. Docs would be left in the build tree also, if that is what is desired. Other Items: I have not implemented 'svn sw' yet, as it performs an update when switching between branches, which I am not sure is a desired artifact and would need to be manages closely when errors / user interrupts occur. I've also added a few alias command-line examples in a Here-Doc. Users can simply source the file and test them out or add the soure to their .bashrc, instruction for both are in the Here-Doc. I think that covers most of the feedback I've gotten thus far. There are a couple other things I'd like to add going forward; Configure only for use with Cmake-GUI, Build (re-compile) only things like that, but those can be added in later versions. After testing today, I'll commit the changes so others can have a look and test things out. 73's Greg, KI7MT On 12/21/2015 12:50 PM, Bill Somerville wrote: > On 21/12/2015 19:43, KI7MT wrote: >> OK, that makes sense to what I am seeing. I may need to add another >> option for single target builds so it uses either Debug or Release >> configuration. >> >> When your doing / testing single target builds, do you typically >> configure it with Debug or do you maintain separate build trees for >> Debug and Release? > > Hi Greg, > > there are some configuration details that are not mutable, the overall > build configuration is the main one of those. You must have separate > build trees for each configuration i.e. Release, Debug, etc... > > It is possible to use the same build tree for different branches, this > works because svn/git update the modification dates of files checked > out. I usually have one build tree for each of Debug and Release > configuration and use 'svn sw' and 'git checkout' to move my single > source trees between branches. It does mean somewhat larger than > necessary builds when I switch branches but that is a small price that > is offset by the space saving and uniformity of commands I use to build > and test. > > 73 > Bill > G4WJS. > > ------------------------------------------------------------------------------ > _______________________________________________ > 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
