Make
- GNU Make
- Make Rule Introduction What a rule looks like
- Special Note: recipes are indented using a tab character, not spaces. Using spaces (or an editor that expands tabs to spaces) will result in an invalid Makefile.
- Automatic Variables including
$@,$<, and$^ - NMake Microsoft's verion of Make
- srcML Playground Generate new srcML of source code, input format for
srccomplexity -
Make prerequisite graph for srcComplexity:
Exercise 27: Makefile
Use the GitHub Classroom Makefile Exercise link on Brightspace to create the repository for the Makefile program. Then use GitHub Codespaces to implement the Makefile. The workflow is:
Precondition: The starting Makefile is valid
- Edit and save the Makefile with the added build feature or enhancement
- Execute the build:
make - If there is a problem, go back to step 1.
- Commit the change to the local repository:
git commit -am "<Insert Commit Message>" - Push the change to the remote repository (GitHub):
git push - Verify the change at GitHub
Note: GitHub Codespaces automatically clones the repository for you. If you work on this on your own machine, then you will have to authenticate with GitHub and clone the repository one your own machine.
All commits made in class are viewable as they are made by following along in GitHub:
The Makefile is currently empty. Implement a Makefile to build the project by following along in class, or viewing the commits shown in class.
- Each change must be committed separately with a proper commit message
- The Makefile in each commit must be a valid Makefile and must work properly. Not doing so will result in a 0 on the assignment.
- For the commit message, use the one that I use in the demo repository
Due by 3:30 pm on Friday, Oct 13