Greeting all.
From package "poco" i get the following warning message:
WARNING: poco-1.7.9-r0 do_package: poco-1.7.9 was registered as shlib
provider for libCppUnit.so.1, changing it to poco-cppunit-1.7.9 because
it was built later
Is this safe to ignore ?
Thanks for your support.
--
On 2017-12-27 12:11 PM, Greg Wilson-Lindberg wrote:
Hi Bruce,
First, the kernel is 4.4.50, the recipe is linux-raspberrypi_4.4.bb in
meta-raspberrypi. My image recipe is based on one from Qt, but it is
using the kernel recipe in meta-raspberry.
I changed my .bbappend to:
# Scribe additions
Hi,
https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/python/python-ironman_0.2.13.bb
-
this is an example recipe for python.
You simply need to change the SRC_URI to point to where your python package
is (tarball generally preferred) by something like
file://path/to/tarball.tar.gz
apt-cache depends gives you the prerequisites of your package
dpkg is your friend to check for installed packages
That above is for debian like distros, for redhat, use rpm -qa or rpm -ql
On Wed, Jan 3, 2018 at 5:16 PM, Rail Shafigulin
wrote:
> I haven't worked with Yocto a lot, so forgive m
Folks,
I'm looking for a recipe that will install a custom python package to the
python site-packages on the rootfs. The Python package uses setuptools and the
standard setup.py and is not available on pypi because I wrote it. In general I
am having difficulty finding a recipe for a custom pack
I haven't worked with Yocto a lot, so forgive me if the question seems
a bit trivial.
I'm working with a Zynq FPGA from Xilinx. I'm trying to build a Linux
image for it. Xilinx is using its own distro called Petalinux. They do
provide a layer called meta-petalinux for building it.
I need to inclu
Hi,
Has anyone used a gitweb interface as a PREMIRROR?
The idea is to version control a GIT repo by adding the tarballs to it
as needed (i.e. to track the changes, etc), and then have a yocto build
access it using the gitweb interface.
I have tried variations of premirror URL expressions like be
On 01/03/2018 09:47 AM, Paul Barker wrote:
> Hi all,
>
> As we've only got one table at FOSDEM this year we're not going to
> have space for as many bits of hardware as usual. I'd still like us to
> show off the project and what people are building with OpenEmbedded &
> Yocto Project though. Given
Just a test, as previous mail didnt get through after 2 hours, nor did a
moderation mail arrive.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Hi Paul,
Thanks for putting this together. I've added a slide at the end with
projects I'm aware of that are using OE/Yocto. I'm sure there are plenty
more to be added though.
Best regards,
Herman
On 2018-01-03 15:47, Paul Barker wrote:
Hi all,
As we've only got one table at FOSDEM this ye
Hi all,
As we've only got one table at FOSDEM this year we're not going to
have space for as many bits of hardware as usual. I'd still like us to
show off the project and what people are building with OpenEmbedded &
Yocto Project though. Given the limited space I think the best way to
do this woul
Greetings.
I'm new to yocto and cross compiling, so i may be wrong interpreting my
situation to begin with...
Post compile i get the message:
ERROR: pylongps-0.1.0-r0 do_package_qa: QA Issue: package pylongps
contains bad RPATH /usr/lib/x86_64-linux-gnu
It seems to me the reason is an entr
On 01/03/2018 06:15 PM, Paul Eggleton wrote:
Hi Robert,
On Wednesday, 3 January 2018 6:23:57 PM NZDT Robert Yang wrote:
On 12/27/2017 09:23 PM, Robert Yang wrote:
We have 124 layers, the "update.py -b " costs about 10 minutes to
finish the update for one branch, and we need update several b
Hi Robert,
On Wednesday, 3 January 2018 6:23:57 PM NZDT Robert Yang wrote:
> On 12/27/2017 09:23 PM, Robert Yang wrote:
> > We have 124 layers, the "update.py -b " costs about 10 minutes to
> > finish the update for one branch, and we need update several branches
> > periodly, which is really a l
14 matches
Mail list logo
