On Jan 31, 2013, at 10:50 PM, Bruce Ashfield bruce.ashfi...@windriver.com
wrote:
On 13-01-23 10:17 AM, Patrick Turley wrote:
On Jan 23, 2013, at 7:48 AM, Bruce Ashfieldbruce.ashfi...@windriver.com
wrote:
On 13-01-23 12:34 AM, Patrick Turley wrote:
On Jan 22, 2013, at 11:17 PM, Bruce
On Jan 23, 2013, at 7:48 AM, Bruce Ashfield bruce.ashfi...@windriver.com
wrote:
On 13-01-23 12:34 AM, Patrick Turley wrote:
On Jan 22, 2013, at 11:17 PM, Bruce Ashfield bruce.ashfi...@windriver.com
wrote:
On 13-01-23 12:14 AM, Patrick Turley wrote:
On Jan 22, 2013, at 10:43 PM, Bruce
Here's our machine in local.conf:
MACHINE = dm8148-mpu
Naturally, then, we see a directly like this under tmp/work:
dm8148_mpu-poky-linux-gnueabi
Also, under tmp/sysroots, we see these two:
dm8148-mpu
dm8148-mpu-tcbootstrap
Finally, when I install the SDK, I see the
is that the SDK installation script puts the native
sysroot in one directory, but the tool chain believes the default location for
the native sysroot is in a *different* directory that doesn't exist.
On Wednesday, January 23, 2013, Patrick Turley
patricktur...@gamestop.commailto:patricktur...@gamestop.com
On Jan 23, 2013, at 10:19 AM, Zhang, Jessica jessica.zh...@intel.com wrote:
Please file a bug at bugzilla.yoctoproject.org
Done:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=3784
Thank you.
___
yocto mailing list
yocto@yoctoproject.org
On Jan 21, 2013, at 5:16 PM, Patrick Turley patricktur...@gamestop.com wrote:
On Jan 21, 2013, at 4:35 PM, Zhang, Jessica jessica.zh...@intel.com wrote:
Hi Patrick,
Since you're able to add the dev packages to images, just do bitbake
yourimagewithALSA -c populate_sdk, that should
On Jan 15, 2013, at 1:16 PM, Zhang, Jessica jessica.zh...@intel.com wrote:
For your LDFLAGS question in another email thread, the yocto SDK is mainly
produced for application developer, but seems we are hearing more usage
request for it to support kernel module build as well. As Eric
On Jan 16, 2013, at 11:11 AM, Darren Hart dvh...@linux.intel.com wrote:
On 01/15/2013 10:38 AM, Bruce Ashfield wrote:
I finally found the entries that I was recalling earlier. They are:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=241
On Jan 22, 2013, at 2:34 PM, Bruce Ashfield bruce.ashfi...@windriver.com
wrote:
On 13-01-22 03:28 PM, Patrick Turley wrote:
One problem I ran into … When I tried to execute make scripts, I got a
whole bunch of config questions that I *think* should have been answered
with a .config file
On Jan 22, 2013, at 10:43 PM, Bruce Ashfield bruce.ashfi...@windriver.com
wrote:
On 13-01-22 9:26 PM, Patrick Turley wrote:
If I just hold down the Enter key, I believe all the defaults are taken,
and I eventually *do* get hostprogs that execute, but I don't know if
they're appropriate
On Jan 16, 2013, at 11:11 AM, Darren Hart dvh...@linux.intel.com wrote:
On 01/15/2013 10:38 AM, Bruce Ashfield wrote:
I finally found the entries that I was recalling earlier. They are:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=241
I've been working on re-targeting some code from a vendor's board to our own
board.
For libraries and other low-level code, everything's been fine. For test
applications, I'm running into a dependency on the header file
alsa/asoundlib.h, which is obviously part of ALSA.
I've been building our
On Jan 21, 2013, at 4:35 PM, Zhang, Jessica jessica.zh...@intel.com wrote:
Hi Patrick,
Since you're able to add the dev packages to images, just do bitbake
yourimagewithALSA -c populate_sdk, that should generate a SDK contains ALSA.
By default, meta-toolchain-sdk is predefined unless you
I used the meta-toolchain-sdk recipe to produce an SDK, and I installed it.
Here's an interesting line from the environment setup script:
export LDFLAGS=-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed
All these linker options are preceded by -Wl, which indicates the SDK is
*expecting* them to
-out-of-tree-modules
I just did the exact same thing and was happy to discover there is support in
yocto for doing just this.
Brian
On Mon, 2013-01-14 at 23:27 +, Patrick Turley wrote:
I have to build a module from a third-party that has nothing to do with Yocto.
I want to build this module
, Patrick Turley wrote:
I used the meta-toolchain-sdk recipe to produce an SDK, and I installed it.
Here's an interesting line from the environment setup script:
export LDFLAGS=-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed
All these linker options are preceded by -Wl, which indicates the SDK
On Jan 15, 2013, at 12:00 PM, Bruce Ashfield bruce.ashfi...@windriver.com
wrote:
On 13-01-15 12:54 PM, Patrick Turley wrote:
Thank you for directing me toward that documentation. As it happens, I
have already read that, and it doesn't apply.
There are ways to do this, your requirement
I have to build a module from a third-party that has nothing to do with Yocto.
I want to build this module against the kernel Yocto is giving me.
The Make file for this module has a build command like this:
make -C $(LINUX_DIR) M=`pwd` $(ENV) \
EXTRA_CFLAGS=$(EXTRA_CFLAGS) modules
I'm using a Yocto-based SDK, produced by:
bitbake meta-toolchain-sdk
This creates the file
poky-eglibc-x86_64-arm-toolchain-gmae-1.3.sh
in the directory
build/tmp/deploy/sdk
I ran the installation script to install the SDK on my build system. Within the
SDK installation
We have a piece of software that is normally built with a Code Sourcery tool
chain. We want to build it with a Yocto-produced tool chain instead.
The shortest (though admittedly hackiest) path to success may be to create a
file tree that *looks* like a Code Sourcery tool chain, but is actually
https://github.com/pturley0/bitbake-hello-world
On Oct 9, 2012, at 5:56 PM, McClintock Matthew-B29882 b29...@freescale.com
wrote:
On Tue, Oct 9, 2012 at 5:31 PM, Patrick Turley
patricktur...@gamestop.com wrote:
Success. The file tree depicted at the bottom of this mail is nearly
I just read your posting of 26 June on the Yocto mailing list:
https://lists.yoctoproject.org/pipermail/yocto/2012-June/009714.html
I didn't see any responses. Did you get any help with this issue?
___
yocto mailing list
yocto@yoctoproject.org
Success. The file tree depicted at the bottom of this mail is nearly the
smallest, valid BitBake project that prints Hello, World! Here's the output:
$ ../BitBake/bin/bitbake a
Parsing recipes: 100%
|#| Time: 00:00:00
That's a perfectly reasonable suggestion, and a good excuse for me to open a
github account and learn how to use it :)
On Oct 9, 2012, at 5:56 PM, McClintock Matthew-B29882 b29...@freescale.com
wrote:
On Tue, Oct 9, 2012 at 5:31 PM, Patrick Turley
patricktur...@gamestop.com wrote:
Success
I am continuing my work on creating a Hello, World! BitBake project. Because
of the excellent help I got before, things have gone reasonably well, but I'm
again running into something I don't know how to fix.
As before, the entire contents of my very small project appear at the end of
this
uses 'raw' Bitbake and a very basic recipe
to build the Nano editor (including download from the project site).
You need to have a couple of things in place to make this work. I got to run
but I will get back to it and post it.
:rjs
On Wed, Oct 3, 2012 at 3:56 PM, Patrick Turley
patricktur
*Very* helpful stuff.
I have re-created the tree you described, and everything seems to work. In
particular, bitbake-layers seems happy. I tried executing it against BitBake
1.12.0 and it succeeded. FYI, it failed against the current BitBake master,
which is 1.16.0.
I have some additional
I'll start with my question (so you can decide whether you care to read
the rest):
What is the BitBake equivalent of Hello, World!?
Specifically, what is the minimum project structure that
correctly describes a single layer and a single recipe?
In my previous message, some of the indentation in the representation of
my file tree was wrong (because we're using Outlook, which destroy all
indentation when you paste it into an e-mail message). The errors are
small, but I want to avoid annoying anyone who might think I don't even
have the
29 matches
Mail list logo
