Home Accessibility Courses Twitter The Mouth Facebook Resources Site Map About Us Contact
 
For 2023 (and 2024 ...) - we are now fully retired from IT training.
We have made many, many friends over 25 years of teaching about Python, Tcl, Perl, PHP, Lua, Java, C and C++ - and MySQL, Linux and Solaris/SunOS too. Our training notes are now very much out of date, but due to upward compatability most of our examples remain operational and even relevant ad you are welcome to make us if them "as seen" and at your own risk.

Lisa and I (Graham) now live in what was our training centre in Melksham - happy to meet with former delegates here - but do check ahead before coming round. We are far from inactive - rather, enjoying the times that we are retired but still healthy enough in mind and body to be active!

I am also active in many other area and still look after a lot of web sites - you can find an index ((here))
What is Make?

Make is a build tool. Let me give you some examples of where it might be used:
• If you're making an executable program, there is often a quite complex series of instructions to follow to convert your source files into the final executable file (your ultimate target).
• Similarly, if you're installing software from a distribution there is often a complex series of steps to move from that distribution to a fully installed and deployed installation.
• Another task which is similarly structured is the production of a test report from a series of test, which run on a system of some sort.

In writing your makefile - your instructions to make - you break down the operations you want to perform (your build) into a series of stages, each of which has some dependencies (the starting files) and a target (the output file), and rules describing how to get from dependencies to target. When you run the make tool, it looks at the relative time stamps on each of the files, and which targets are missing too, and works out which rules need to be run and in which order, so that only the rules that need to be run are run.

Make supports a wide variety of facilities to help the author of the makefile write a short and maintainable makefile which doesn't repeat things time and time again, and allows the author the ability to generate multiple output files and to "nest" make within make for greater flexibility. Other facilities allow the author to provide feedback and error handling during the running of make so that the user who is building or installing a product or running a series of tests through make is kept informed of its progress. But these powerful facilities come at the cost of a certain bewilderment for the newcomer, who can take a look at the make manual and wonder where to start. It's really not that hard with a bit of instruction and some hands on training and exercises.

I first trained on make as long ago as the early 1990s, having been a user of extensive makefiles for building, testing and installing our Designer I software package over the previous decade - a full-featured Computer Aided Design system written in C, Fortran and Assembler. Make was used for builds, for testing, and for installation across multiple platforms with our own preprocessors for system compatibility controlled from within make to allow us to easily maintain common source across a number of operating systems. And I still use make, most notably for C and C++ courses, where we include a short section within some of our public courses. I can also provide private training on make - a good introduction in half a day, or a full and quite deep course taking a day.

These days, we're very happy for delegates to use their own computers on most of our private training courses, and we only provide laptops ourselves where they're required (we remain very happy to do so). With make, though, we'll always provide systems, as there's going to be a wide variety of source data / material to use during the course, and the course covers installation of software as the administrator / root, and on delegate's own systems this would mean substantial downloading prior to the course, and could mean security concerns as to just what was installed during the make process - especially if in the learning process the student made errors that (for example) cleaned up (a.k.a. deleted) parts of the system. Better to do the early learning and experimentation on our machines which can be rebuilt than on your own.

(written 2012-03-02, updated 2012-03-10)

 
Associated topics are indexed as below, or enter http://melksh.am/nnnn for individual articles
A191 - Web Application Deployment - Installing Linux
  [705] Disc Partitioning - (2006-04-30)
  [1288] Linux run states, shell special commands, and directory structures - (2007-08-03)
  [1292] DHCP automatic IP address v Static IP - (2007-08-06)

A168 - Web Application Deployment - Compiler and development tools
  [694] Ant and Make - (2006-04-22)
  [1671] Compiling C programs with gcc - an overview - (2008-06-10)
  [2674] Make and makefiles - a commented example to help you learn - (2010-03-12)
  [3053] Make - automating the commands for building and installing - (2010-11-16)
  [3651] Makefile - some basics, and a demonstration - (2012-03-13)
  [3652] A Complete makefile example - (2012-03-14)
  [3658] Using Make for a distribution - (2012-03-17)
  [3666] Makefile variables - defined internally, from the command line and from the environment - (2012-03-22)
  [4013] Web Frameworks - nested templates - (2013-02-22)
  [4585] What is make? What is gcc? - (2015-11-28)


Back to
Getting around Dublin by public transport - some observations
Previous and next
or
Horse's mouth home
Forward to
Nesting Templates in Django
Some other Articles
Best tenner I ever spent?
Parse error: parse error, unexpected T_STRING on brand new web site - why?
Defining database relations in your Django model
Nesting Templates in Django
What is Make?
Getting around Dublin by public transport - some observations
Serialsing and unserialising data for storage and transfer in Perl
Sharing lots of values in Tcl without having lots of global declarations
Historic Drawings from near Melksham
Meeting Report - Tuesday 21st Feb - to Melksham Chamber of Commerce from Shadow Community Operations Board
4759 posts, page by page
Link to page ... 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96 at 50 posts per page


This is a page archived from The Horse's Mouth at http://www.wellho.net/horse/ - the diary and writings of Graham Ellis. Every attempt was made to provide current information at the time the page was written, but things do move forward in our business - new software releases, price changes, new techniques. Please check back via our main site for current courses, prices, versions, etc - any mention of a price in "The Horse's Mouth" cannot be taken as an offer to supply at that price.

Link to Ezine home page (for reading).
Link to Blogging home page (to add comments).

You can Add a comment or ranking to this page

© WELL HOUSE CONSULTANTS LTD., 2024: 48 Spa Road • Melksham, Wiltshire • United Kingdom • SN12 7NY
PH: 01144 1225 708225 • EMAIL: info@wellho.net • WEB: http://www.wellho.net • SKYPE: wellho

PAGE: http://www.wellho.net/mouth/3632_Wha ... Make-.html • PAGE BUILT: Sun Oct 11 16:07:41 2020 • BUILD SYSTEM: JelliaJamb