[cmake-developers] Controlling CMake GUI source/build directory from CLI

Venedict Tchistopolskii venytch at gmail.com
Fri Jan 25 15:55:34 EST 2019


Cherry picked and tested. Works great, thank you!

Now, if only the source/build path would stick around, without requiring
config to be triggered. :P

On Fri, Jan 25, 2019 at 8:56 AM Kyle Edwards <kyle.edwards at kitware.com>
wrote:

> Venedict,
>
> Currently, cmake-gui only lets you specify a build or source directory,
> not both.
>
> I've opened https://gitlab.kitware.com/cmake/cmake/merge_requests/2863 to
> add explicit -S and -B options to cmake-gui, which will allow you to
> specify both.
>
> Kyle
>
> On Fri, 2019-01-25 at 08:10 -0800, Venedict Tchistopolskii wrote:
>
> Actually that doesn't work.....
> *cmake-gui.exe "D:/GitHub/SOURCE" "D:/GitHub/SOURCE/solutions_cmake/win64"*
>
> Ignores both options, but
> *cmake-gui.exe "D:/GitHub/SOURCE"*
>
> Uses current directory as noted. Why? Syntax wrong or something?
>
> VT
>
>
> On Fri, Jan 25, 2019 at 6:52 AM Kyle Edwards <kyle.edwards at kitware.com>
> wrote:
>
> On Fri, 2019-01-25 at 09:18 +0100, Gößwein Matthias / eeas gmbh wrote:
> > However, the manual does not describe this behavior, maybe it should
> > be
> > mentioned there.
> > (https://cmake.org/cmake/help/v3.13/manual/cmake-gui.1.html)
>
> Even better, perhaps we should add explicit -B and -S options the way
> cmake and ccmake already do.
>
> Kyle
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cmake.org/pipermail/cmake-developers/attachments/20190125/3d070fdd/attachment.html>


More information about the cmake-developers mailing list