configure.ac doesn't check for presence of pkg-config macros
Bug #795647 reported by
Gareth Edwards
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gEDA |
Won't Fix
|
Undecided
|
Peter TB Brett |
Bug Description
Currently the configure.ac file assumes that pkg-config is installed with its autoconf macros. This gives a slightly confusing error message that the PKG_PROC_PKG_CONFIG macro is not defined.
Attached path explicitly checks for the macro and suggests that pkg-config is installed if it can't be found.
To post a comment you must log in.
I don't feel very keen on this patch.
1) The issue only affects people compiling from git -- if you are compiling from a tarball, it's not an issue (the autoconf macro actually generates code which checks for pkg-config).
2) People who can compile from git can also be expected to read README files (although it might well be that the README file needs enhancement on this point).
3) "./autogen.sh" (via "aclocal") emits a warning about missing macros. Maybe we should add -Werror to our aclocal options?
IMHO "configure.ac" should be aimed at generating the best possible "configure" with the minimum amount of boilerplate to save developers from themselves. ;-)