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

Andrew Vagin avagin at parallels.com
Fri Mar 21 00:20:46 PDT 2014


On Thu, Mar 20, 2014 at 08:17:28PM +0400, Ruslan Kuprieiev wrote:
> Although many people don't like autoconf, I believe, it is more suitable

I'm one of this group and I would prefer to avoid it as long as we can.

> here then tests in Makefile.conf. For example, configure script allows us
> to easily detect optional libraries and add them to LIBS.

Why can't we do that using Makefile.config?

> 
> 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
> 
> -- 
> 1.8.3.2
> 
> _______________________________________________
> CRIU mailing list
> CRIU at openvz.org
> https://lists.openvz.org/mailman/listinfo/criu


More information about the CRIU mailing list