Re: [yocto] Fwd: Yocto

[Khem Raj]

I think you can effectively build your own image with QT, it seems to
me thats what you are interested in. For that
you would be able to create a new recipe which includes the
core-image-minimal recipe and then adds the needed
QT packages and packagegroups via CORE_IMAGE_EXTRA_INSTALL.

On Fri, May 25, 2018 at 6:18 AM, Scott Rifenbark  wrote:
> Hi Nikhil,
>
> I am forwarding your email to the Yocto Project email group.  Someone there
> can better help you with your questions.  I take care of the Yocto manual
> set.
>
> Thanks,
> Scott Rifenbark
>
> -- Forwarded message -
> From: nikh kkvv 
> Date: Fri, May 25, 2018, 6:03 AM
> Subject: Yocto
> To: 
>
>
> Hi srifenbark,
>
>
> I am Nikhil working as soft ware engineer in kerala.
>
> Currently i am working with a project which require yocto based file system.
> I am using sama5d36-xplained evaluation kit.
>
> Based on the information from the following site
> http://www.at91.com/linux4sam/bin/view/Linux4SAM/YoctoProject build a file
> system which support qt images and tested successfully.
>
> Is there any way to  avoid this demo images from this build and add qt
> support for bitbake core-image minimal process.
>
>
> Regards
> Nikhil
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Fwd: Yocto

[Scott Rifenbark]

-- Forwarded message -
From: Scott Rifenbark 
Date: Fri, May 25, 2018, 6:18 AM
Subject: Fwd: Yocto
To: 


Hi Nikhil,

I am forwarding your email to the Yocto Project email group.  Someone there
can better help you with your questions.  I take care of the Yocto manual
set.

Thanks,
Scott Rifenbark

-- Forwarded message -
From: nikh kkvv 
Date: Fri, May 25, 2018, 6:03 AM
Subject: Yocto
To: 


Hi srifenbark,


I am Nikhil working as soft ware engineer in kerala.

Currently i am working with a project which require yocto based file system.
I am using sama5d36-xplained evaluation kit.

Based on the information from the following site
http://www.at91.com/linux4sam/bin/view/Linux4SAM/YoctoProject build a file
system which support qt images and tested successfully.

Is there any way to  avoid this demo images from this build and add qt
support for bitbake core-image minimal process.


Regards
Nikhil
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Fwd: Yocto

[Scott Rifenbark]

Hi Nikhil,

I am forwarding your email to the Yocto Project email group.  Someone there
can better help you with your questions.  I take care of the Yocto manual
set.

Thanks,
Scott Rifenbark

-- Forwarded message -
From: nikh kkvv 
Date: Fri, May 25, 2018, 6:03 AM
Subject: Yocto
To: 


Hi srifenbark,


I am Nikhil working as soft ware engineer in kerala.

Currently i am working with a project which require yocto based file system.
I am using sama5d36-xplained evaluation kit.

Based on the information from the following site
http://www.at91.com/linux4sam/bin/view/Linux4SAM/YoctoProject build a file
system which support qt images and tested successfully.

Is there any way to  avoid this demo images from this build and add qt
support for bitbake core-image minimal process.


Regards
Nikhil
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: Yocto Layers not getting recognized by bitbake

[varun bhatnagar]

Hi Paul,

I am pasting the content of my recipe file below, please have a look at it.


DESCRIPTION = bitake file
*DEPENDS = net-snmp fuse*
RDEPENDS = curl rpm openssh openldap procps psmisc sed net-snmp-server
LICENSE = GPLv2+
PR = r0
SRC_URI = *file:///home/user/Myapp.tar.gz*file:///home/user/Myapp.tar.gz%22
;
EXTRA_OECMAKE += -DCMAKE_FIND_ROOT_PATH=${STAGING_DIR_HOST} 
EXTRA_OECMAKE += -DTARGET_ARCHITECTURE=${TARGET_ARCH} 
EXTRA_OECMAKE += -DCMAKE_SYSTEM_NAME=Linux 
EXTRA_OECMAKE += -DCMAKE_SYSTEM_VERSION=1 
EXTRA_OECMAKE += -DRSTATE=${PR} 
EXTRA_OECMAKE += -DCMAKE_FIND_ROOT_PATH_MODE_PROGRAM=NEVER 
EXTRA_OECMAKE += -DCMAKE_FIND_ROOT_PATH_MODE_LIBRARY=ONLY 
EXTRA_OECMAKE += -DCMAKE_FIND_ROOT_PATH_MODE_INCLUDE=ONLY 
EXTRA_OECMAKE += -DRPM=1 

inherit cmake

do_configure(){
cmake ..${EXTRA_OECMAKE}
}

do_compile(){
oe_runmake all
}

//
Varun


On Mon, Jul 1, 2013 at 3:18 PM, Paul Eggleton paul.eggle...@linux.intel.com
 wrote:

 On Sunday 30 June 2013 00:05:58 varun bhatnagar wrote:
  Yes Paul that was the entry was there in CORE_IMAGE_EXTRA_INSTALL. I have
  removed it from there but I need to add the command provided by these
  packages in my image. So I have added one line in my layer.conf file
  IMAGE_INSTALL_append= test-ea . Now if I try to run bitbake -k
  core-image-minimal, it gives me a message saying Nothing provides
  test-ea. What shall I do? (I have build the recipe file of test-ea
 without
  any error.)

 Can you show me what the test-ea recipe contains?

 Cheers,
 Paul

 --

 Paul Eggleton
 Intel Open Source Technology Centre

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: Yocto 1.4: Bad behavior between rm_work and packaging causing failures?

[Paul Eggleton]

Hi Jerrod,

On Monday 08 July 2013 09:25:12 Jerrod Peach wrote:
 Re-sending as we've hit another rash of these issues and it ate up a couple
 days of investigation that still led to no resolution or figuring out how
 to reproduce it.  I'm going to log a bug in a day or so, even though my
 information is incomplete, if no one knows what's going on here and can
 explain how to avoid it (other than turning rm_work off, which I suspect
 would fix the problem but cost us a bunch of disk space as a trade-off).
 
 -- Forwarded message --
 From: Jerrod Peach pea...@lexmark.com
 Date: Thu, Jun 13, 2013 at 12:28 PM
 Subject: Yocto 1.4: Bad behavior between rm_work and packaging causing
 failures?
 To: yocto yocto@yoctoproject.org
 
 
 All,
 
 Since upgrading to Yocto 1.4, several people at our organization have
 noticed a couple of weird build failures related to rm_work and packaging.
  Here are the two failure scenarios:
 
 1) A user builds package, but bitbake only re-runs the do_pkg_write_rpm
 task without having run any other build tasks.  This appears to be due to a
 supposedly-valid stamp file existing for the other tasks in the task graph.
  This would normally result in an empty rpm being created, but the rpm
 creation code (smartly) refuses to create empty rpms.  This, then, causes a
 build failure during image creation (if the package is needed for the
 image, of course) because the rpm isn't present.  We think this situation
 leads to the second failure we see.
 
 2) Whether a build succeeds or fails, if it's run on our build
 infrastructure, we upload its sstate to an sstate mirror.  sstate is still
 uploaded for the do_package_write_rpm task in case 1 for builds performed
 on our infrastructure.  That means the sstate, then, contains no rpm for
 the package in question.  This causes later builds to fail with the same
 error as in case 1 (the rpm isn't present when the image needs it), but for
 a different reason (getting a hit on poisoned sstate).
 
 We do not know how to reproduce this problem.  We think it's related to
 commit f090c15 (in the poky repo), but we haven't had much time to
 investigate further.  I suspect there is only one bug to fix here (i.e.,
 whatever is causing stamp files to incorrectly exist), but since there are
 some number of unknowns here, I thought I'd be better off describing the
 whole situation, just in case.
 
 Has anyone else seen this?  Does anyone have ideas as to what's causing it?

I haven't seen this, but then I don't often run with rm_work enabled. I have 
asked Martin Jansa (the OE rm_work expert, who also made the change you have 
pointed to) about it but he has not seen any similar issues in his setup.

I think it's probably worth concentrating on the first issue. I can run some 
tests, but the question is are you able to elaborate on what builds might have 
been done before the user runs the problem build, and the nature of any 
changes that were made between prior builds and the failing build? Are you 
adding any custom tasks in your setup at all?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: Yocto 1.4: Bad behavior between rm_work and packaging causing failures?

[Jerrod Peach]

 I think it's probably worth concentrating on the first issue. I can run
 some
 tests, but the question is are you able to elaborate on what builds might
 have
 been done before the user runs the problem build, and the nature of any
 changes that were made between prior builds and the failing build? Are you
 adding any custom tasks in your setup at all?

 Cheers,
 Paul


Paul,

So, I just came to a realization: We don't have any commonalities in tasks
being added (or whether tasks are added at all) in the packages we saw it
in.  However, we are running the builds automatically through Jenkins (the
open source continuous integration software, if you're not familiar with
it).  We've never seen this on a build that wasn't run through Jenkins,
though we've only seen it twice, so that's not saying a whole lot.  We're
wondering if a build aborted through Jenkins gets a SIGKILL, and if it does
AND that happens during rm_work, I bet that could cause this problem.
 Granted, this is all speculation, and we don't even know if the failures
occurred immediately after aborted builds, but that's the only thing my
colleagues and I can think of right now.

If you do want to continue investigating (which might be worthwhile, as our
speculation could be totally off-base), the packages from poky with which
we had this problem were eglibc-mtrace and systemd-serialgetty.  (We had
the problem with 5 other packages, but they're all custom packages of
ours.)  I find the latter particularly interesting, as that recipe seems to
be quite boring aside from its several python functions.  That makes me
think even more that we're seeing some weird combination of factors in our
Jenkins builds.

Kind regards,

Jerrod
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Fwd: Yocto 1.4: Bad behavior between rm_work and packaging causing failures?

[Jerrod Peach]

Re-sending as we've hit another rash of these issues and it ate up a couple
days of investigation that still led to no resolution or figuring out how
to reproduce it.  I'm going to log a bug in a day or so, even though my
information is incomplete, if no one knows what's going on here and can
explain how to avoid it (other than turning rm_work off, which I suspect
would fix the problem but cost us a bunch of disk space as a trade-off).

-- Forwarded message --
From: Jerrod Peach pea...@lexmark.com
Date: Thu, Jun 13, 2013 at 12:28 PM
Subject: Yocto 1.4: Bad behavior between rm_work and packaging causing
failures?
To: yocto yocto@yoctoproject.org


All,

Since upgrading to Yocto 1.4, several people at our organization have
noticed a couple of weird build failures related to rm_work and packaging.
 Here are the two failure scenarios:

1) A user builds package, but bitbake only re-runs the do_pkg_write_rpm
task without having run any other build tasks.  This appears to be due to a
supposedly-valid stamp file existing for the other tasks in the task graph.
 This would normally result in an empty rpm being created, but the rpm
