|
|
|
# COMP8440: Lab1 - building tuxpaint
|
|
|
|
## Lab Setup
|
|
|
|
As this is the first lab, you should carefully read the [Lab Setup](labsetup) page and follow all the instructions on that page to get the FOSSD environment installed and running.
|
|
|
|
|
|
|
|
Next, if you have not already done so, you should join the [comp8440 mailing list](http://fossd.anu.edu.au) using your ANU student email account. Note that you will need to be able to receive email to that account while in the lab. You will find that the email icon in the main menu bar of your lab system can be setup for accessing your ANU mail account.
|
|
|
|
|
|
|
|
When you first join the list, please send a very short email to the list to make sure it is working.
|
|
|
|
|
|
|
|
## Investigating tuxpaint
|
|
|
|
The aim of this lab is to build and install the TuxPaint project. The tuxpaint project has been chosen as it provides an illustration of some of the types of problems you are likely to run into with your own project.
|
|
|
|
|
|
|
|
During this lab we will be spending quite a lot of time running through the various steps below on the projector, while you follow along on your own system. If you run into trouble on your own system, then we will be able to display your screen on the projector, so we can work through the solution for the benefit of all the students.
|
|
|
|
|
|
|
|
The lab has a number of parts:
|
|
|
|
* Investigate the project
|
|
|
|
- Who wrote it?
|
|
|
|
- Who supports it?
|
|
|
|
- Where would you submit a bug report?
|
|
|
|
- Where would you get help?
|
|
|
|
- How do you get the source code?
|
|
|
|
- How active is development?
|
|
|
|
* Download the source code
|
|
|
|
* Build and install it
|
|
|
|
|
|
|
|
## Downloading the code
|
|
|
|
The source code for tuxpaint can be downloaded in several different ways, each of which leads to a different level of difficulty in building the project.
|
|
|
|
|
|
|
|
If you have time in this lab, try to download and build via all 3 of the following mechanisms:
|
|
|
|
|
|
|
|
* Using the apt package manager
|
|
|
|
* Using a release tarball
|
|
|
|
* Using a source code management system
|
|
|
|
|
|
|
|
You should now carefully read the [build tips](building) page for instructions on each of these approaches.
|
|
|
|
|
|
|
|
What are the advantages and disadvantages of each approach?
|
|
|
|
|
|
|
|
## Testing tuxpaint
|
|
|
|
As the name suggests, tuxpaint is a simple paint program. After building and installing it, just start it by running "tuxpaint" in a terminal window.
|
|
|
|
|
|
|
|
## Source Code Management (SCM) Tips
|
|
|
|
|
|
|
|
You may find some of the tips on the [SCM Tips](scmtips) page useful for this lab.
|
|
|
|
|
|
|
|
## MAKE SURE YOU BACKUP
|
|
|
|
|
|
|
|
Make sure you do a backup at the end of the lab, or you may lose all your work. |
|
|
\ No newline at end of file |
