All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: <openembedded-core@lists.openembedded.org>
Subject: Weird ALTERNATIVES and staging conflict.
Date: Thu, 30 Oct 2014 15:17:15 +0100	[thread overview]
Message-ID: <5452486B.6070303@topic.nl> (raw)

I have this base script that builds FPGA bitstreams:

https://github.com/topic-embedded-products/meta-topic/blob/master/recipes-bsp/fpga/fpga-image.inc

Now you can have multiple recipes using it, and as such, it seemed a good idea 
to add these lines to that recipe:

+ALTERNATIVE_${PN} = "fpga.bin bitstreams"
+ALTERNATIVE_LINK_NAME[fpga.bin] = "${datadir}/fpga.bin"
+ALTERNATIVE_TARGET[fpga.bin] = "${datadir}/fpga.bin"
+ALTERNATIVE_LINK_NAME[bitstreams] = "${datadir}/bitstreams"
+ALTERNATIVE_TARGET[bitstreams] = "${datadir}/bitstreams"


This still resulted in staging conflicts. So I made two simple recipes to 
demonstrate the problem:

SUMMARY = "FPGA bitstream"
XILINX_VIVADO_VERSION = "2014.1"
require recipes-bsp/fpga/fpga-image.inc
LICENSE = "internal"
LIC_FILES_CHKSUM = 
"file://${METATOPIC_BASE}/LICENSE;md5=cf85de037de7ae12cc2d0059741fdbae"
SRC_URI = ""
S = "${WORKDIR}"

do_compile() {
	echo "${PN}" > fpga.bit
}
do_convert_bitstreams() {
	ln -f fpga.bit fpga.bin
}


I save this as "fpga-image-fake-one.bb" and "fpga-image-fake-two.bb"

I then create an image that installs them both, and bitbake that image. This 
(still) results in the following error:


ERROR: The recipe fpga-image-fake-two is trying to install files into a shared 
area when those files already exist. Those files and their manifest location are:
 
/home/mike/zynq_platform/build/tmp-glibc/sysroots/topic-miami-7015/usr/share/fpga.bin
  Matched in manifest-topic-miami-7015-fpga-image-fake-one.populate_sysroot
Please verify which recipe should provide the above files.



But looking at the contents of the fake packages, the fpga.bin has been 
renamed by alternatives (as expected), and the symlink will be created after 
installing, so how come I still get this?



Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Topic zoekt gedreven (embedded) software specialisten!
http://topic.nl/vacatures/topic-zoekt-software-engineers/



             reply	other threads:[~2014-10-30 14:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 14:17 Mike Looijmans [this message]
2014-10-30 17:47 ` Weird ALTERNATIVES and staging conflict Richard Purdie
2014-11-03  9:53   ` Mike Looijmans
2014-11-03 10:04     ` Richard Purdie
2014-11-03 10:49       ` Mike Looijmans
2014-11-03 11:35         ` Mike Looijmans
2014-11-03 12:09           ` Richard Purdie
2014-11-03 14:11             ` Mike Looijmans
2014-11-03 11:35         ` Richard Purdie

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=5452486B.6070303@topic.nl \
    --to=mike.looijmans@topic.nl \
    --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 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.