Hi Bill, Thanks for the feedback.
I still need to update the jtsdk-wsjtx-sb script so it too will take command line input the way jtsdk-wsjtx does now; that should not be too much trouble. I did notice, with the exception of targets residing in sub-folders ( manpages, docs, etc ), Cmake will build the entire project if try to install just a single target. With the sub-folder targets, you can use the Makefile that is generated to perform an install if desired. So for the time being, I've left the out the --target install step for single target builds. They all seem to work properly in the Build Directory. Adding these capabilities to JTSDK-Win32 may prove to be a bit more challenging, but I think I can be done. 73's Greg, KI7MT On 12/21/2015 05:13 AM, Bill Somerville wrote: > On 21/12/2015 05:48, KI7MT wrote: >> Question: For single target builds, does there need to be an install >> step or is compiling it good enough? >> > ... >> 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. > > Hi Greg, > > currently the install step is required for wsjtx, most other targets are > either runnable from the build tree or do not produce executable > artefacts. Some are more useful not installed, for example building the > User Guide always creates the same document name in the build tree > 'wsjtx-main.html' but it gets renamed on install, in this case the build > tree version is handy to bookmark in a browser for review. Many targets > do not get installed like test tools, the jt*sim tools are good examples > of these. In other cases you might have WIP and the build is broken, you > may want to restrict the build to a smaller part than the full install. > > The install target builds the 'all' target and then the 'install' > target, obviously 'all' has many dependencies that will also get built > if they are out of date. > > So summarizing a developer may want to anything from a single source > file, library or document through to the final install package. > > It is on my list to make sure that everything can be run from the build > tree so that install builds are only needed to do test installs or for > day to day use and testing. Until recently kvasd was a complication but > that and the plan to do away with separate sub-processes like jt9 in the > final product should simplify this. > > I like what you have done with this, I think that JTSDK is moving to a > good place where developers can use it as a serious build tool without > losing the efficiency and power of the CMake build script. > > 73 > Bill > G4WJS. ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
