Hi,
I'm dealing with a product which needs a hacked-up X server using a
proprietary graphics vendor's video controller. It's easiest just to
make a separate recipe to do this, which pastes in and then modifies
as appropriate the contents of xserver-kdrive-common.inc and
xserver-kdrive_1.3.0.0.bb.
This all works fine to build, and even can be addressed directly by
the name "virtual/xserver" by bitbake commands once I've configured my
machine conf file to prefer this provider of virtual/xserver:
$ bitbake virtual/xserver
NOTE: Handling BitBake files: / (0761/0761) [100 %]
NOTE: Parsing finished. 737 cached, 0 parsed, 24 skipped, 0 masked.
NOTE: build 200708201612: started
OE Build Configuration:
BB_VERSION = "1.8.5"
OE_REVISION = "<unknown>"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "my-machine"
DISTRO = "my-distro"
DISTRO_VERSION = "0.0-snapshot-20070820"
TARGET_FPU = "soft"
NOTE: Resolving missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Tasks Summary: Attempted 499 tasks of which 499 didn't need to
be rerun and 0 failed.
NOTE: build 200708201612: completed
As soon as I try to use this in a task which RDEPENDS on
"virtual/xserver", though, Bitbake complains:
$ bitbake task-blah
...
ERROR: No providers of runtime build target virtual/xserver ('for
['/projects/poky.my-machine/meta/packages/tasks/task-blah.bb'])
I noticed that task-poky uses "${XSERVER}" rather than
"virtual/xserver"; are virtual things purely build-time namespaces and
not visible to the RDEPENDS clauses?
-- To unsubscribe send a mail to poky+unsubscribe@o-hand.comReceived on Mon, 20 Aug 2007 16:21:58 -0500
This archive was generated by hypermail 2.1.8 : Mon Aug 20 2007 - 18:00:10 EDT