September 2005
Intermediate to advanced
328 pages
10h 9m
English
Content preview from Practical Development EnvironmentsBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Chapter 5. Building Software
this chapter discusses how software products are built from their source files. The first half of the chapter describes what a build tool is and what you might want a build tool to do. The second half compares six of the most commonly used build tools: shell scripts and batch files, make, GNU Autotools, Ant, Jam, and SCons.
One solid study, not written by a consultant working for a company that sells a build tool, suggests that between 10% and 30% of the time spent working on many complex software projects is spent wrestling with the build tool, waiting for slow builds, or investigating phantom bugs due to inconsistent builds.[1] That’s a substantial amount of time! Whether you believe the figures or not, frustrating experiences with a build tool can certainly make any project far less productive. Conversely, a good build tool can fade into the background and let you get on with writing code.
The purpose of this chapter is to help you choose and use an appropriate build tool for your project. If that choice has already been made, then the examples and references for each build tool should help you use the build tool better. If you are using a build tool that isn’t described here, then the general observations about builds should still be useful.
How Software Gets Built
This section is a brief overview of how source code is turned into an executable, a program that can actually run on a computer. This is the process is known as “building software.” A summary ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.