Hi,
I am building images for Intel Quark and have successfully setup and built
images.
Now there is a new BSP out, and I am not sure how to use it.
Do I have to start from scratch with this new BSP?
Can I add it to my existing build and tell bitbake to rebuild?
- How would I do that?
Folks,
I'm trying to create a recipe for Adafruit's BeagleBone IO Python Library:
https://github.com/adafruit/adafruit-beaglebone-io-python
The problem is that this python package generates some dtbos and install
them on /lib/firmware but these files were not presented on generated
package.
Here
It would help if you provided more context, but this might be what you are
looking for -
http://cgit.openembedded.org/cgit.cgi/openembedded-core/tree/meta/recipes-core/systemd/systemd-serialgetty.bb?h=master
Adam
On Tue, Jan 28, 2014 at 4:38 AM, Rohit2 Jindal wrote:
> Hi,
>
>
>
>
>
> I s there
I am not sure if that's the correct behaviour at all. If you are building
the kernel, it should only build the kernel (and its deps).
How are you building it? I suppose you are doing 'bitbake virtual/kernel',
but just checking!
Adam
On Wed, Jan 29, 2014 at 12:09 PM, Alex J Lennon <
ajlen...@dyna
Hi, sorry this is a last-minute question.
I'm throwing together slides for my talk at FOSDEM on Sunday and I
could do with decent copies of the Yocto Project and OpenEmbedded
logos to include where appropriate. I think having good images of the
correct logos when I'm talking about OE/Yocto will he
Hi Adam,
On 30/01/2014 18:40, Adam Lee wrote:
I am not sure if that's the correct behaviour at
all. If you are building the kernel, it should only build the
kernel (and its deps).
How are you building it? I suppose you are doing 'bitbake
Hi Paul,
I had similar trouble today. I couldn't for the life of me find a
nice SVG of the Yocto logo,
although I did scan through the brand guidelines pdf. They seem to
point to the website
but in the end I just scaled up the PDF and grabbed a capture from
t
Hi Alex, so are you bitbaking the entire image every time you make a change
to the kernel (The .bb file you linked is the image recipe)?
If you only build the kernel (ie bitbake virtual/kernel), your system
shouldn't build the entire image.
Let me know!
Adam
On Thu, Jan 30, 2014 at 3:11 PM, Ale
On 30/01/2014 23:54, Adam Lee wrote:
Hi Alex, so are you bitbaking the entire image
every time you make a change to the kernel (The .bb file you
linked is the image recipe)?
If you only build the kernel (ie bitbake virtual/kernel),
y
I see. Why not just build the kernel image (uImage) and copy the file over
to your /boot partition? That way you don't have to build and as well as
write an entire image to ur card, saving you some time.
On Thu, Jan 30, 2014 at 4:00 PM, Alex J Lennon <
ajlen...@dynamicdevices.co.uk> wrote:
>
>
I see this example in the doc:
# We have a conf and classes directory, add to BBPATH
BBPATH := "${BBPATH}:${LAYERDIR}"
# We have a recipes directory containing both .bb and .bbappend files, add to
BBFILES
BBFILES := "${BBFILES} ${LAYERDIR}/recipes/*/*.bb \
${LAYERDIR}/recipes/*/*.b
Correction, the function should be get_file_layer, but the same logic is used
in that function:
def get_file_layer(self, filename):
for layer, _, regex, _ in
self.bbhandler.cooker.recipecache.bbfile_config_priorities:
if regex.match(filename):
for layerdir
Hi all,
I'm currently playing with Yocto 1.4, and I have few questions about
generated SDKs.
1/ The sysroot seems to be hardcoded in binaries, for instance:
$
/opt/poky/1.4.2/sysroots/x86_64-pokysdk-linux/usr/bin/armv6-vfp-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc
--print-sysroot
/opt/poky/1.
Hello,
I have a build issue. I'm trying to write a Bitbake recipe for jsoncpp, which
uses SConstruct. My .bb file is at
https://gist.github.com/thirtythreeforty/8725055. When I run it, Bitbake
complains,
| DEBUG: Executing shell function do_compile
| Traceback (most recent call last):
| Fi
14 matches
Mail list logo