creation code (smartly) refuses to create empty rpms.  This, then, causes a
build failure during image creation (if the package is needed for the
image, of course) because the rpm isn't present.  We think this situation
leads to the second failure we see.

2) Whether a build succeeds or fails, if it's run on our build
infrastructure, we upload its sstate to an sstate mirror.  sstate is still
uploaded for the do_package_write_rpm task in case 1 for builds performed
on our infrastructure.  That means the sstate, then, contains no rpm for
the package in question.  This causes later builds to fail with the same
error as in case 1 (the rpm isn't present when the image needs it), but for
a different reason (getting a hit on poisoned sstate).

We do not know how to reproduce this problem.  We think it's related to
commit f090c15 (in the poky repo), but we haven't had much time to
investigate further.  I suspect there is only one bug to fix here (i.e.,
whatever is causing stamp files to incorrectly exist), but since there are
some number of unknowns here, I thought I'd be better off describing the
whole situation, just in case.

Has anyone else seen this?  Does anyone have ideas as to what's causing it?

Kind regards,

Jerrod
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: Yocto Layers not getting recognized by bitbake

[Paul Eggleton]

On Sunday 30 June 2013 00:05:58 varun bhatnagar wrote:
 Yes Paul that was the entry was there in CORE_IMAGE_EXTRA_INSTALL. I have
 removed it from there but I need to add the command provided by these
 packages in my image. So I have added one line in my layer.conf file
 IMAGE_INSTALL_append= test-ea . Now if I try to run bitbake -k
 core-image-minimal, it gives me a message saying Nothing provides
 test-ea. What shall I do? (I have build the recipe file of test-ea without
 any error.)

Can you show me what the test-ea recipe contains?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: Yocto Layers not getting recognized by bitbake

[varun bhatnagar]

Yes Paul that was the entry was there in CORE_IMAGE_EXTRA_INSTALL. I have
removed it from there but I need to add the command provided by these
packages in my image. So I have added one line in my layer.conf file
IMAGE_INSTALL_append= test-ea . Now if I try to run bitbake -k
core-image-minimal, it gives me a message saying Nothing provides
test-ea. What shall I do? (I have build the recipe file of test-ea without
any error.)


On Fri, Jun 28, 2013 at 1:55 AM, Paul Eggleton 
paul.eggle...@linux.intel.com wrote:

 On Thursday 27 June 2013 23:28:05 varun bhatnagar wrote:
   Thanks a ton Paul and Saul for the reply. Your suggestion worked. :)
  But after building my recipe file I executed bitbake -k
 core-image-minimal
  and I got the following error:
 
  NOTE: Resolving any missing task queue dependencies
  Missing or unbuildable dependency chain was: ['app-ea']
  ERROR: Nothing RPROVIDES 'app-ea' (but
  /local/varun/poky-yocto-1.4-m3/meta/recipes-core/images/
  core-image-minimal.bb RDEPENDS on or otherwise requires it)
  NOTE: Runtime target 'com-ea' is unbuildable, removing...
  Missing or unbuildable dependency chain was: ['test-ea']
  ERROR: Nothing RPROVIDES 'tipcutils' (but
  /local/varun/poky-yocto-1.4-m3/meta/recipes-core/images/
  core-image-minimal.bb RDEPENDS on or otherwise requires it)
  NOTE: Runtime target 'tipcutils' is unbuildable, removing...
  Missing or unbuildable dependency chain was: ['tipcutils']
  NOTE: Preparing runqueue
  ERROR: All buildable tasks have been run but the build is incomplete
  (--continue mode). Errors for the tasks that failed will have been
 printed
  above.
 
  Summary: There were 3 ERROR messages shown, returning a non-zero exit
 code.
 
 
  Any idea how to resolve this one?

 None of com-ea, test-ea or tipcutils are normally in
 core-image-minimal
 nor are they in any OE layer that I am aware of. I can only suggest that
 you
 might have added these to CORE_IMAGE_EXTRA_INSTALL, is that correct? If so,
 either remove these or ensure they actually exist somewhere in an enabled
 layer where that layer has BBFILES correctly set up in its conf/layer.conf
 file
 to match the directory structure of the layer.

 Cheers,
 Paul

 --

 Paul Eggleton
 Intel Open Source Technology Centre

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: Yocto Layers not getting recognized by bitbake

