Haoyu Tan’s code library. Contribute to haoyutan/codelib development by creating an account on GitHub. Autotools: a practitioner’s guide to Autoconf, Automake and Libtool. by John Calcote – Chapter 1: A brief introduction to the GNU Autotools. by John . There are few people who would deny that Autoconf, Automake and Libtool have revolutionized the free software world. While there are many thousands of.

Author: Mutilar Tojajora
Country: Pakistan
Language: English (Spanish)
Genre: Love
Published (Last): 20 June 2010
Pages: 375
PDF File Size: 20.79 Mb
ePub File Size: 14.41 Mb
ISBN: 709-1-42076-297-9
Downloads: 90143
Price: Free* [*Free Regsitration Required]
Uploader: Dutaxe

It’s very easy to type make –but that’s not the problem. Regardless, you can bet there are other mailing list readers who experienced far more confusion over this exchange. What auyotools dream of a tool to work with–I love it! Neither do I, but there is a handful of developers in the world who know a large percentage of these differences. Who ajtotools read this book This book is written for the open source software package maintainer.

License Verbatim copying and gguide of this entire article are permitted worldwide, without royalty, in any medium, provided this notice is preserved. The purpose of the Autotools is to make life simpler for the end-user. Let me try to explain with an analogy. Let’s analyze this picture: With these concepts, you’ll be prepared to understand some of the most fundamental rationale behind architectural decisions made by the Autotools developers.

If that’s the case, then this response made no sense to him whatsoever. In the early ‘s I was working on the final stages of my bachelor’s degree in computer science at Brigham Young University. His authors wouldn’t finish the project, and the publisher’s market analysis indicated that there prctitioner very little interest in the book.


As a side benefit, the GNU manuals for the Autotools should begin to make a lot more sense to you. Between them and the free software community, the Autotools were born.

This book attempts to alleviate some of the confusion and reduce the existing learning curve by presenting the Autotools in a manner conducive to an open source beginner learning how to use them.

Now, it’s truly wonderful that we have experts on mailing lists who are so willing to respond cheerfully to questions like this, and so quickly–this exchange took place within a few hours. I recommend that you give this chapter a quick read practitionet start with, and then come back to it later, after you’ve read the rest of this book. They fixed about 65 percent of the problems resulting from system configuration differences–and they were a pain autotoops the neck to write properly.

Autotools: a practitioner’s guide to Autoconf, Automake and Libtool

I chose not to do this for two reasons: So, returning to that passionate hate felt by some developers toward the Autotools: This chapter describes the interaction between these packages, and the files consumed by and generated by each one.

However, without looking, I submit that similar questions have probably been asked dozens of autotoops in the last 5 years. You’ll still need to handle the operation experience, of course, but Autotools can provide a great multi-platform build and installation experience–with far less effort on your part.


Is that a “never”? They’re free, and links are provided in the References section of this book, but they’re easy to find with a simple internet query.

Chapter 7 is a compilation of tips and tricks or resusable solutions that I’ve come across during my experience with the Autotools. There are few people who would deny that Autoconf, Automake and Libtool have revolutionized the free software world.

Autotools: a practitioner’s guide to Autoconf, Automake and Libtool

This chapter designs a simple project jupiter from start to finish using a hand-coded configure script and makefiles. Each of those maintainers probably uses or has tried to use the Autotools.

If you already have a basic familiarity with these packages, you can probably skip these chapters, but please feel free to revisit them if you find yourself in over your autotoolss with the remaining chapters.

Given the high-level nature of configure. It’s a great reference, but a terrible tutorial. Learning by example is an excellent way to begin to retain the information you’ve read.

Take sedfor example: