[CRIU] [PATCH 0/7] use autoconf istead of Makefile.conf

Pavel Emelyanov xemul at parallels.com
Thu Mar 20 12:26:13 PDT 2014


On 03/20/2014 08:17 PM, Ruslan Kuprieiev wrote:
> Although many people don't like autoconf, I believe, it is more suitable
> here then tests in Makefile.conf. For example, configure script allows us
> to easily detect optional libraries and add them to LIBS.

How would the build process look like after this set?
It should be stated in patch(es) comments and in the readme file.

> Ruslan Kuprieiev (7):
>   configure: add configure.in
>   configure: move Makefile to Makefile.in, add @LIBS@ and don't use
>     Makefile.conf
>   configure: add config.h.in
>   string: include bsd/string.h if libbsd is available
>   make: remove config tests
>   configure: add generated configure script
>   git: ignore trash files generated by autoconf
> 
>  .gitignore                |    3 +
>  Makefile                  |  301 ----
>  Makefile.config           |   32 -
>  Makefile.in               |  300 ++++
>  configure                 | 4108 +++++++++++++++++++++++++++++++++++++++++++++
>  configure.in              |   66 +
>  include/config.h.in       |   13 +
>  include/string.h          |    4 +
>  scripts/feature-tests.mak |   70 -
>  scripts/utilities.mak     |   15 -
>  10 files changed, 4494 insertions(+), 418 deletions(-)
>  delete mode 100644 Makefile
>  delete mode 100644 Makefile.config
>  create mode 100644 Makefile.in
>  create mode 100755 configure
>  create mode 100644 configure.in
>  create mode 100644 include/config.h.in
>  delete mode 100644 scripts/feature-tests.mak
>  delete mode 100644 scripts/utilities.mak
> 




More information about the CRIU mailing list