[varun bhatnagar]

 Thanks a ton Paul and Saul for the reply. Your suggestion worked. :)
But after building my recipe file I executed bitbake -k core-image-minimal
and I got the following error:

NOTE: Resolving any missing task queue dependencies
Missing or unbuildable dependency chain was: ['app-ea']
ERROR: Nothing RPROVIDES 'app-ea' (but
/local/varun/poky-yocto-1.4-m3/meta/recipes-core/images/
core-image-minimal.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'com-ea' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['test-ea']
ERROR: Nothing RPROVIDES 'tipcutils' (but
/local/varun/poky-yocto-1.4-m3/meta/recipes-core/images/
core-image-minimal.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'tipcutils' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['tipcutils']
NOTE: Preparing runqueue
ERROR: All buildable tasks have been run but the build is incomplete
(--continue mode). Errors for the tasks that failed will have been printed
above.

Summary: There were 3 ERROR messages shown, returning a non-zero exit code.


Any idea how to resolve this one?

//
Varun
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: Yocto Layers not getting recognized by bitbake

[Paul Eggleton]

On Thursday 27 June 2013 23:28:05 varun bhatnagar wrote:
  Thanks a ton Paul and Saul for the reply. Your suggestion worked. :)
 But after building my recipe file I executed bitbake -k core-image-minimal
 and I got the following error:
 
 NOTE: Resolving any missing task queue dependencies
 Missing or unbuildable dependency chain was: ['app-ea']
 ERROR: Nothing RPROVIDES 'app-ea' (but
 /local/varun/poky-yocto-1.4-m3/meta/recipes-core/images/
 core-image-minimal.bb RDEPENDS on or otherwise requires it)
 NOTE: Runtime target 'com-ea' is unbuildable, removing...
 Missing or unbuildable dependency chain was: ['test-ea']
 ERROR: Nothing RPROVIDES 'tipcutils' (but
 /local/varun/poky-yocto-1.4-m3/meta/recipes-core/images/
 core-image-minimal.bb RDEPENDS on or otherwise requires it)
 NOTE: Runtime target 'tipcutils' is unbuildable, removing...
 Missing or unbuildable dependency chain was: ['tipcutils']
 NOTE: Preparing runqueue
 ERROR: All buildable tasks have been run but the build is incomplete
 (--continue mode). Errors for the tasks that failed will have been printed
 above.
 
 Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
 
 
 Any idea how to resolve this one?

None of com-ea, test-ea or tipcutils are normally in core-image-minimal 
nor are they in any OE layer that I am aware of. I can only suggest that you 
might have added these to CORE_IMAGE_EXTRA_INSTALL, is that correct? If so, 
either remove these or ensure they actually exist somewhere in an enabled 
layer where that layer has BBFILES correctly set up in its conf/layer.conf file 
to match the directory structure of the layer.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: Yocto Layers not getting recognized by bitbake

[Paul Eggleton]

On Sunday 23 June 2013 00:34:17 varun bhatnagar wrote:
 I am trying to compile my code using yocto. For that I have created two
 layers: meta-networking and meta-oe. I have added these dependencies in
 bblayer.conf too. But these are not getting build. Can anyone please tell
 me what should I do to make this work.
 
 //
 Varun
 
 --
 From: *Gary Thomas* g...@mlbassoc.com
 Date: Mon, Jun 17, 2013 at 11:03 PM
 To: yocto@yoctoproject.org
 
 
 More details are needed to be able to help.
 
 What do you mean not getting built?  Do you mean that if you
 try to build recipe XYZ which is in one of those layers that it's
 not being built?  Or perhaps you mean something else?
 
 What do you mean created two layers: ...?  Did you just extract
 these from meta-openembedded?  or something else?
 
  I am building one of my application using yocto by giving bitbake -k
  core-image-minimal command but I am facing some errors as this application
  requires two libraries
  *1) net-snmp*
  *2) fuse*
  *
  
  *
  I have one link where in they are asking to add these two libraries in the
  form of layers and then execute bitbake -k core-image-minimal command.
  
  I am pasting one screenshot below:
  
  As you can I have added two layers meta-networking (contains net-snmp) and
  meta-oe(contains fuse). After this I added these layers in
  *build/conf/bblayer.conf.*
  *
  *
  *
  
  *
  After this I again executed bitbake -k core-image-minimal command but I
  faced the same error as before... :(
  Is there anyway that these layers get recognized? Do I need to execute
  some other command?
 
 Obviously, this is a recipe that you made.
 
 Does it show these dependencies?  e.g. a line like this in your recipe file:
 DEPENDS = net-snmp fuse
 (or whatever the *packages* that you need are)
 
 Bitbake can't read your mind; it will only build the recipes you ask and the
 dependencies which are explicitly specified in that build chain.
 
 If you still have trouble, try sending your recipe (.bb file and all other
 components you might have), bblayers.conf, etc to the list because we're not
 mind readers either :-)
 
  On Tue, Jun 18, 2013 at 2:32 AM, Sudhangathan B S
  sudhangat...@gmail.commailto: 
  sudhangat...@gmail.com** wrote:
  Can you please paste your command and it's output here..! If you don't
  
  mind..!! Or explain with equivalent clarity. It
  
  l will good if you can also put in your directory structure.
  
  --**---
  Sudhangathan BS
  Ph:(+91) 9731-905-205
  --**---
  
  
  On Mon, Jun 17, 2013 at 11:33 PM, varun bhatnagar 
  
  varun292...@gmail.com mailto:varun292...@gmail.com** wrote:
  Actually the package which I am building is having some
  
  dependencies on some libraries. So I provided those libraries with the
  help of creating layers. I did not extract those from meta-openembedded,
  instead, I manually created two layers and added them in bblayer.conf file.

