Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: how to exclude files when packaging?
Date: Thu, 17 Nov 2011 09:56:50 +0100	[thread overview]
Message-ID: <20111117085650.GA23959@jama.jama.net> (raw)
In-Reply-To: <CAEsOVNdL3bTKA9rv6p9SEpvoY+a3b5y6Ftn=ySMVdgkW3nMm3w@mail.gmail.com>

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

On Thu, Nov 17, 2011 at 08:14:06AM +0000, McClintock Matthew-B29882 wrote:
> On Wed, Nov 16, 2011 at 8:29 PM, Ni Qingliang
> <niqingliang@insigma.com.cn> wrote:
> > Hello, All:
> >        I'm working on opensaf, wrote a bb file for it,
> > and found that the FILES_${PN} has included /usr/lib/${PN}/*.
> > but there are some .a and .so(symlink) in /usr/lib/${PN}, which will
> > result QA issue.
> >        how to exclude some files (e.g. *.a, *.so) in FILES_${PN}?
> >
> >        there are some elf in /usr/lib/${PN} whose prefix is not 'lib', so if
> > no 'exclude' feature, I must redefine FILES_${PN} like this:
> >        FILES_${PN} = "/usr/lib/${PN}/*.so.* \
> >                       /usr/lib/${PN}/saf* \
> >                       /usr/lib/${PN}/open* \
> >                       /usr/lib/${PN}/immload \
> >                       /usr/lib/${PN}/nid_tipc \
> >                       /usr/lib/${PN}/smf* \
> >                       /usr/lib/${PN}/clc-cli/*"
> 
> Explicitly list what you want in FILES_${PN}
> 
> FILES_${PN} = /usr/lib/${PN}/saf
> 
> Make another PACKAGE for other files
> 
> PACKAGES =+ ${PN}-misc
> FILES_${PN}-misc = /usr/lib/${PN}/saf
> 
> Maybe someone else can chime in if there is a way to mask certain files...

Be carefull with order of packages in PACKAGES usually you need it from
most specific files pattern to less specific and the problem above is
related to this:

http://lists.linuxtogo.org/pipermail/openembedded-core/2011-October/011283.html

which wasn't applied, so yes you have to redefine whole FILES_${PN} or
the part you need for your app, like I did for syslog-ng
http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-October/035607.html

Regards,

> 
> -M
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2011-11-17  9:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17  2:29 how to exclude files when packaging? Ni Qingliang
2011-11-17  8:14 ` McClintock Matthew-B29882
2011-11-17  8:56   ` Martin Jansa [this message]
2011-11-17  8:57   ` Henning Heinold
2011-11-17  9:12     ` Ni Qingliang
2011-11-17 19:38       ` Mark Hatle
2011-11-17 19:43         ` Chris Larson
2011-11-17 19:51           ` Mark Hatle
2011-11-17  9:10 ` Koen Kooi
2011-11-17  9:30   ` Ni Qingliang

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=20111117085650.GA23959@jama.jama.net \
    --to=martin.jansa@gmail.com \
    --cc=B29882@freescale.com \
    --cc=openembedded-core@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