Difference between revisions of "Real World Mozilla Makefile Lab"

From CDOT Wiki
Jump to: navigation, search
m (switched order of make && make clean)
Line 20: Line 20:
 
# You will know you are done when the following commands result in nled.exe being produced:
 
# You will know you are done when the following commands result in nled.exe being produced:
  
 +
$ make
 
  $ make clean
 
  $ make clean
$ make
+
 
  
 
or, if you want to combine this into one line:
 
or, if you want to combine this into one line:
  
  $ make clean && make
+
  $ make && make clean
  
 
== Hints ==
 
== Hints ==

Revision as of 19:46, 17 September 2007

Real World Mozilla > Real World Mozilla Day 2 > Makefile Lab

Overview

This lab is designed to give you first-hand experience creating a simple Makefile and using Make to build software. While the Mozilla build system is much more complex than this example, the ideas learned here will get you started understanding how Mozilla is built.

For nostalgic reasons we will work with the source code to Evan Weaver's nled editor, written in C.

Instructions

The lab machines have already been set-up to use MSVC 8 and MozillaBuild RC1. You only need to run Mozilla-Build MSVC 8.bat (there is a link on the desktop) to begin (i.e., you shouldn't need to install anything).

  1. Download and extract the nled source code
  2. Start Mozilla-Build MSVC8.bat to get a proper build environment
  3. Move to the directory where you extracted the source
  4. Using a text editor, create a file in this directory named Makefile
  5. Examine all the .c files to determine dependencies with the .h files
  6. Write targets and rules for each of the object files and the final executable
  7. Write a clean target in order to delete all .obj and .exe files
  8. You will know you are done when the following commands result in nled.exe being produced:
$ make
$ make clean


or, if you want to combine this into one line:

$ make && make clean

Hints

  • CL -c option
  • CL -Fo option
  • The default extension for object files on win32 is .obj vs. .o on Unix
  • To create the executable (nled.exe) you must link all .obj files and user32.lib
  • Running make with the -n option will show you all the commands make is going to run, which is helpful when debugging makefiles:
$ make -n

Resources