<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">There is cmake **build** step: cmake
--build _builds<br>
<br>
So in GUI it's:<br>
* cmake configure<br>
* cmake generate<br>
* IDE build (which you can do with cmake --build so it can be
called "cmake build" step)<br>
<br>
in cmd:<br>
* cmake configure+generate<br>
* cmake build<br>
<br>
Also I can call it "cmake step" in docs about some C++ project,
but if the docs about cmake itself I think this term is too wide<br>
<br>
On 25-Jun-16 02:13, Craig Scott wrote:<br>
</div>
<blockquote
cite="mid:CA+dygY=ramopUC1kv+d_M-4h17wRa5swh6LdEsUj1YdGh9skRQ@mail.gmail.com"
type="cite">In documentation, blog articles, etc. I just call it
the "cmake" step (or sometimes the "project setup" step if talking
in a more project-wide sense). For many users, the separate
configure and generate steps are somewhat of an implementation
detail, so it makes more sense to give it a single term. I'm not
aware of any generally accepted term, but the ones I use seem to
be fairly easy to understand, especially for those new to CMake.
YMMV.<br>
<br>
On Saturday, 25 June 2016, Ruslan Baratov via CMake <<a
moz-do-not-send="true" href="mailto:cmake@cmake.org"><a class="moz-txt-link-abbreviated" href="mailto:cmake@cmake.org">cmake@cmake.org</a></a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On 24-Jun-16
23:49, Robert Maynard wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Please run the configure and generate steps by<br>
</blockquote>
It's too long :)<br>
<br>
Also it doesn't express the fact that it's a single action,
consider:<br>
"To add variables on configure and generate steps use '-D'"<br>
"Before running configure and generate steps note that old
variables from cache can be used"<br>
etc.<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On Fri, Jun 24, 2016 at 4:40 PM, Ruslan Baratov<br>
<<a moz-do-not-send="true">ruslan_baratov@yahoo.com</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On 24-Jun-16 23:25, Robert Maynard wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
cmake from the command line is still running the two
stages, it just<br>
doesn't allow for feedback/input from the user between the
two stages.<br>
</blockquote>
Yes, I understand that. Question is about the name of the
step. I.e. when I<br>
do write manual what should I choose<br>
Please run configure step by: cmake -H. -B_builds<br>
or<br>
Please run generate step by: cmake -H. -B_builds<br>
?<br>
<br>
May be both versions are correct? Or both incorrect?<br>
<br>
Ruslo<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On Fri, Jun 24, 2016 at 4:06 PM, Ruslan Baratov via CMake<br>
<<a moz-do-not-send="true">cmake@cmake.org</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
I have a question about CMake terminology. When we are
using CMake GUI<br>
there<br>
are two buttons "Configure" and "Generate", hence we
have two stages:<br>
<br>
1. Configure step, when we do configuring project,
effectively creating<br>
file<br>
with cache variables (which we can modify) without
really generating<br>
native<br>
tools files like Makefile/*.sln/etc.<br>
<br>
2. Generate step, when we do generating project using
file with cache<br>
variables, i.e. create those Makefile/*.sln/etc.<br>
<br>
The question is about command line version of CMake.
Since we do creating<br>
file with cache and generate native tools files in one
step what is the<br>
right term? Is it a configure step because we read
user's '-D' and create<br>
cache file? Is it a generate step because native tools
files generated<br>
at<br>
the end? May be there is a third name to describe the
fact that it's<br>
configure+generate step?<br>
<br>
Thanks, Ruslo<br>
--<br>
<br>
Powered by <a moz-do-not-send="true"
href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ
at:<br>
<a moz-do-not-send="true"
href="http://www.cmake.org/Wiki/CMake_FAQ"
target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Kitware offers various services to support the CMake
community. For more<br>
information on each offering, please visit:<br>
<br>
CMake Support: <a moz-do-not-send="true"
href="http://cmake.org/cmake/help/support.html"
target="_blank">http://cmake.org/cmake/help/support.html</a><br>
CMake Consulting: <a moz-do-not-send="true"
href="http://cmake.org/cmake/help/consulting.html"
target="_blank">http://cmake.org/cmake/help/consulting.html</a><br>
CMake Training Courses: <a moz-do-not-send="true"
href="http://cmake.org/cmake/help/training.html"
target="_blank">http://cmake.org/cmake/help/training.html</a><br>
<br>
Visit other Kitware open-source projects at<br>
<a moz-do-not-send="true"
href="http://www.kitware.com/opensource/opensource.html"
target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a moz-do-not-send="true"
href="http://public.kitware.com/mailman/listinfo/cmake"
target="_blank">http://public.kitware.com/mailman/listinfo/cmake</a><br>
</blockquote>
</blockquote>
<br>
<br>
</blockquote>
</blockquote>
<br>
-- <br>
<br>
Powered by <a moz-do-not-send="true"
href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a
moz-do-not-send="true"
href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank"><a class="moz-txt-link-freetext" href="http://www.cmake.org/Wiki/CMake_FAQ">http://www.cmake.org/Wiki/CMake_FAQ</a></a><br>
<br>
Kitware offers various services to support the CMake community.
For more information on each offering, please visit:<br>
<br>
CMake Support: <a moz-do-not-send="true"
href="http://cmake.org/cmake/help/support.html"
target="_blank">http://cmake.org/cmake/help/support.html</a><br>
CMake Consulting: <a moz-do-not-send="true"
href="http://cmake.org/cmake/help/consulting.html"
target="_blank">http://cmake.org/cmake/help/consulting.html</a><br>
CMake Training Courses: <a moz-do-not-send="true"
href="http://cmake.org/cmake/help/training.html"
target="_blank">http://cmake.org/cmake/help/training.html</a><br>
<br>
Visit other Kitware open-source projects at <a
moz-do-not-send="true"
href="http://www.kitware.com/opensource/opensource.html"
target="_blank"><a class="moz-txt-link-freetext" href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a></a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a moz-do-not-send="true"
href="http://public.kitware.com/mailman/listinfo/cmake"
target="_blank">http://public.kitware.com/mailman/listinfo/cmake</a><br>
</blockquote>
<br>
<br>
-- <br>
<div dir="ltr">
<div>
<div dir="ltr">Craig Scott<br>
<div>Melbourne, Australia</div>
<div><a moz-do-not-send="true" href="http://crascit.com"
target="_blank">http://crascit.com</a><br>
</div>
</div>
</div>
</div>
<br>
</blockquote>
<p><br>
</p>
</body>
</html>