A couple weeks ago, several people here were kind enough to help me through
the process of adding the OpenEmbedded layer called
meta-openembedded/meta-oe to my core-image-base-cedartrail-nopvr build,
which I wanted because it contains Samba. I eventually got it to build
without errors. But still
* Paul D. DeRocco pdero...@ix.netcom.com [130327 09:09]:
The log file shows that the layer.conf file for that layer is being read,
and there is indeed some recipes for Samba. The bitbake -s option lists
samba as one of the packages. But the logs only show a few of recipes being
processed from
On 26 March 2013 20:04, Trevor Woerner twoer...@gmail.com wrote:
On Tue, Mar 26, 2013 at 2:37 PM, Burton, Ross ross.bur...@intel.com wrote:
Danni would be a terrible name
Of course it would be a terrible name, that's why I suggested it; I
figured it'd fit in with the others :-D
(don't
Mark,
Option 1 isn't a very big concern since it's likely only developers working
on the restricted code will cause its hashes to permute.
Option 2 is precisely what we were thinking about doing. The concern,
though, is what happens when a developer who doesn't have access to the
code changes a
While this may not resolve your problem, these are my 0.2 cents.
I assume you already know this:
The hash does not need to be permuted between dependency updates, as
(e.g.) eglibc promises ABI and API stability between major releases
(like most Linux libraries).
This means that the hash has to
Hi Jessica,
What is the issue that Time found you are referring to ?
Regarding the way you found to allow creating projects with invalid names, this
comes from the org.eclipse.cdt.core.templates, and in my opinion is a bug.
What happens is that the template arguments, in our case the project
Hi all,
I've recently been faced the need to support an upgrade path for a system
designed with Yocto. The format for packages is currently ipk.
While the system was under development, I was heavily relying on package
feeds and opkg update/upgrade based upgrades. However, once deployed, this
From: Anders Darander
Maybe a dumb question...
Have you added samba to the image that you're building?
Just adding a layer won't cause the added recipes to be built and
deployed.
It's not a dumb question. No, I haven't added samba to the image that I'm
building. I've read the Yocto
From: ChenQi
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html
section 5.2 Customizing Images
In your case, you could add the following line to local.conf.
IMAGE_INSTALL_append += samba
And you can use 'bitbake -g image_recipe_name' to see
whether samba is pulled
On 03/28/2013 11:10 AM, Paul D. DeRocco wrote:
From: ChenQi
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html
section 5.2 Customizing Images
In your case, you could add the following line to local.conf.
IMAGE_INSTALL_append += samba
And you can use 'bitbake -g
* Paul D. DeRocco pdero...@ix.netcom.com [130328 04:11]:
From: ChenQi
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html
section 5.2 Customizing Images
In your case, you could add the following line to local.conf.
IMAGE_INSTALL_append += samba
And you can use
11 matches
Mail list logo
