Introduction to the Autotools (2012)
dwheeler.com
Introduction to the Autotools (2012)
1–10 of 57 posts
Re: Introduction to the Autotools (2012)
#2Autotools Mythbuster[0] is another great resource.
Re: Introduction to the Autotools (2012)
#3This documentation and video is good if you want to use autotools. But in 2016, you should really be asking yourself if autotools is the right choice. It is rather baroque, and there are many other choices these days that provide similar functionality for less developer time and effort.
Re: Introduction to the Autotools (2012)
#4This documentation and video is good if you want to use autotools. But in 2016, you should really be asking yourself if autotools is the right choice. It is rather baroque, and there are many other choices these days that provide similar functionality for less developer time and effort.
Could you provide some examples of other choices that you speak of? Thank you.
Re: Introduction to the Autotools (2012)
#5Autotools Mythbuster[0] is another great resource. [0] https://autotools.io/index.html
I get a 403 Forbidden.
Re: Introduction to the Autotools (2012)
#6This is awesome. Have just been strugglingh to get started with this the past few evenings. Will take this as my guide. Thanks for posting!
BTW, good place to start learning the relevant parts of GCC?
Re: Introduction to the Autotools (2012)
#7This documentation and video is good if you want to use autotools. But in 2016, you should really be asking yourself if autotools is the right choice. It is rather baroque, and there are many other choices these days that provide similar functionality for less developer time and effort.
To elaborate on "baroque": autotools spends a lot of time and effort on detecting behaviours which (a) no new Unix system has exhibited for at least two decades, and (b) your code almost certainly isn't going to be able to handle anyway.
Autotools was great once, but the world has moved on. Write code which is POSIX compliant and skip the whole mess.
Re: Introduction to the Autotools (2012)
#8Re: Introduction to the Autotools (2012)
#9[deleted]
Re: Introduction to the Autotools (2012)
#10This documentation and video is good if you want to use autotools. But in 2016, you should really be asking yourself if autotools is the right choice. It is rather baroque, and there are many other choices these days that provide similar functionality for less developer time and effort.
To elaborate on "baroque": autotools spends a lot of time and effort on detecting behaviours which (a) no new Unix system has exhibited for at least two decades, and (b) your code almost certainly isn't going to be able to handle anyway. Autotools was great once, but the world has moved on. Write code which is POSIX compliant and skip the whole mess.
As a user building packages I like autotools because of its uniformity. If I want to change the install root I use "--prefix". If I want to crosscompile I can set "--build" and "--host". If I need to set a compiler flag, autotools actually observes CFLAGS.
A few years ago I was trying to install a python extension and I couldn't figure out how to set a cflag on the native code it was compiling. It ignored CC, CFLAGS, etc. The documentation said nothing about it, super frustrating.