All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Patch for libfann-2.0.0 recipe
Date: Thu, 18 Jun 2009 20:14:34 +0200	[thread overview]
Message-ID: <h1e06a$9ja$1@ger.gmane.org> (raw)
In-Reply-To: <4A3A82F6.1010306@balister.org>

On 18-06-09 20:09, Philip Balister wrote:
> Koen Kooi wrote:
>> On 18-06-09 18:05, Elvis Dowson wrote:
>>> Hi Rolf,
>>>
>>> On Jun 17, 2009, at 8:43 AM, Rolf Leggewie wrote:
>>>
>>>> Can you please take a look at
>>>> http://wiki.openembedded.net/index.php/Styleguide and reorder the
>>>> fields accordingly? I think there is also a script in the contrib
>>>> directory to help with this.
>>>
>>> Here is the modified recipe: recipes/libfann/libfann-2.0.0.bb
>>>
>>> DESCRIPTION = "Fast Artificial Neural Network Library"
>>> HOMEPAGE = "http://leenissen.dk/fann/"
>>> SECTION = "libs"
>>> LICENSE = "BSD"
>>> SRCDATE = "20090618"
>>> PV = "2.0.0"
>>
>>> PR = "r01"
>>
>> Don't set PR to that.
>>
>>> SRC_URI = "http://prdownloads.sourceforge.net/fann/fann-${PV}.tar.bz2"
>>>
>>> S = "${WORKDIR}/fann-${PV}"
>>>
>>> inherit autotools pkgconfig
>>
>> use AUTOTOOLS_STAGE_PKGCONFIG = "1"
>>
>>> do_stage () {
>>> oe_libinstall -a -so -C src libfann ${STAGING_LIBDIR}
>>> install -d ${STAGING_INCDIR}/fann
>>> (cd ${S}/src/include; cp compat_time.h config.h doublefann.h fann.h
>>> fann_activation.h fann_cascade.h fann_data.h fann_error.h
>>> fann_internal.h fann_io.h fann_train.h fixedfann.h floatfann.h
>>> ${STAGING_INCDIR}/fann/)
>>> install -m 0644 ${S}/aclocal.m4 ${STAGING_DATADIR}/aclocal/
>>> }
>>
>> Again, don't use custom staging methods for silly reasons.
>
> I don't think the reason here is silly. I checked on my Fedora box and
> it installs the headers in include/fann/*.h also. The headers may need
> installing here so we can avoid patching existing software. I'm not
> intimately familiar with fann, so it would be great if people who are
> could look at this.

I think the fann authors know best where to install their to, which 
means using autotools_stage_all.

regards,

Koen




  reply	other threads:[~2009-06-18 18:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 17:14 Patch for libfann-2.0.0 recipe Elvis Dowson
2009-06-16 18:27 ` Koen Kooi
2009-06-16 18:38   ` Philip Balister
2009-06-16 19:00     ` Elvis Dowson
2009-06-16 19:59       ` Philip Balister
2009-06-16 21:36       ` Koen Kooi
2009-06-17  4:43 ` Rolf Leggewie
2009-06-18 16:05   ` Elvis Dowson
2009-06-18 16:48     ` Koen Kooi
2009-06-18 16:52       ` Otavio Salvador
2009-06-18 17:52         ` Koen Kooi
2009-06-18 18:11           ` Philip Balister
2009-06-18 18:24             ` Koen Kooi
2009-06-18 23:05               ` Tom Rini
2009-06-19  1:28                 ` Otavio Salvador
2009-06-19  8:06                 ` Koen Kooi
2009-06-19 17:47                   ` Tom Rini
2009-06-19 17:53                     ` Koen Kooi
2009-06-18 18:09       ` Philip Balister
2009-06-18 18:14         ` Koen Kooi [this message]
2009-06-18 18:36           ` Elvis Dowson
2009-06-18 18:56             ` Philip Balister
2009-06-19 13:37             ` Philip Balister
2009-06-19 13:52               ` Elvis Dowson

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='h1e06a$9ja$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.