On Fri, 2019-01-25 at 14:06 -0800, Venedict Tchistopolskii wrote:
> Could you clarify on saving the build-directory section?
>
> I'm not sure how it knows which cache or build directory to load. In
> my setup here the issue I noted applies even if build directory is
> generated on both projects/et
Gagh I'm stupid, missed the drop down, thanks for clarifying!
Much better now :)
VT
On Fri, Jan 25, 2019 at 2:48 PM Kyle Edwards
wrote:
> On Fri, 2019-01-25 at 14:06 -0800, Venedict Tchistopolskii wrote:
>
> Could you clarify on saving the build-directory section?
>
> I'm not sure how it knows
Could you clarify on saving the build-directory section?
I'm not sure how it knows which cache or build directory to load. In my
setup here the issue I noted applies even if build directory is generated
on both projects/etc.
VT
On Fri, Jan 25, 2019 at 1:59 PM Kyle Edwards
wrote:
> On Fri, 2019
On Fri, 2019-01-25 at 13:23 -0800, Venedict Tchistopolskii wrote:
> Get 2 CMake projects.
>
> Get CMake GUI to 'configure' one of them. Close/re-open and it will
> automatically point to this configured project source and build
> locations, regardless of what build/version/cmake-gui.exe you use.
Get 2 CMake projects.
Get CMake GUI to 'configure' one of them. Close/re-open and it will
automatically point to this configured project source and build locations,
regardless of what build/version/cmake-gui.exe you use.
Run a different cmake-gui.exe through the CLI, passing in source and build
l
On Fri, 2019-01-25 at 12:55 -0800, Venedict Tchistopolskii wrote:
> Cherry picked and tested. Works great, thank you!
Great, glad to hear it!
> Now, if only the source/build path would stick around, without requiring
> config to be triggered. :P
Can you clarify what you mean by this?
Kyle
>
--
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
wrote:
> Venedict,
>
> Currently, cmake-gui only lets you specify a build or source directory,
> not
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
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
wrote:
> O
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
Dear Venedict,
Yes, that ist possible. Basically the syntax for cmake-gui is:
cmake-gui [] ( | )
So you can either pass a source directory or a build directory where
cmake was already run.
If you pass the path to the source directory as parameter, then cmake
uses the current directory as build
11 matches
Mail list logo
