This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
haas:spring2020:cprog:projects:sof0 [2020/01/26 15:45] – [Submission] wedge | haas:spring2020:cprog:projects:sof0 [2020/01/26 15:46] (current) – [Review of Compiling/Executing] wedge | ||
---|---|---|---|
Line 231: | Line 231: | ||
</ | </ | ||
- | The BINARY_FILE comes **immediately after** the **-o**, **NOT** the SOURCE_FILE (it must never **immediately** follow a **-o**). It can precede, and such is perfectly valid (especially if you feel that way more intuitive). | + | The BINARY_FILE comes **immediately after** the **-o**, **NOT** the SOURCE_FILE (the source file must never **immediately** follow a **-o**). It can precede, and such is perfectly valid (especially if you feel that way more intuitive). |
- | The **-Wall** (treat all warnings as errors, increase general verbosity about warnings) and **--std=gnu99** (switch compiler to use the **C99** standard of the C language, with GNU extensions) are options given to the compiler. | + | The **-Wall** (treat all warnings as errors, increase general verbosity about warnings) and **< |
To execute your binary, we need to specify a path to it, so we use **./**, which basically references the current directory: | To execute your binary, we need to specify a path to it, so we use **./**, which basically references the current directory: |