Hi Bill, See below.
On 11/21/2015 14:36, Bill Somerville wrote: > On 21/11/2015 21:29, Greg Beam wrote: >> Hi Bill, > Hi Greg, >> >> That is where I made it too last time around. If the ^/build folder was >> previously configured, things are OK, if not, I can't seem to pass it >> the tool-chain file and all the rest. Basically, I had to go through and >> set everything manually, which is allot really. > Somewhere in your script workflow you are enforcing something that is > not right. A build tree should be configured exactly once. Once > configured it can be built (cmake --build <build-tree-root> ...) and it > can have CMake options changed. So it only makes sense to utilize > cmake-gui on a configured build tree to change CMake options. I may have mixed my words in writing, but I understand what your saying here. I maintain a separate build trees for Release and Debug in the scripts, overkill - probably, but it ensures the defaults are always in the same place. > > Perhaps you are confusing CMake variables and CMake options. Variables > are set by configure, with the exception that variables for packages > that are missing will be set by the first build after after the package > is installed. Users can do what your describing here already. But, they need a ^/build tree first, as you stated above. The only thing the rconfig section does not do is take input parameters, it uses a set of defaults. Assuming they've never configured wsjt-x before, on a brand new JTSDK install, for wsjtx v1.7.0, they need srcs and create the ^/build tree first: 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. 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. 73's Greg, KI7MT >> >> 73's >> Greg, KI7MT > 73 > Bill > G4WJS. >> >> On 11/21/2015 13:45, Bill Somerville wrote: >>> On 21/11/2015 20:40, Greg Beam wrote: >>>> Yes, I agree. I have put some thought into that but was never able to >>>> pass parameters to cmake-gui properly, do you know where those docs are >>>> for that specifically? >>> Hi Greg, >>> >>> it takes a single optional argument which is the build tree root >>> directory, something like: >>> >>> $ cmake-gui ~/wsjtx-dev-prefix/build/debug >>> >>> 73 >>> Bill >>> G4WJS. ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
