Hi Bill, A couple updates.
1. As advised, I've removed the maintainer functions and menu entries. 2. I have single target build working as expected. I tested jt9sim, jt65sim, jt65, jt65code, jt4sim, etc, but, I am not running install after compiling the target, and the build directory is separate from what would normally be a release Debug or Release Target. Question: For single target builds, does there need to be an install step or is compiling it good enough? I used the following in a bash shell to test: yes |jtsdk-wsjtx dec wsjtx jt65 yes n |jtsdk-wsjtx dec wsjtx jt65sim etc etc etc After thinking about the alias commands a bit more, one could use many variations, things like: To auto update from SVN: alias build-wsjtx="yes |jtsdk-wsjtx dev wsjtx $1" Then: build-wsjtx jt65sim To *not* auto update from SVN: alias build-wsjtx="yes n |jtsdk-wsjtx dev wsjtx $1" Then: build-wsjtx jt65sim Or one can use a combination of the above with the $@ operator or even hard code several targets. I looked though the target list from make(space)(tab)(tab), there are a number of targets that could be useful in development turns, if folks new about them and how to build them easily. 73's Greg, KI7MT On 12/20/2015 05:54 PM, Bill Somerville wrote: > On 21/12/2015 00:36, KI7MT wrote: >> It would not be too difficult to make $3 accept anything, but if it's >> entered wrong, the build would fail in the cmake configure stage. > That's not a build then it's a configure. I am confused by your examples > as you mentioned and example to build 'doc' but there is no build target > call 'doc'. There is a build target called 'docs' along with many > others. Unfortunately neither CMake nor GNU make have a facility for > listing all targets. You can see the available targets using bash > command line completion (assuming you have the relevant make command > line completion installed), like this: > > $ cd <build-root> > $ make(space)(tab)(tab) > > I'm not suggesting we should codify these hundreds of targets or even > provide a way of dynamically listing them, after all bash command line > completion does the job just fine already. My point is that all of those > targets are valid and might be used by a developer to do some relevant > fragment of the build. > > 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
