All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-mono] Question about Q/A installed vs shipped failure
Date: Fri, 01 Nov 2013 11:43:30 +0000	[thread overview]
Message-ID: <527393E2.2090001@dynamicdevices.co.uk> (raw)
In-Reply-To: <10981400.qX3sYBV1WQ@helios>

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


On 01/11/2013 11:32, Paul Eggleton wrote:
> Hi Alex,
>
> On Friday 01 November 2013 10:03:44 Alex J Lennon wrote:
>> I'm looking at at the gtk-sharp recipe in meta-mono:
>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-mono/tree/recipes-mono/gtk-sh
>> arp/gtk-sharp_2.10.2.bb
>>
>> This defines the contents of various gtk-sharp related packages making
>> use of FILES_foo = and PACKAGES =
>>
>> When I try to build against the Yocto head it fails a Q/A check with
>> "ERROR: QA Issue: gtk-sharp: Files/directories were installed but not
>> shipped"
>>
>> Normally I would expect the extraneous files to be found in the image
>> tree and add do_install_append() to rm the unneeded files from {$}D/foo/bar
>>
>> However the behaviour of this recipe seems different.
>>
>> For some reason the extraneous files are being found in the ../package
>> tree. They are put there by the do_package() step, which is executed
>> after my do_install_append().
> This sounds a bit odd. Out of curiosity I just built gtk-sharp and it seems to
> me the files it's reporting as unpackages are under image/, which should allow
> them to be deleted. What are you adding to the recipe to try to fix this?

Hi Paul,

I've been into a devshell and can see the files, on my system at least, 
are definitely in package/ not image/

I'm currently in the midst of adding support for Mono 3.2.3 into a fork 
I took of the Yocto latest meta-mono repo

My current sandbox repo is here: 
git@git.assembla.com:ciseco-eve.meta-mono.git (web: 
https://www.assembla.com/code/ciseco-eve/git-2/nodes)

It's now building Mono 3.2.3 and running console only .exes but I'm 
having some trouble with support for Windows Forms which I'm looking into.

I'm building for qemux86 with, what I believe is, Yocto head:

Build Configuration:
BB_VERSION        = "1.21.0"
BUILD_SYS         = "i686-linux"
NATIVELSBSTRING   = "Ubuntu-12.04"
TARGET_SYS        = "i586-poky-linux"
MACHINE           = "qemux86"
DISTRO            = "poky"
DISTRO_VERSION    = "1.5+snapshot-20131101"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta
meta-yocto        = "master:523f2a9ea970713fb775bc48f84b67420b1106a0"
meta-oe
meta-efl          = "master:3000970fcd979ac2d68ef406778dbc4da86da73f"
meta-fsl-arm      = "master:88117e976c16f22b9bbfeb26a52088e31f1d0c4d"
meta-fsl-arm-extra = "master:5b753d3d130ed6932715329d0e887a015e628766"
meta-fsl-demos    = "master:87233da97fe0ead245773e092acb56faa24f3835"
meta-mono         = "master:0c2655fc8037d9aa46e884f9bac5c52c7ff7ae8e"

Best Regards,

Alex



>> I have tried adding a do_package_append() which I thought might help but
>> bitbake won't accept this.
> This shouldn't be necessary.
>   
> Cheers,
> Paul
>

-- 

Dynamic Devices Ltd <http://www.dynamicdevices.co.uk/>

Alex J Lennon / Director
1 Queensway, Liverpool L22 4RA

mobile: +44 (0)7956 668178

Linkedin <http://www.linkedin.com/in/alexjlennon> Skype 
<skype:alexjlennon?add>

This e-mail message may contain confidential or legally privileged 
information and is intended only for the use of the intended 
recipient(s). Any unauthorized disclosure, dissemination, distribution, 
copying or the taking of any action in reliance on the information 
herein is prohibited. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, or contain viruses. 
Anyone who communicates with us by e-mail is deemed to have accepted 
these risks. Company Name is not responsible for errors or omissions in 
this message and denies any responsibility for any damage arising from 
the use of e-mail. Any opinion and other statement contained in this 
message and any attachment are solely those of the author and do not 
necessarily represent those of the company.


[-- Attachment #2.1: Type: text/html, Size: 7331 bytes --]

[-- Attachment #2.2: ddlogo-4.png --]
[-- Type: image/png, Size: 3997 bytes --]

[-- Attachment #2.3: linkedin.png --]
[-- Type: image/png, Size: 631 bytes --]

[-- Attachment #2.4: skype.png --]
[-- Type: image/png, Size: 800 bytes --]

      reply	other threads:[~2013-11-01 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 10:03 [meta-mono] Question about Q/A installed vs shipped failure Alex J Lennon
2013-11-01 11:08 ` Søren Holm
2013-11-01 11:32 ` Paul Eggleton
2013-11-01 11:43   ` Alex J Lennon [this message]

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=527393E2.2090001@dynamicdevices.co.uk \
    --to=ajlennon@dynamicdevices.co.uk \
    --cc=paul.eggleton@linux.intel.com \
    --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.