title: What is the command line used by CLion when invoking CMake?
body: <p>What is exactly the command line (process and arguments) used by CLion  when invoking CMake? I'm trying to use the same directory for manual builds using the terminal and for building using the IDE, but it seems that one is interacting badly with the other.</p>
  
  <p>I have no problem with using CLion only to handle CMake configurations (to avoid slight configuration mismatch triggering another CMake execution), but it seems that even standard builds using <code>make</code> on the command line trigger <code>cmake</code> again.</p>
  
  <p>I've seen that CLion prints it's "call" to CMake, but I don't see where it references the current working directory. And since on the GUI you configure paths relative to the project root folder (where <code>CMakeLists.txt</code> live), instead of relative to the build folder. I was hoping that this detail is the culprit here.</p>
  
  <p>Usually in the command line I'd do it like this:</p>
  
  <pre><code>$ cd project
  $ mkdir -p builds/debug
  $ cd builds/debug
  $ cmake $MY_CMAKE_OPTS -DSPECIAL_FILE=../../file.ext ../..
  </code></pre>
  
  <p>On CLion, though, I have to configure it like this:</p>
  
  <pre><code>CMake options: $MY_CMAKE_OPTS -DSPECIAL_FILE=file.ext
  Generation path: builds/debug
  The rest I've used the default
  </code></pre>
  
  <p>This <em>special file</em> is used on the configuration phase, so using paths other than relative to project root or absolute paths won't work.</p>