Difference between revisions of "SPO600 Code Building Lab"

From CDOT Wiki
Jump to: navigation, search
(Created page with 'Category:SPO600 Labs{{Admon/lab|Purpose of this Lab|In this lab, you will do a baseline build of a software package and benchmark its performance.}} == Lab 2 == === Prerequ…')
 
(Tasks)
Line 8: Line 8:
  
 
=== Tasks ===
 
=== Tasks ===
 +
 +
{{Admon/caution|Do not build or install as root.|Do not build the software as root, and do not install the software into the system directories.}}
  
 
# Select a software package from the [[http://www.gnu.org/software/software.html Free Software Foundation's GNU Project]].
 
# Select a software package from the [[http://www.gnu.org/software/software.html Free Software Foundation's GNU Project]].
# Build the software. ''Do NOT build the software as the root user. Do NOT install the software into the system directories.''
+
# Build the software. You may need to install build dependencies (e.g., compilers, tools, and libraries).
 
# Test that it works.
 
# Test that it works.
 
# Select a second, open source software package that has a different license, and repeat the process with that software.
 
# Select a second, open source software package that has a different license, and repeat the process with that software.
 
# Blog about the process, your results, your observations, and what you learned.
 
# Blog about the process, your results, your observations, and what you learned.

Revision as of 22:38, 10 January 2016

Lab icon.png
Purpose of this Lab
In this lab, you will do a baseline build of a software package and benchmark its performance.

Lab 2

Prerequisites

You must have working accounts on a Linux server (such as Matrix, Zenit, the SPO600 Servers or your own system).

Tasks

Stop (medium size).png
Do not build or install as root.
Do not build the software as root, and do not install the software into the system directories.
  1. Select a software package from the [Free Software Foundation's GNU Project].
  2. Build the software. You may need to install build dependencies (e.g., compilers, tools, and libraries).
  3. Test that it works.
  4. Select a second, open source software package that has a different license, and repeat the process with that software.
  5. Blog about the process, your results, your observations, and what you learned.