Rather than creating these layers from scratch (which I think is the most 
likely source of the problem) I'd suggest starting by cloning the original 
meta-openembedded repository and building your recipe with the meta-networking 
and meta-oe layers enabled in your bblayers.conf file.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: Yocto Layers not getting recognized by bitbake

[varun bhatnagar]

Thanks a ton for the reply Paul :)
But how to clone the meta-openembedded repository. I am not very clear on
the suggestion given by you.  :(
Can you please provide some steps on how to do this (cloning open-embedded
repository).

//
Varun


On Tue, Jun 25, 2013 at 4:16 PM, Paul Eggleton 
paul.eggle...@linux.intel.com wrote:

 On Sunday 23 June 2013 00:34:17 varun bhatnagar wrote:
  I am trying to compile my code using yocto. For that I have created two
  layers: meta-networking and meta-oe. I have added these dependencies
 in
  bblayer.conf too. But these are not getting build. Can anyone please tell
  me what should I do to make this work.
 
  //
  Varun
 
  --
  From: *Gary Thomas* g...@mlbassoc.com
  Date: Mon, Jun 17, 2013 at 11:03 PM
  To: yocto@yoctoproject.org
 
 
  More details are needed to be able to help.
 
  What do you mean not getting built?  Do you mean that if you
  try to build recipe XYZ which is in one of those layers that it's
  not being built?  Or perhaps you mean something else?
 
  What do you mean created two layers: ...?  Did you just extract
  these from meta-openembedded?  or something else?
 
   I am building one of my application using yocto by giving bitbake -k
   core-image-minimal command but I am facing some errors as this
 application
   requires two libraries
   *1) net-snmp*
   *2) fuse*
   *
  
   *
   I have one link where in they are asking to add these two libraries in
 the
   form of layers and then execute bitbake -k core-image-minimal command.
  
   I am pasting one screenshot below:
  
   As you can I have added two layers meta-networking (contains net-snmp)
 and
   meta-oe(contains fuse). After this I added these layers in
   *build/conf/bblayer.conf.*
   *
   *
   *
  
   *
   After this I again executed bitbake -k core-image-minimal command but I
   faced the same error as before... :(
   Is there anyway that these layers get recognized? Do I need to execute
   some other command?
 
  Obviously, this is a recipe that you made.
 
  Does it show these dependencies?  e.g. a line like this in your recipe
 file:
  DEPENDS = net-snmp fuse
  (or whatever the *packages* that you need are)
 
  Bitbake can't read your mind; it will only build the recipes you ask and
 the
  dependencies which are explicitly specified in that build chain.
 
  If you still have trouble, try sending your recipe (.bb file and all
 other
  components you might have), bblayers.conf, etc to the list because we're
 not
  mind readers either :-)
 
   On Tue, Jun 18, 2013 at 2:32 AM, Sudhangathan B S
   sudhangat...@gmail.commailto:
   sudhangat...@gmail.com** wrote:
   Can you please paste your command and it's output here..! If you
 don't
  
   mind..!! Or explain with equivalent clarity. It
  
   l will good if you can also put in your directory structure.
  
   --**---
   Sudhangathan BS
   Ph:(+91) 9731-905-205
   --**---
  
  
   On Mon, Jun 17, 2013 at 11:33 PM, varun bhatnagar 
  
   varun292...@gmail.com mailto:varun292...@gmail.com** wrote:
   Actually the package which I am building is having some
  
   dependencies on some libraries. So I provided those libraries with the
   help of creating layers. I did not extract those from
 meta-openembedded,
   instead, I manually created two layers and added them in bblayer.conf
 file.

 Rather than creating these layers from scratch (which I think is the most
 likely source of the problem) I'd suggest starting by cloning the original
 meta-openembedded repository and building your recipe with the
 meta-networking
 and meta-oe layers enabled in your bblayers.conf file.

 Cheers,
 Paul

 --

 Paul Eggleton
 Intel Open Source Technology Centre

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: Yocto Layers not getting recognized by bitbake

[Saul Wold]

On 06/25/2013 12:04 PM, varun bhatnagar wrote:

Thanks a ton for the reply Paul :)
But how to clone the meta-openembedded repository. I am not very clear
on the suggestion given by you.  :(
Can you please provide some steps on how to do this (cloning
open-embedded repository).


Paul is suggesting that you use the git tools to clone the repo.

you can get man pages for git, but the summary is:

git clone git://git.openembedded.org/meta-openembedded

in the poky directory, this will bring everything you need.

Sau!


//
Varun


On Tue, Jun 25, 2013 at 4:16 PM, Paul Eggleton
paul.eggle...@linux.intel.com mailto:paul.eggle...@linux.intel.com
wrote:

On Sunday 23 June 2013 00:34:17 varun bhatnagar wrote:
  I am trying to compile my code using yocto. For that I have
created two
  layers: meta-networking and meta-oe. I have added these
dependencies in
  bblayer.conf too. But these are not getting build. Can anyone
please tell
  me what should I do to make this work.
 
  //
  Varun
 
  --
  From: *Gary Thomas* g...@mlbassoc.com mailto:g...@mlbassoc.com
  Date: Mon, Jun 17, 2013 at 11:03 PM
  To: yocto@yoctoproject.org mailto:yocto@yoctoproject.org
 
 
  More details are needed to be able to help.
 
  What do you mean not getting built?  Do you mean that if you
  try to build recipe XYZ which is in one of those layers that it's
  not being built?  Or perhaps you mean something else?
 
  What do you mean created two layers: ...?  Did you just extract
  these from meta-openembedded?  or something else?
 
   I am building one of my application using yocto by giving
bitbake -k
   core-image-minimal command but I am facing some errors as this
application
   requires two libraries
   *1) net-snmp*
   *2) fuse*
   *
  
   *
   I have one link where in they are asking to add these two
libraries in the
   form of layers and then execute bitbake -k core-image-minimal
command.
  
   I am pasting one screenshot below:
  
   As you can I have added two layers meta-networking (contains
net-snmp) and
   meta-oe(contains fuse). After this I added these layers in
   *build/conf/bblayer.conf.*
   *
   *
   *
  
   *
   After this I again executed bitbake -k core-image-minimal
command but I
   faced the same error as before... :(
   Is there anyway that these layers get recognized? Do I need to
execute
   some other command?
 
  Obviously, this is a recipe that you made.
 
  Does it show these dependencies?  e.g. a line like this in your
recipe file:
  DEPENDS = net-snmp fuse
  (or whatever the *packages* that you need are)
 
  Bitbake can't read your mind; it will only build the recipes you
ask and the
  dependencies which are explicitly specified in that build chain.
 
  If you still have trouble, try sending your recipe (.bb file and
all other
  components you might have), bblayers.conf, etc to the list
because we're not
  mind readers either :-)
 
   On Tue, Jun 18, 2013 at 2:32 AM, Sudhangathan B S
   sudhangat...@gmail.com mailto:sudhangat...@gmail.commailto:
   sudhangat...@gmail.com mailto:sudhangat...@gmail.com** wrote:
   Can you please paste your command and it's output here..!
If you don't
  
   mind..!! Or explain with equivalent clarity. It
  
   l will good if you can also put in your directory structure.
  
   --**---
   Sudhangathan BS
   Ph:(+91) 9731-905-205
   --**---
  
  
   On Mon, Jun 17, 2013 at 11:33 PM, varun bhatnagar 
  
   varun292...@gmail.com mailto:varun292...@gmail.com
mailto:varun292...@gmail.com mailto:varun292...@gmail.com** wrote:
   Actually the package which I am building is having some
  
   dependencies on some libraries. So I provided those libraries
with the
   help of creating layers. I did not extract those from
meta-openembedded,
   instead, I manually created two layers and added them in
bblayer.conf file.

Rather than creating these layers from scratch (which I think is the
most
likely source of the problem) I'd suggest starting by cloning the
original
meta-openembedded repository and building your recipe with the
meta-networking
and meta-oe layers enabled in your bblayers.conf file.

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre




___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


___
yocto mailing list
yocto@yoctoproject.org

[yocto] Fwd: Yocto Layers not getting recognized by bitbake

[varun bhatnagar]

Hi,

Sorry I am sending this again but can anybody suggest something for this
problem please (please go through the mail chain below).

//
Varun

Forwarded conversation
Subject: Yocto Layers not getting recognized by bitbake


From: *varun bhatnagar* varun292...@gmail.com
Date: Mon, Jun 17, 2013 at 10:38 PM
To: yocto@yoctoproject.org yocto@yoctoproject.org


