Fix setting CPPFLAGS/LIBS in audacious-plugins autoconf script
The audacious-plugins autoconf script currently sets up CPPFLAGS/LIBS with the
flags from Audacious very early in the script and polluting the environment
which causes some of the autoconf checks to potentially fail. So move setting
CPPFLAGS/LIBS to the very end so as to not pollute the environment but still
provide the flags for the build.
#2 Updated by Brad Smith about 7 years ago
John Lindgren wrote:
How would Audacious CPPFLAGS/LIBS cause autoconf checks to fail?
This line near the very top of the autoconf script...
adds libaudclient and libaudgui to LIBS which brings in those libraries and a whole slew of dependencies from them which is then polluting the linking environment for the autoconf tests. There is no reason these libs should be added like this so early on. Move them to the very end after running all of the autoconf checks.