===== Build Process =====

Building software is a complex task that many developers gloss over. The simple act of compiling a program invokes a process with five or more stages, including pre-proccessing, compiling, optimizing, assembling, and linking. However, a complex software system will have hundreds or even thousands of source files, as well as dozens or hundreds of build configuration options, auto configuration scripts (cmake, autotools), build scripts (such as Makefiles) to coordinate the process, test suites, and more.

==== General Course Information ====

* Course resources are linked from the CDOT wiki, starting at http://wiki.cdot.senecacollege.ca/wiki/index.php/SPO600 (Quick find: This page will usually be Google's top result for a search on "SPO600").

* Coursework is submitted by blogging.

==== Course and Setup: Accounts, agreements, servers, and more ====

* [[SPO600 Communication Tools]]

* [[Fall 2019 SPO600 Participants]] page

==== How open source communities work ====

* Do the [[SPO600 Code Review Lab|Code Review Lab (Lab 1)]] as homework.

* [[Computer Architecture]] overview (see also the [[:Category:Computer Architecture|Computer Architecture Category]])

* Analyzing compiler output

** Disassembly

=== Week 1 Deliverables ===

# Course setup:

## Set up your [[SPO600 Communication Tools]] - in particular, set up a blog and add it to [http://zenit.senecac.on.ca/~chris.tyler/planet/ Planet CDOT] (via the [[Planet CDOT Feed List]]).

## Add yourself to the [[SPO600 Participants]] page (leave the projects columns blank).

## Generate a [[SPO600_Servers#Preparatory_Steps|pair of keys]] for [[SSH]] and email the public key to your professor, so that he can set up your access to the [[SPO600 Servers|class servers]].

<!--