On Tue, Jun 28, 2016 at 12:04 AM, Eric Noulard
wrote:
>
>
> 2016-06-25 17:42 GMT+02:00 Ruslan Baratov :
>
>> On 25-Jun-16 10:44, Craig Scott wrote:
>>
>> One of the slight wrinkles here is that the distinction between configure
>> and generation times is now a little stronger due to generator exp
2016-06-25 17:42 GMT+02:00 Ruslan Baratov :
> On 25-Jun-16 10:44, Craig Scott wrote:
>
> One of the slight wrinkles here is that the distinction between configure
> and generation times is now a little stronger due to generator expressions.
> In order to really understand generator expressions, yo
On 25-Jun-16 10:44, Craig Scott wrote:
One of the slight wrinkles here is that the distinction between
configure and generation times is now a little stronger due to
generator expressions. In order to really understand generator
expressions, you cannot really avoid getting your head around
con
On 25-Jun-16 10:02, Eric Noulard wrote:
Hi there,
I'd like to give my opinion here.
I agree that the fact that the cmake ui (qt or curse) makes it
possible to separate configure from generate
is an implementation detail. In fact one could perfectly decide that
the "configure" step should "gene
One of the slight wrinkles here is that the distinction between configure
and generation times is now a little stronger due to generator expressions.
In order to really understand generator expressions, you cannot really
avoid getting your head around configure and generate being distinct parts
of
There is cmake **build** step: cmake --build _builds
So in GUI it's:
* cmake configure
* cmake generate
* IDE build (which you can do with cmake --build so it can be called
"cmake build" step)
in cmd:
* cmake configure+generate
* cmake build
Also I can call it "cmake step" in docs about
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.
On 24-Jun-16 23:49, Robert Maynard wrote:
Please run the configure and generate steps by
It's too long :)
Also it doesn't express the fact that it's a single action, consider:
"To add variables on configure and generate steps use '-D'"
"Before running configure and generate steps note that
Please run the configure and generate steps by
On Fri, Jun 24, 2016 at 4:40 PM, Ruslan Baratov
wrote:
>
> On 24-Jun-16 23:25, Robert Maynard wrote:
>>
>> cmake from the command line is still running the two stages, it just
>> doesn't allow for feedback/input from the user between the two stages.
On 24-Jun-16 23:25, Robert Maynard wrote:
cmake from the command line is still running the two stages, it just
doesn't allow for feedback/input from the user between the two stages.
Yes, I understand that. Question is about the name of the step. I.e.
when I do write manual what should I choose
cmake from the command line is still running the two stages, it just
doesn't allow for feedback/input from the user between the two stages.
On Fri, Jun 24, 2016 at 4:06 PM, Ruslan Baratov via CMake
wrote:
> Hi,
>
> I have a question about CMake terminology. When we are using CMake GUI there
> are
Hi,
I have a question about CMake terminology. When we are using CMake GUI
there are two buttons "Configure" and "Generate", hence we have two stages:
1. Configure step, when we do configuring project, effectively creating
file with cache variables (which we can modify) without really
genera
12 matches
Mail list logo
