Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The first line:</p> <pre><code>SDKROOT= make -C $TEMP_DIR -f $PROJECT_DIR/greg/Makefile VPATH=$PROJECT_DIR/greg || exit $? </code></pre> <ul> <li><code>SDKROOT=</code> sets the environment variable <code>SDKROOT</code> to nothing for the execution of the <code>make</code> command.</li> <li><code>make</code> is the build tool, and it's being run with the following options: <ul> <li><code>-C $TEMP_DIR</code>: means run <code>make</code> in the directory <code>$TEMP_DIR</code></li> <li><code>-f $PROJECT_DIR/greg/Makefile</code> specifies to <code>make</code> to use the Makefile in <code>$PROJECT_DIR/greg</code></li> <li><code>VPATH=$PROJECT_DIR/greg</code> sets another variable, <code>VPATH</code> to <code>$PROJECT_DIR/greg</code>. <code>VPATH</code> specifies to <code>make</code> <a href="http://www.gnu.org/software/make/manual/html_node/General-Search.html#General-Search" rel="nofollow">a search path for prerequisits</a>.</li> </ul></li> <li><code>|| exit $?</code> means that if the <code>make</code> command fails the script should exit with the same error code as <code>make</code>, as <code>$?</code> means <em>the return code of the last run program/command</em>.</li> </ul> <p>The second line:</p> <pre><code>$TEMP_DIR/greg -o $DERIVED_FILES_DIR/${INPUT_FILE_BASE}.m $INPUT_FILE_PATH </code></pre> <p>appears to be running the command <code>$TEMP_DIR/greg</code> with the option <code>-o $DERIVED_FILES_DIR/${INPUT_FILE_BASE}.m</code> and with some input from <code>$INPUT_FILE_PATH</code>. This looks like the program which may have been built from the previous line's <code>make</code> command, so it's hard to know exactly what it does.</p> <h3>EDIT</h3> <p>The SDKROOT is an environment variable used by XCode to say where the SDK it's using is installed. It will be a path like <code>/Developer/SDKs/MacOSX"${HOST_VERSION}".sdk/</code> for instance. The value should be setup somewhere in XCode I imagine (I don't used xcode so can't be more helpful than that.). By doing <code>SDKROOT=</code> at the beginning of the command the value of <code>SDKROOT</code> will be nothing/blank. The reason for this is that the code being compiled will use resources which exist in the <code>SDKROOT</code>, rather than local ones; such resources may be classes, config or libraries for example.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload