Hello,
On Thu, 2012-02-16 at 10:26 +0530, Joshua Immanuel wrote:
Can you please explain little bit more on what INSANE_SKIP_${PN} =
dev-so does. I don't find any documentation on it.
I guess, it suppresses the warnings stating that an non-dev package
contains symlink. This is the warning I
On Thursday, February 16, 2012, Autif Khan autif.ml...@gmail.com wrote:
Hello,
On Thu, 2012-02-16 at 10:26 +0530, Joshua Immanuel wrote:
Can you please explain little bit more on what INSANE_SKIP_${PN} =
dev-so does. I don't find any documentation on it.
I guess, it suppresses the warnings
I'm trying to figure out how to use a cloned/modified copy of the
linux-yocto-3.0 git repository. Here's what I did:
* cloned linux-yocto-3.0.git and committed to the meta branch
* specified my new repo:
--- a/meta/recipes-kernel/linux/linux-yocto_3.0.bb
+++
On Thu, Feb 16, 2012 at 8:16 PM, Hollis Blanchard
hollis_blanch...@mentor.com wrote:
I'm trying to figure out how to use a cloned/modified copy of the
linux-yocto-3.0 git repository. Here's what I did:
* cloned linux-yocto-3.0.git and committed to the meta branch
* specified my new repo:
On Thu, Feb 16, 2012 at 9:33 PM, Hollis Blanchard
hollis_blanch...@mentor.com wrote:
Yeah, I've looked through there, but where should stdout (i.e. those echo
commands) be appearing?
I'd guess it's failing before that... you can add your own echo's.
Also, this should be in that log file:
On 02/16/2012 01:43 PM, McClintock Matthew-B29882 wrote:
On Thu, Feb 16, 2012 at 9:33 PM, Hollis Blanchard
hollis_blanch...@mentor.com wrote:
Yeah, I've looked through there, but where should stdout (i.e. those echo
commands) be appearing?
I'd guess it's failing before that... you can add
Last week, we announced the MEL Kit support for both the BeagleBoard and the
PandaBoard. This week, we are announcing the availability of MEL Kits for
emulated target environments. This should be handy for those that want to
check out CodeBench Lite or MEL Lite, but you lack hardware.
On 12-02-16 03:16 PM, Hollis Blanchard wrote:
I'm trying to figure out how to use a cloned/modified copy of the
linux-yocto-3.0 git repository. Here's what I did:
* cloned linux-yocto-3.0.git and committed to the meta branch
* specified my new repo:
Very strange. Is this from the yocto master
On 12-02-16 05:06 PM, Hollis Blanchard wrote:
On 02/16/2012 01:43 PM, McClintock Matthew-B29882 wrote:
On Thu, Feb 16, 2012 at 9:33 PM, Hollis Blanchard
hollis_blanch...@mentor.com wrote:
Yeah, I've looked through there, but where should stdout (i.e. those
echo
commands) be appearing?
I'd
On 02/16/2012 02:11 PM, Bruce Ashfield wrote:
On 12-02-16 03:16 PM, Hollis Blanchard wrote:
I'm trying to figure out how to use a cloned/modified copy of the
linux-yocto-3.0 git repository. Here's what I did:
* cloned linux-yocto-3.0.git and committed to the meta branch
* specified my new
On 12-02-16 05:50 PM, Hollis Blanchard wrote:
On 02/16/2012 02:11 PM, Bruce Ashfield wrote:
On 12-02-16 03:16 PM, Hollis Blanchard wrote:
I'm trying to figure out how to use a cloned/modified copy of the
linux-yocto-3.0 git repository. Here's what I did:
* cloned linux-yocto-3.0.git and
On 12-02-16 06:18 PM, Hollis Blanchard wrote:
On 02/16/2012 03:02 PM, Bruce Ashfield wrote:
That's the problem. I have a patch that detects this and abort is a non
bare upstream is used. I just need to send them .. which I'll do when
I get back to my desk next week.
There are two reason for
On 02/16/2012 03:25 PM, Bruce Ashfield wrote:
The point is that the tree is local to your machine, but it doesn't
have to be. You may only have push, not direct commit access. It's
really not asking for anything that isn't already common practice.
Hmm, I'm not at all a git expert, but I
On 12-02-16 06:52 PM, Hollis Blanchard wrote:
On 02/16/2012 03:25 PM, Bruce Ashfield wrote:
The point is that the tree is local to your machine, but it doesn't
have to be. You may only have push, not direct commit access. It's
really not asking for anything that isn't already common practice.
I'm using the ecipse-plugin:
http://autobuilder.yoctoproject.org/pub/nightly/20120216-2/eclipse-plugin/indigo/org.yocto.sdk-rc1-201202161547-archive.zip
my build tree is following the latest yocto git tree:
git://git.yoctoproject.org/poky.git
and when assign the build tree as toolchain directory
and there is no use to change DISTRO_VERSION in
build_tree/tmp/tmp/environment-setup-ppc603e-insigma-linux.
On Fri, 2012-02-17 at 10:42 +0800, 倪庆亮 wrote:
I'm using the ecipse-plugin:
http://autobuilder.yoctoproject.org/pub/nightly/20120216-2/eclipse-plugin/indigo/org.yocto.sdk-rc1-201202161547
the environment-setup file in build tree had defined CFLAGS and CXXFLAGS
which include the sysroot argument(build_tree/tmp/sysroots/machine).
Do we must specify the sysroot location in the eclipse plugin?
after specify it, I found the CFLAGS CXXFLAGS in project property follow
it, and dropped
Ni Qingliang wrote on 2012-02-17:
the environment-setup file in build tree had defined CFLAGS and CXXFLAGS
which include the sysroot argument(build_tree/tmp/sysroots/machine).
Do we must specify the sysroot location in the eclipse plugin?
after specify it, I found the CFLAGS CXXFLAGS in
18 matches
Mail list logo
