All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: S.Jaritz@esa-grimma.de
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Antwort: Re: how to configure the build packages of a makefile based libary
Date: Fri, 29 Apr 2016 09:59:05 +0100	[thread overview]
Message-ID: <CAJTo0La51T5zQZv0JbakTifLUNVv=n291fmrx=RhmLpDq+C7Gg@mail.gmail.com> (raw)
In-Reply-To: <OFAE948224.6BDA8DD0-ONC1257FA4.0028E4AF-C1257FA4.002B73A2@esa-grimma.de>

[-- Attachment #1: Type: text/plain, Size: 1934 bytes --]

Hi Stefan,

So close :)  Some more points:

On 29 April 2016 at 08:54, <S.Jaritz@esa-grimma.de> wrote:
> LICENSE = "COPYING"

This should be the name of the license itself, not the filename.  Looks a
bit like MIT to me.

> LIC_FILES_CHKSUM =
"file://${WORKDIR}/git/COPYING;md5=d84d659a35c666d23233e54503aaea51"

This URI is relative to ${S} so you can just do file://COPYING;md5=....

> EXTRA_OEMAKE = "'PREFIX=/usr/'"

Use PREFIX=${prefix} to respect the what the distro has configured.
Annoyingly you can't override the other paths such a libdir easily, so this
will break in multilib configurations or if I recall correctly, on aarch64.

The commandline outputs:
> #############
> NOTE: Executing RunQueue Tasks
> WARNING: QA Issue: libhiredis: /libhiredis-staticdev/usr/lib/libhiredis.a
> is owned by uid 1000, which is the same as the user running bitbake. This
> may be due to host contamination [host-user-contaminated]
> WARNING: QA Issue: libhiredis: /libhiredis/usr/lib/libhiredis.so.0.13 is
> owned by uid 1000, which is the same as the user running bitbake. This may
> be due to host contamination [host-user-contaminated]
> WARNING: QA Issue: libhiredis:
> /libhiredis-dev/usr/lib/pkgconfig/hiredis.pc is owned by uid 1000, which is
> the same as the user running bitbake. This may be due to host contamination
> [host-user-contaminated]
> #############
>

The upstream Makefile is using "cp -a" which preserves ownership, so as you
built the package the files are owned by you.  Luckily you can override
this by passing "INSTALL='cp -r' to the make install (they use cp to
recursively copy directories, so you need to pass -r instead).

I've a recipe locally with these changes and it builds without warnings and
is packaged correctly.

This is what happens when maintainers think autotools is too complicated
and a bare makefile is just fine: they do it wrong. :)

Ross

[-- Attachment #2: Type: text/html, Size: 3131 bytes --]

  reply	other threads:[~2016-04-29  8:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28  9:50 how to configure the build packages of a makefile based libary S.Jaritz
2016-04-28 10:51 ` Burton, Ross
2016-04-28 12:09   ` S.Jaritz
2016-04-28 12:44     ` Burton, Ross
2016-04-28 15:25       ` Fred Ollinger
2016-04-28 15:46         ` Burton, Ross
2016-04-28 16:09           ` Antwort: " S.Jaritz
2016-04-28 16:16             ` Burton, Ross
2016-04-28 16:16             ` Antwort: " Fred Ollinger
2016-04-28 16:18             ` YUKATHARSANI JEYACHANDRA
2016-04-28 16:25               ` Burton, Ross
2016-04-29  7:54                 ` Antwort: " S.Jaritz
2016-04-29  8:59                   ` Burton, Ross [this message]
2016-04-29  9:59                     ` Antwort: " S.Jaritz
2016-04-29 11:11                       ` Burton, Ross
2016-04-29 14:01                         ` SIVA SUBRAMANIAN.P
2016-04-29 14:17                           ` Burton, Ross
2016-04-28 10:52 ` SIVA SUBRAMANIAN.P

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='CAJTo0La51T5zQZv0JbakTifLUNVv=n291fmrx=RhmLpDq+C7Gg@mail.gmail.com' \
    --to=ross.burton@intel.com \
    --cc=S.Jaritz@esa-grimma.de \
    --cc=yocto@yoctoproject.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.