All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] icecast: new package
Date: Wed, 17 Jul 2013 12:19:05 +0200	[thread overview]
Message-ID: <20130717121905.36d0e71f@skate> (raw)
In-Reply-To: <1374055607-24500-1-git-send-email-elezegarcia@gmail.com>

Dear Ezequiel Garcia,

On Wed, 17 Jul 2013 07:06:47 -0300, Ezequiel Garcia wrote:

> +diff -Naur icecast-2.3.3/m4/xiph_curl.m4 icecast-2.3.3-patched/m4/xiph_curl.m4
> +--- icecast-2.3.3/m4/xiph_curl.m4	2012-06-11 13:45:26.000000000 -0300
> ++++ icecast-2.3.3-patched/m4/xiph_curl.m4	2013-07-17 06:58:02.000000000 -0300
> +@@ -48,28 +48,10 @@
> + dnl
> + dnl Now check if the installed libcurl is sufficiently new.
> + dnl
> +-AC_CHECK_HEADERS([curl/curl.h],, curl_ok="no") 
> + AC_MSG_CHECKING(for libcurl)
> +-if test "$curl_ok" = "yes"
> +-then
> +-    AC_RUN_IFELSE(AC_LANG_SOURCE([
> +-#include <curl/curl.h>
> +-int main()
> +-{
> +-    return 0;
> +-}
> +-]),,[curl_ok="no"])
> +-fi
> +-if test "$curl_ok" = "yes"; then
> +-    AC_MSG_RESULT(yes)
> +-    AC_DEFINE(HAVE_CURL, 1, [Define if you have libcurl.])
> +-    ifelse([$1], , :, [$1])     
> +-else
> +-    AC_MSG_RESULT(no)
> +-    CURL_LIBS=""
> +-    CURL_CFLAGS=""
> +-    ifelse([$2], , :, [$2])
> +-fi
> ++AC_MSG_RESULT(yes)
> ++AC_DEFINE(HAVE_CURL, 1, [Define if you have libcurl.])
> ++ifelse([$1], , :, [$1])     

So here you're completely removing the curl check and assume that it is
always present?


> +ifeq ($(BR2_PACKAGE_LIBCURL),y)
> +ICECAST_DEPENDENCIES += libcurl
> +ICECAST_CONF_OPT += --with-curl-config=$(STAGING_DIR)/usr/bin/curl-config
> +else
> +ICECAST_CONF_OPT += --without-curl
> +endif

and here curl is still optional?

Regarding the xiph_curl.m4 check, you could turn it into an AC_TRY_LINK
test, like is done for Speex, Theora and so on. Or maybe even keep only
the AC_CHECK_HEADERS() as an indication of whether curl is available or
not.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

       reply	other threads:[~2013-07-17 10:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1374055607-24500-1-git-send-email-elezegarcia@gmail.com>
2013-07-17 10:19 ` Thomas Petazzoni [this message]
2013-07-17 10:25   ` [Buildroot] [PATCH v2] icecast: new package Ezequiel Garcia
2013-07-17 10:48     ` Ezequiel Garcia
2013-07-17 11:36     ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130717121905.36d0e71f@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.