I have a recipe that I built for building jzmq, however one of the
issues I have is with the naming of the release files from the github site.
Unlike czmq which has downloads ( zip and tar.gz ) that are named
czmq-${PV}.tar.gz, the downloads from jzmq are just called v${PV}.tar.gz.
How can
Hi,
Do to a fun "feature" of zeromq, the newest libraries are not backward
compatible and hence I need to install a zeromq-4.1.5 and zeromq-3.2.2
libraries onto my target to assist with one application using the old
version and a newer application using the newer one.
How can I do this
Hi,
I've gotten almost all of my files downloaded using a local mirror for a
new build. I'm having trouble debugging one specific case where it
appears my mirror rules can't find the package that it should be finding
in the local mirror directory. This is my hypothesis as I've worked
http://.*/.* file://media/build/mirror/ \n \
svn://.*/.*file://media/build/mirror/ \n \
https://.*/.*file://media/build/mirror/ \n \
"
BB_FETCH_PREMIRRORONLY = "1"
SOURCE_MIRROR_URL ?= "file:///media/build/mirror/"
On 06/28/2017 12:39 PM, Jimi Damon wrote:
Hi,
Fixed : PEBKAC
I needed the two following elements
MIRRORS ?= "\
git://.*/.*file://media/build/mirror/ \n \
git://.*/.*/.* file://media/build/mirror/ \n \
ftp://.*/.*file://media/build/mirror/ \n \
http://.*/.* file://media/build/mirror/ \n \
svn://.*/.*
Hi,
I'm trying to save the entire build PLUS the tools used to create the
build and I'm finding that when I initially perform the
bitbake -c fetchall b2qt-embedded-qt5-image
followed by a copy of the required downloaded .tar.gz files to the
mirror directory and then creating a new build
Hi,
I've added zeromq to a build by adding the meta-iot-cloud layer. This
adds zeromq to the target rootfs, but I can't get this added to the host
rootfs when I create an sdk ( using bitbake -c populate_sdk
core-image-minimal ).
I've read about adding something like
username.
I'm not sure which setting in my bash shell is causing this error so I'm
all ears for any suggestions.
-Jimi
On 06/15/2017 01:47 AM, Paul Eggleton wrote:
On Thursday, 15 June 2017 5:12:19 AM CEST Gary Thomas wrote:
On 2017-06-15 01:58, Jimi Damon wrote:
I'm trying out two differe
Thursday, 15 June 2017 5:12:19 AM CEST Gary Thomas wrote:
On 2017-06-15 01:58, Jimi Damon wrote:
I'm trying out two different yocto distributions and in each one the
devshell doens't work. Instead it just gets to the
Summary line and returns to my normal shell ( bash ) .
What are you expecting to hap
Hi ,
I'm trying out two different yocto distributions and in each one the
devshell doens't work. Instead it just gets to the Summary line and
returns to my normal shell ( bash ) .
I'm invoking it with
bitbake -c devshell core-image-minimal
bitbake --version = 1.32.0
I'm getting my
Yes that's very good in the theoretical, but I was looking for actual
commands to get this done.
Solution was from Leo Sandoval,
COMPATIBLE_HOST = "null"
inside of the chromium_52.0.2743.76.bbappend
On 06/13/2017 02:56 PM, Burton, Ross wrote:
The canonical solution here is to write
possible.
Thanks
On 06/13/2017 12:55 PM, Leonardo Sandoval wrote:
On Tue, 2017-06-13 at 12:26 -0700, Jimi Damon wrote:
This package is being built on the host side during a bitbake using a
Boundary Devices Yocto build (
MACHINE=nitrogen6x DISTRO=fslc-x11 . setup-environment build
since the compilation takes quite a long time for Chromium.
On 06/13/2017 12:32 PM, Leonardo Sandoval wrote:
On Tue, 2017-06-13 at 11:32 -0700, Jimi Damon wrote:
Hi,
I tried using the PACKAGE_EXCLUDE = "chromium" in my local.conf file
but I'm finding that my build it is still tryin
Hi,
I tried using the PACKAGE_EXCLUDE = "chromium" in my local.conf file but
I'm finding that my build it is still trying to build this package.
Is there a way to prevent this build stage from occurring ?
Thanks
--
___
yocto mailing list
14 matches
Mail list logo
