Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: receipe for libmicrohttpd
Date: Thu, 30 Apr 2009 22:26:49 +0100	[thread overview]
Message-ID: <49FA1799.7010100@xora.org.uk> (raw)
In-Reply-To: <20090430155320.GA7550@pcimg12.dei.unipd.it>

Ottavio Campana wrote:
> On Thu, Apr 30, 2009 at 03:22:30PM +0100, Graeme Gregory wrote:
>   
>> Ottavio Campana wrote:
>>     
>>> I wrote the receipe for libmicrohttpd, a LPGL library used to embedded a
>>> web server in programs.
>>>
>>> It works for me, but I'd like to have some feedback from you, if it is
>>> good or not and if you'd like to add it to OE.
>>>
>>> Ottavio
>>>
>>> PR = "r1"
>>> PN = "libmicrohttpd"
>>> DESCRIPTION = "GNU libmicrohttpd is a small C library that is supposed to make it easy to run an HTTP server as part of another application"
>>> HOMEPAGE = "http://www.gnu.org/software/libmicrohttpd/"
>>> SECTION = "libs"
>>> LICENSE = "LGPL"
>>>
>>> SRC_URI = "ftp://ftp.gnu.org/gnu/libmicrohttpd/libmicrohttpd-0.4.1.tar.gz"
>>>
>>> inherit autotools pkgconfig
>>>
>>> do_stage() {
>>>         oe_runmake DESTDIR="${D}" install
>>>         autotools_stage_all
>>> }
>>>
>>> do_qa_staging () {
>>> }
>>>
>>>   
>>>       
>> You need to run the recipe through oe-stylize (found in contrib directory).
>>
>> Why did you override do_qa_staging() ?
>>
>> Apart from this recipe looks good, cleanup and submit as a git-diff.
>>     
>
> here it is. I hope it's good.
>
>   
I missed it first time, but you dont need to set PN =

PN is derived from the .bb file name and is already set for you.

Graeme




  reply	other threads:[~2009-04-30 21:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30 14:04 receipe for libmicrohttpd Ottavio Campana
2009-04-30 14:22 ` Graeme Gregory
2009-04-30 15:53   ` Ottavio Campana
2009-04-30 21:26     ` Graeme Gregory [this message]
2009-05-02 22:31       ` Marc Humphreys

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=49FA1799.7010100@xora.org.uk \
    --to=dp@xora.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox