Hi Bill, 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.
Yes, I don't know why I stuck it in there as "doc" v.s. docs, as the build command is calling "docs". I'll fix that. This is what that case calls: cmake --build . --target docs 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 tried that already, make(space)(tab)(tab), it gave me: Display all 568 possibilities? (y or n) Obviously I said no :-) I spent a good deal of time trying to do just that, parse the Makefile or figure out a way to have CMake tell me what targets were available. I eventually settled on hard coding the 4 targets as that's what most but certainly not all folks would want to use regularly. > 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. I'll look at making $3 accept either NULL then default to Release or set whatever the user sticks in it and let Cmake sort it out from there. > > 73 > Bill > G4WJS. 73's Greg, KI7MT ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
