Comment by duped 3 months ago Do you review the 10k+ lines of generated bash in ./configure, too? 2 comments duped Reply cozzyd 3 months ago ./configure shouldn't be in your repo unless it's handwritten johnisgood 3 months ago Pretty much. It is called "autotools" for a reason.Theoretically you should be able to generate the configuration scripts through "autoconf" (or autoreconf), or generate Makefile.in for configure from Makefile.am using "automake", etc.
cozzyd 3 months ago ./configure shouldn't be in your repo unless it's handwritten johnisgood 3 months ago Pretty much. It is called "autotools" for a reason.Theoretically you should be able to generate the configuration scripts through "autoconf" (or autoreconf), or generate Makefile.in for configure from Makefile.am using "automake", etc.
johnisgood 3 months ago Pretty much. It is called "autotools" for a reason.Theoretically you should be able to generate the configuration scripts through "autoconf" (or autoreconf), or generate Makefile.in for configure from Makefile.am using "automake", etc.
./configure shouldn't be in your repo unless it's handwritten
Pretty much. It is called "autotools" for a reason.
Theoretically you should be able to generate the configuration scripts through "autoconf" (or autoreconf), or generate Makefile.in for configure from Makefile.am using "automake", etc.