Add prerequisites for building with GNU autotools #241
Conversation
rockdaboot
force-pushed
the
add-autotools-prerequisites
branch
from
84cc6d4 to
9293ccc
Compare
| - python2.7+ (for converting the PSL list) | ||
| - basic C development tools (compiler, linker) | ||
| - git, make, autoconf, autoconf-archive, autopoint, automake, autotools, | ||
| - libtool, gettext, m4, pkg-config |
There was a problem hiding this comment.
A lot of this can be summarized as "need autotools". Mentioning autopoint and m4 in particular are very specific details that are really abstracted away by the primary projects they are bundled with or a dependency of -- m4 is required by autoconf since autoconf processes m4 files, autopoint is part of gettext.
There was a problem hiding this comment.
Indeed, m4 has been pulled in as dependency here on Debian testing, but not so for autopoint nor autotools-dev. So I'd rather mention these tools/packages.
Removing git because without it you won't be able to fetch the sources!? (Mostly)
There was a problem hiding this comment.
I did not realize autopoint was a separate package in Debian. How utterly pointless...
There was a problem hiding this comment.
It has been part of gettext a while ago, AFAIR. There must be some reason to separate both, but idea tbh.
| - git, make, autoconf, autoconf-archive, autopoint, automake, autotools, | ||
| - libtool, gettext, m4, pkg-config | ||
| - for building docs: gtk-doc-tools (gtkdocize) | ||
| - for building tarballs: gzip, lzip |
There was a problem hiding this comment.
building tarballs isn't part of building the project, it's part of maintaining the project. IMO it's not good material for README.md, but could be good material for RELEASING.md as project-internal release checklists etc.
Fixes #157