Hi,

I am trying to compile my code using yocto. For that I have created two
layers: meta-networking and meta-oe. I have added these dependencies in
bblayer.conf too. But these are not getting build. Can anyone please tell
me what should I do to make this work.

//
Varun

--
From: *Gary Thomas* g...@mlbassoc.com
Date: Mon, Jun 17, 2013 at 11:03 PM
To: yocto@yoctoproject.org


More details are needed to be able to help.

What do you mean not getting built?  Do you mean that if you
try to build recipe XYZ which is in one of those layers that it's
not being built?  Or perhaps you mean something else?

What do you mean created two layers: ...?  Did you just extract
these from meta-openembedded?  or something else?

-- 
--**--
Gary Thomas |  Consulting for the
MLB Associates  |Embedded world
--**--
__**_
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.**org/listinfo/yoctohttps://lists.yoctoproject.org/listinfo/yocto

--
From: *varun bhatnagar* varun292...@gmail.com
Date: Mon, Jun 17, 2013 at 11:33 PM
To: yocto@yoctoproject.org yocto@yoctoproject.org


Actually the package which I am building is having some dependencies on
some libraries. So I provided those libraries with the help of creating
layers. I did not extract those from meta-openembedded, instead, I manually
created two layers and added them in bblayer.conf file. Now, after
configuring all this stuff I am again trying to recompile my code but still
I am getting the same error saying that it is not able to find those
libraries provided by me in the form of layers.

--
From: *Sudhangathan B S* sudhangat...@gmail.com
Date: Tue, Jun 18, 2013 at 2:32 AM
To: varun bhatnagar varun292...@gmail.com
Cc: yocto@yoctoproject.org yocto@yoctoproject.org


Can you please paste your command and it's output here..! If you don't
mind..!! Or explain with equivalent clarity. It
l will good if you can also put in your directory structure.

-
Sudhangathan BS
Ph:(+91) 9731-905-205
-

--
From: *varun bhatnagar* varun292...@gmail.com
Date: Tue, Jun 18, 2013 at 9:58 PM
To: yocto@yoctoproject.org yocto@yoctoproject.org


I am building one of my application using yocto by giving bitbake -k
core-image-minimal command but I am facing some errors as this application
requires two libraries
*1) net-snmp*
*2) fuse*
*
*
I have one link where in they are asking to add these two libraries in the
form of layers and then execute bitbake -k core-image-minimal command.

I am pasting one screenshot below:

As you can I have added two layers meta-networking (contains net-snmp) and
meta-oe(contains fuse). After this I added these layers in *
build/conf/bblayer.conf.*
*
*
*
*
After this I again executed bitbake -k core-image-minimal command but I
faced the same error as before... :(
Is there anyway that these layers get recognized? Do I need to execute some
other command?


//
Varun

--
From: *Gary Thomas* g...@mlbassoc.com
Date: Tue, Jun 18, 2013 at 10:11 PM
To: yocto@yoctoproject.org


On 2013-06-18 17:28, varun bhatnagar wrote:

 I am building one of my application using yocto by giving bitbake -k
 core-image-minimal command but I am facing some errors as this application
 requires two libraries
 *1) net-snmp*
 *2) fuse*
 *

 *
 I have one link where in they are asking to add these two libraries in the
 form of layers and then execute bitbake -k core-image-minimal command.

 I am pasting one screenshot below:

 As you can I have added two layers meta-networking (contains net-snmp) and
 meta-oe(contains fuse). After this I added these layers in
 *build/conf/bblayer.conf.*
 *
 *
 *

 *
 After this I again executed bitbake -k core-image-minimal command but I
 faced the same error as before... :(
 Is there anyway that these layers get recognized? Do I need to execute
 some other command?


Obviously, this is a recipe that you made.

Does it show these dependencies?  e.g. a line like this in your recipe file:
  DEPENDS = net-snmp fuse
(or whatever the *packages* that you need are)

Bitbake can't read your mind; it will only build the recipes you ask and the
dependencies which are explicitly specified in that build chain.

If you still have trouble, try sending your recipe (.bb file and all other
components you might have), bblayers.conf, etc to the list because we're not
mind readers either :-)


 On Tue, Jun 18,