|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
Wird oft zusammen gekauft
Produktinformation
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
Ist der Verkauf dieses Produkts für Sie nicht akzeptabel? |
Mehr über den Autor
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
› Besuchen Sie die Seite von John Calcote auf Amazon
› Besuchen Sie die Seite von John Calcote auf Amazon
Produktbeschreibungen
Kurzbeschreibung
The GNU Autotools make it easy for developers to create software that is portable across many Unix-like operating systems. Although the Autotools are used by thousands of open source software packages, they have a notoriously steep learning curve. And good luck to the beginner who wants to find anything beyond a basic reference work online. Autotools is the first book to offer programmers a tutorial-based guide to the GNU build system. Author John Calcote begins with an overview of high-level concepts and a quick hands-on tour of the philosophy and design of the Autotools. He then tackles more advanced details, like using the M4 macro processor with Autoconf, extending the frame work provided by Automake, and building Java and C# sources. He concludes the book with detailed solutions to the most frequent problems encountered by first-time Autotools users. You'll learn how to: - Master the Autotools build system to maximize your software's portability - Generate Autoconf configuration scripts to simplify the compilation process - Produce portable makefiles with Automake - Build cross-platform software libraries with Libtool - Write your own Autoconf macros Autotools focuses on two projects: Jupiter, a simple "Hello, world!" program, and FLAIM, an existing, complex open source effort containing four separate but interdependent subprojects. Follow along as the author takes Jupiter's build system from a basic makefile to a full-fledged Autotools project, and then as he converts the FLAIM projects from complex hand-coded makefiles to the powerful and flexible GNU build system.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
In diesem Buch
(Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Vorgeschlagene Tags zu ähnlichen Produkten(Was ist das?)Setzen Sie den ersten relevanten Tag hinzu (ein Schlüsselwort, das mit diesem Produkt in engem Zusammenhang steht).
|
Kundenrezensionen
Es gibt noch keine Kundenrezensionen auf Amazon.de
5 Sterne
4 Sterne
3 Sterne
2 Sterne
1 Sterne
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
8 Rezensionen
18 von 18 Kunden fanden die folgende Rezension hilfreich
Just what the doctor ordered
23. September 2010
Format:Taschenbuch
If there was ever a tool that needed a book it's Autoconf (and related scripts). Happily, Calcote has done a great job of describing, in detail, a collection of tools that can seem opaque at first glance (also at second glance). This book is vital for anyone who needs to work with Autotools and I wish I'd had it years ago.
The final chapter (A catalog of tips and reusable solutions for creating great projects) is fantastic because it dishes up a collection of practical, real solutions to problems users of Autotools will encounter. Above all, the book shows that it was written by someone who truly understands the set of tools, and thankfully is able to write clearly.
He doesn't shy away from getting into difficult details (like the M4 macro language) and chapters 8 and 9 are an exposition of the use of Autotools for an actual, large project showing what a real-world use of the tools looks like. Those 50 pages are probably the most valuable in the entire book.
Highly recommended for anyone who needs to use Autotools.
The final chapter (A catalog of tips and reusable solutions for creating great projects) is fantastic because it dishes up a collection of practical, real solutions to problems users of Autotools will encounter. Above all, the book shows that it was written by someone who truly understands the set of tools, and thankfully is able to write clearly.
He doesn't shy away from getting into difficult details (like the M4 macro language) and chapters 8 and 9 are an exposition of the use of Autotools for an actual, large project showing what a real-world use of the tools looks like. Those 50 pages are probably the most valuable in the entire book.
Highly recommended for anyone who needs to use Autotools.
8 von 8 Kunden fanden die folgende Rezension hilfreich
Clear and well written
12. Oktober 2010
Format:Taschenbuch
To quote the first page of the introduction "... and there are also many developers who hate the Autotools - with a passion". I think that I can safely say that I started out in that camp. In short, I find that autotools projects too oftern do not live up to the aim of being cross platform, and more philosophically, that they encourage non-standard C/C++ "standard" libraries and compilers. But I'm not writing a review of a book about Autotools, not the Autotools themselves.
The book is organized as 2 introductory chapters, then 5 chapters on autoconf/automaka/libtool. That's followed by 2 chapters covering an example of converting a non-trivial project to use Autotools. The last two chapters cover M4, the macro language Autotools is based on, and then a catalog of tips. This isn't a reference book, you won't find an exhaustive list of all the Autotools macros.
Even if you are not going to use autotools extensively, I found the introduction to "make" very clear. In fact, as good an introduction as anything I've read. Though I've read the O'Reilly books on "make" and "GNU make", I still learned a few things about "make". If, like me, you are just an occasional user of Autotools, then you'll find it useful if the "configure" script doesn't work out of the box. As an example, I tried to build CUnit just after reading this book. I followed the "readme.txt", but it didn't work. Running one extra command and adding some command line options sorted it out. If you're going to be using Autotools extensively, then you'll obviously want to read this book.
Calcote does go out of his way to recommend platform-independent practices, even going as far as to accommodate make tools other than GNU make. Example code is marked with numbered dots, which are then referred to in the text. I found that very readable and easy to follow. In general the tone of the book is quite calm and neutral (compared to some authors on GNU software who seem to get, well, a bit over-excited about their subject).
The only weakness I felt was in the chapter on libtool and dynamic linking. Mac OS X ought to have been mentioned (perhaps it was omitted because of its peculiar "app bundles"). I think that the difference between UNIX dynamic libraries ought to have been mentioned (all global data/functions exported by default, like static libraries) and Windows dynamic libraries (only data/functions decorated with __declspec(dllexport) are exported, for performance reasons).
In the end, did this book soften my views on Autotools? Yes, a bit. It may not match my ideals, but I can't imagine that Autotools is going to be replaced any time soon. So I'm better off knowing about how to use Autotools.
The book is organized as 2 introductory chapters, then 5 chapters on autoconf/automaka/libtool. That's followed by 2 chapters covering an example of converting a non-trivial project to use Autotools. The last two chapters cover M4, the macro language Autotools is based on, and then a catalog of tips. This isn't a reference book, you won't find an exhaustive list of all the Autotools macros.
Even if you are not going to use autotools extensively, I found the introduction to "make" very clear. In fact, as good an introduction as anything I've read. Though I've read the O'Reilly books on "make" and "GNU make", I still learned a few things about "make". If, like me, you are just an occasional user of Autotools, then you'll find it useful if the "configure" script doesn't work out of the box. As an example, I tried to build CUnit just after reading this book. I followed the "readme.txt", but it didn't work. Running one extra command and adding some command line options sorted it out. If you're going to be using Autotools extensively, then you'll obviously want to read this book.
Calcote does go out of his way to recommend platform-independent practices, even going as far as to accommodate make tools other than GNU make. Example code is marked with numbered dots, which are then referred to in the text. I found that very readable and easy to follow. In general the tone of the book is quite calm and neutral (compared to some authors on GNU software who seem to get, well, a bit over-excited about their subject).
The only weakness I felt was in the chapter on libtool and dynamic linking. Mac OS X ought to have been mentioned (perhaps it was omitted because of its peculiar "app bundles"). I think that the difference between UNIX dynamic libraries ought to have been mentioned (all global data/functions exported by default, like static libraries) and Windows dynamic libraries (only data/functions decorated with __declspec(dllexport) are exported, for performance reasons).
In the end, did this book soften my views on Autotools? Yes, a bit. It may not match my ideals, but I can't imagine that Autotools is going to be replaced any time soon. So I'm better off knowing about how to use Autotools.
5 von 5 Kunden fanden die folgende Rezension hilfreich
Autotools
19. März 2011
Format:Taschenbuch
This is an excellent book! It is aimed at open source package maintainers, however I read it because I just wanted to know how to use
Autoconf and Automake properly. For this objective it was perfect and worth every penny. The book develops a project logically, starting with a hand written makefile, turning this into a template for Autoconf then using Automake and Libtool. In later sections the author gives an account of how he took an existing open source project and converted it to use the Autotools. There is a chapter on m4 and another containing tips and advice from the author's hard won experience. Everything is well explained and the philosophy behind these tools is made clear. There are plenty of useful footnotes to the text and code listings are particularly well referenced in the text.
Autoconf and Automake properly. For this objective it was perfect and worth every penny. The book develops a project logically, starting with a hand written makefile, turning this into a template for Autoconf then using Automake and Libtool. In later sections the author gives an account of how he took an existing open source project and converted it to use the Autotools. There is a chapter on m4 and another containing tips and advice from the author's hard won experience. Everything is well explained and the philosophy behind these tools is made clear. There are plenty of useful footnotes to the text and code listings are particularly well referenced in the text.
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
Ähnliche Artikel finden
Anhand des Sachgebietes nach ähnlichen Produkten suchen:
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
|
