All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-webserver][PATCH 6/6] xdebug: add new recipe
Date: Wed, 03 Oct 2012 12:28:29 +0100	[thread overview]
Message-ID: <1913726.eYu8z7U0Ds@helios> (raw)
In-Reply-To: <k4h3jt$n4q$3@ger.gmane.org>

On Wednesday 03 October 2012 12:21:51 Koen Kooi wrote:
> Op 01-10-12 18:14, Paul Eggleton schreef:
> > Add new recipe for the Xdebug PHP debugger/profiler.
> > 
> > Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> ---
> > meta-webserver/recipes-php/xdebug/xdebug_2.2.1.bb |   29
> > +++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644
> > meta-webserver/recipes-php/xdebug/xdebug_2.2.1.bb
> > 
> > diff --git a/meta-webserver/recipes-php/xdebug/xdebug_2.2.1.bb
> > b/meta-webserver/recipes-php/xdebug/xdebug_2.2.1.bb new file mode 100644
> > index 0000000..5bd374c --- /dev/null +++
> > b/meta-webserver/recipes-php/xdebug/xdebug_2.2.1.bb @@ -0,0 +1,29 @@
> > +SUMMARY = "Debugging and profiling extension for PHP"
> 
> Missing DESCRIPTION

No, this is deliberate - presumably you're aware that the default value of 
DESCRIPTION is "${SUMMARY}" ? The opposite is not true, which leads to 
packages with useless summaries if you set DESCRIPTION and not SUMMARY; so if 
it's just one line the single variable to set is SUMMARY. I know we have a lot 
of recipes that have this issue; we should probably address that on a wider 
basis.

> > +LICENSE = "Xdebug" +LIC_FILES_CHKSUM =
> > "file://LICENSE;md5=34df3a274aa12b795417c65634c07f16" + +DEPENDS =
> > "modphp" + +PR = "r0"
> 
> default....

See reply to patch 2/6.

> > + +SRC_URI = "http://xdebug.org/files/xdebug-${PV}.tgz" +
> > +SRC_URI[md5sum] = "5e5c467e920240c20f165687d7ac3709" +SRC_URI[sha256sum]
> > = "11d340eb7f87909a596bac054cc927df757dc2fc7c90b50a832c30e9bf84c9ad" +
> > +inherit autotools + +EXTRA_OECONF += "--enable-xdebug
> > -with-php-config=${STAGING_BINDIR_CROSS}/php-config" + +do_configure() {
> > +	${STAGING_BINDIR_CROSS}/phpize +	oe_runconf +}
> 
> Why not do autotools_do_configure?

Because AFAICT PHP modules are somewhat unusual when it comes to configure, and 
totally break if you try to autoreconf. IIRC this was the only way I could get 
the thing to build.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-10-03 11:41 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01 16:14 [meta-webserver][PATCH 0/6] Add meta-webserver Paul Eggleton
2012-10-01 16:14 ` [meta-webserver][PATCH 1/6] Add meta-webserver layer Paul Eggleton
2012-10-01 16:14 ` [meta-webserver][PATCH 2/6] apache2: add from OE-Classic Paul Eggleton
2012-10-03 10:17   ` Koen Kooi
2012-10-03 11:28     ` Paul Eggleton
2012-10-03 11:41       ` Koen Kooi
2012-10-03 12:23         ` Paul Eggleton
2012-10-01 16:14 ` [meta-webserver][PATCH 3/6] modphp: " Paul Eggleton
2012-10-03 10:20   ` Koen Kooi
2012-10-03 11:28     ` Paul Eggleton
2012-10-03 11:44       ` Koen Kooi
2012-10-01 16:14 ` [meta-webserver][PATCH 4/6] apache2: update to version 2.4.2 and fix Paul Eggleton
2012-10-01 16:14 ` [meta-webserver][PATCH 5/6] modphp: update to 5.3.14 " Paul Eggleton
2012-10-01 16:14 ` [meta-webserver][PATCH 6/6] xdebug: add new recipe Paul Eggleton
2012-10-03 10:21   ` Koen Kooi
2012-10-03 11:28     ` Paul Eggleton [this message]
2012-10-03 11:47       ` Koen Kooi
2012-10-03 13:08         ` Paul Eggleton
2012-10-02 14:40 ` [meta-webserver][PATCH 0/6] Add meta-webserver Koen Kooi
2012-10-02 14:53   ` Paul Eggleton
2012-10-03 10:24 ` Koen Kooi
2012-10-03 10:43   ` Paul Eggleton
2012-10-03 11:27     ` Koen Kooi
2012-10-03 11:29       ` Paul Eggleton
2012-10-03 11:43         ` Koen Kooi
2012-10-03 12:23           ` Paul Eggleton
2012-10-03 13:12             ` Koen Kooi
2012-10-03 13:43               ` Paul Eggleton
2012-10-03 14:08                 ` McClintock Matthew-B29882
2012-10-03 14:18                   ` Paul Eggleton
2012-10-03 14:19                   ` Khem Raj

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=1913726.eYu8z7U0Ds@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.