Hi all,
I'm compiling a test package "helloworld",then I just want to do the
standard tasks of "do_fetch","do_unpack" until the task "do_compile",and I do
not want to the next tasks like "do_build","do_package". I think there exist
the task dependency chain,but can hardly find how to remov
On Thursday 20 September 2012 15:41:54 Liu wrote:
> I'm compiling a test package "helloworld",then I just want to do the
> standard tasks of "do_fetch","do_unpack" until the task "do_compile",and I
> do not want to the next tasks like "do_build","do_package". I think there
> exist the task de
On 2012-09-20 05:38, Tom Zanussi wrote:
> On Wed, 2012-09-19 at 19:56 -0400, Bruce Ashfield wrote:
>> On 12-09-19 04:54 PM, Mihai Lindner wrote:
>>> On 2012-09-19 23:32, Bruce Ashfield wrote:
On 12-09-19 04:22 PM, Bruce Ashfield wrote:
> On 12-09-19 03:39 PM, Mihai Lindner wrote:
>> On
On Thursday 20 September 2012 17:59:56 Liu wrote:
> That's not what i mean.I want to remove the tasks like
> "do_build","do_package" from the default tasks list,and reserve the tasks
> (do_fetch,do_unpack,do_compile) I need. I know there exist some dependency
> between tasks and then generate a def
2012/9/19 :
> From: Kishore Bodke
>
> Hi,
>
> This patch set adds three different types of Corpus files
> to Crystal Forest BSP, which are basically used to test the
> Lossless Compression algorithms.
>
> 1. calgary-corpus
> 2. canterbury-corpus
> 3. silesia-corpus
>
> These have been tested on b
I'm writing a recipe to checkout files from local svn. Here is my URI:
SRC_URI =
"svn://svn.ad-group.adh/svn/dev_repos/Generation3_app;module=trunk;protocol=http"
bitbake fails to fetch the source from this location and gives the bellow
error message.
Looks like bitbake is not replacing svn with
Dear Paul,
I have some packages built by a set of Makefiles,and want to build them
using bitbake.So I used recipes to invoke Makefiles to do
fetch,unpack,patch,compile tasks.But I do not need to do the following tasks
like do_build,do_package.
In the default conditions,there exist list of
> Try doing 'bitbake kmod -c cleansstate;bitbake kmod' - does that still fail?
Thanks for the suggestion. I get this when I try to run 'bitbake kmod -c
cleanslate':
ERROR: Task do_cleanslate does not exist for target kmod
Because I don't know any better, I tried this instead:
% bitbake km
On Thursday 20 September 2012 21:11:49 Liu wrote:
> I have some packages built by a set of Makefiles,and want to build them
> using bitbake.So I used recipes to invoke Makefiles to do
> fetch,unpack,patch,compile tasks.But I do not need to do the following
> tasks like do_build,do_package.
> I
On 2012-09-20 07:30, Evade Flow wrote:
Try doing 'bitbake kmod -c cleansstate;bitbake kmod' - does that still fail?
Thanks for the suggestion. I get this when I try to run 'bitbake kmod -c
cleanslate':
ERROR: Task do_cleanslate does not exist for target kmod
typo: it needs to be 'cleanss
From: Timo Mueller
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
---
.../dev-manual
From: Timo Mueller
This target will generate eclipse help for the dev-manual using
the dev-manual-eclipse-customization.xsl stylesheet.
The output will be generated to a separate directory which can be used
for integrating the documentation into eclipse.
---
documentation/Makefile | 10 ++
From: Timo Mueller
---
documentation/Makefile |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/documentation/Makefile b/documentation/Makefile
index 0537c22..005d670 100644
--- a/documentation/Makefile
+++ b/documentation/Makefile
@@ -295,13 +295,13 @@ ifneq ($(DOC
From: Timo Mueller
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
---
documentation/Makefile |6 +-
.../dev-manual/dev-manual-customizati
From: Timo Mueller
Hi,
I've recently submitted a proof of concept showing how eclipse help files
can be generated from the adt-manual using the docbook eclipse3.xsl
stylesheet. These patches are currently in the temporary branch 'timo'
in the yocto-docs git.
This patch series fixes a small bug
From: Timo Mueller
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
---
.../bsp-guide/
From: Timo Mueller
The title of the document used to create metadata for output formats
such as eclipse help.
---
documentation/dev-manual/dev-manual.xml |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/documentation/dev-manual/dev-manual.xml
b/documentation/dev-manua
From: Timo Mueller
Eclipse help documents are now created when calling the 'make all'
target on the dev-manual. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
---
documentation/Makefile | 13 ---
From: Timo Mueller
This target will generate eclipse help for the bsp-guide using
the bsp-guide-eclipse-customization.xsl stylesheet.
The output will be generated to a separate directory which can be used
for integrating the documentation into eclipse.
---
documentation/Makefile |4 +++-
1
From: Timo Mueller
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
---
documentation/Makefile |6 +-
.../bsp-guide/bsp-guide-customization
From: Timo Mueller
Eclipse help documents are now created when calling the 'make all'
target on the bsp-guide. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
---
documentation/Makefile |7 ---
1 f
From: Timo Mueller
The title of the document used to create metadata for output formats
such as eclipse help.
---
documentation/bsp-guide/bsp-guide.xml |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/documentation/bsp-guide/bsp-guide.xml
b/documentation/bsp-guide/bsp
From: Timo Mueller
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
---
documentation/Makefile |7 +--
.../kernel-manual/kernel-manual-cust
From: Timo Mueller
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
---
.../kernel-man
From: Timo Mueller
This target will generate eclipse help for the kernel-manual using
the kernel-manual-eclipse-customization.xsl stylesheet.
The output will be generated to a separate directory which can be used
for integrating the documentation into eclipse.
---
documentation/Makefile |4
From: Timo Mueller
The title of the document used to create metadata for output formats
such as eclipse help.
---
documentation/kernel-manual/kernel-manual.xml |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/documentation/kernel-manual/kernel-manual.xml
b/documentati
From: Timo Mueller
Eclipse help documents are now created when calling the 'make all'
target on the kernel-manual. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
---
documentation/Makefile |8 +---
From: Timo Mueller
Eclipse help documents are now created when calling the 'make all'
target on the poky-ref-manual. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
---
documentation/Makefile |6 +++---
From: Timo Mueller
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
---
.../poky-ref-m
From: Timo Mueller
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
---
documentation/Makefile |7 +--
.../poky-ref-manual-customization.xs
From: Timo Mueller
Eclipse help documents are now created when calling the 'make all'
target on the yocto-project-qs. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
---
documentation/Makefile |9 +
From: Timo Mueller
The title of the document used to create metadata for output formats
such as eclipse help.
---
documentation/poky-ref-manual/poky-ref-manual.xml |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/documentation/poky-ref-manual/poky-ref-manual.xml
b/doc
From: Timo Mueller
This target will generate eclipse help for the poky-ref-manual using
the poky-ref-manual-eclipse-customization.xsl stylesheet.
The output will be generated to a separate directory which can be used
for integrating the documentation into eclipse.
---
documentation/Makefile |
From: Timo Mueller
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
---
documentation/Makefile |3 +--
.../yocto-project-qs-customization.xsl
From: Timo Mueller
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
---
.../yocto-proj
From: Timo Mueller
This target will generate eclipse help for the yocto-project-qs using
the yocto-project-qs-eclipse-customization.xsl stylesheet.
The output will be generated to a separate directory which can be used
for integrating the documentation into eclipse.
---
documentation/Makefile |
On Thursday 20 September 2012 09:30:19 Evade Flow wrote:
> I guess I'll try the BFI approach of restarting the build from scratch next.
> `:-o.
We'd really rather people didn't do this as it does not help us to diagnose
and fix problems.
> Incidentally, searching the OpenEmbedded manual for 'c
Dear Paul,
I know it probably not be right to do in such way.But my project is built
by buildroot,So I just need to run make to build the image.And now
I want to use bitbake to build the project instead of buildroot.Then I think
of the idea to use recipes to "do_fetch","do_unpack",and "oe
On Thursday 20 September 2012 21:50:42 Liu wrote:
> I know it probably not be right to do in such way.But my project is
> built by buildroot,So I just need to run make to build the image.And now
> I want to use bitbake to build the project instead of buildroot.Then I
> think of the idea to us
Dear Paul,
Thanks a lot for your suggestion.Maybe in the future I will change the
original Buildroot makefiles in my project to make the build easy and code
convenient management.
---Liu
-- Original --
From: "Paul Eggleton";
Date: Thu, Se
Fortunately, you caught me before I pulled out a bigger hammer. :-} I was
going to report that this still didn't work after typing:
% bitbake -c cleanstate
But re-reading your post, I saw that there were supposed to be two 'esses'[!]
The following:
% bitbake kmod -c cleansstate
% bitbake k
On Thu, Sep 20, 2012 at 8:26 AM, Tarek El-Sherbiny <
tarek.elsherb...@gmail.com> wrote:
> I'm writing a recipe to checkout files from local svn. Here is my URI:
>
> SRC_URI =
> "svn://svn.ad-group.adh/svn/dev_repos/Generation3_app;module=trunk;protocol=http"
>
Are you trying to fetch from the tip
Yes, I'm trying to fetch from tip. and yes I've got all the parameters
you mentioned.
The strange thing, bitbake is recognizing the Last Changed Rev: 78205 but
not doing the actual checkout!
NOTE: package web-browser-1.0+svnr*78205*-r6: task do_fetch: Started
WARNING: Failed to fetch URL
svn://svn
I would like to NOT put the source code within the ${PN}-dbg pkg and
keep it separate from my symbol binaries in that pkg. Is there a way to
either turn off the collection of the source or allow me to put it in a
different pkg. It could be useful to have some cases but not in all.
I have been us
> I would like to NOT put the source code within the ${PN}-dbg pkg and
> keep it separate from my symbol binaries in that pkg. Is there a way to
> either turn off the collection of the source or allow me to put it in a
> different pkg. It could be useful to have some cases but not in all.
I just
>-Original Message-
>From: Przemysław Czesnowicz [mailto:czesiek...@gmail.com]
>Sent: Thursday, September 20, 2012 3:58 AM
>To: Bodke, Kishore K
>Cc: Zanussi, Tom; Kamble, Nitin A; yocto@yoctoproject.org; Samson, Don;
>Czesnowicz, PrzemyslawX
>Subject: Re: [yocto] [PATCH 0/3][meta-intel]
-Original Message-
From: Zanussi, Tom
Sent: Wednesday, September 19, 2012 7:38 PM
To: Bruce Ashfield
Cc: Mihai Lindner; Development list for the linux-yocto*.git Linux kernel
repositories; yocto@yoctoproject.org; Darren Hart; Bodke, Kishore K; Saxena,
Rahul
Subject: Re: [linux-yocto] [
>-Original Message-
>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Bodke, Kishore K
>Sent: Thursday, September 20, 2012 9:21 AM
>To: Przemyslaw Czesnowicz
>Cc: Samson, Don; Czesnowicz, PrzemyslawX; yocto@yoctoproject.org
>Subject: Re: [yocto]
Hi,
I am running Yocto 1.2 and would like to include the boost development
environment in my SDK. I created a bbappend for the boost recipe that
only contains two lines:
PR = "${INC_PR}.1"
BBCLASSEXTEND += "nativesdk"
When I build with the above I get the following warnings:
NOTE: multiple provi
2012/9/20 Bodke, Kishore K :
>
>
>>-Original Message-
>>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>>boun...@yoctoproject.org] On Behalf Of Bodke, Kishore K
>>Sent: Thursday, September 20, 2012 9:21 AM
>>To: Przemyslaw Czesnowicz
>>Cc: Samson, Don; Czesnowicz, PrzemyslawX; yocto@yo
To bring this full circle... if you want to build behind a restrictive
firewall using pre-mirrored sources and BB_NO_NETWORK, be aware that
recipes which:
1. Specify a git repo as the source, and,
2. Specify the revision to be built using a tag name
will cause your build to abort when bitba
On 09/20/2012 04:08 PM, Evade Flow wrote:
To bring this full circle... if you want to build behind a restrictive
firewall using pre-mirrored sources and BB_NO_NETWORK, be aware that
recipes which:
1. Specify a git repo as the source, and,
2. Specify the revision to be built using a tag na
On 09/20/2012 11:50 AM, Chatre, Reinette wrote:
> Hi,
>
> I am running Yocto 1.2 and would like to include the boost development
> environment in my SDK. I created a bbappend for the boost recipe that
> only contains two lines:
>
> PR = "${INC_PR}.1"
> BBCLASSEXTEND += "nativesdk"
>
> When I bui
On Sun, 2012-09-16 at 15:27 -0700, nitin.a.kam...@intel.com wrote:
> From: Nitin A Kamble
>
> emgd-driver-bin is generating rpm package with name libegl1.
> This name clashes with a package with sanme name from mesa-dri
> recipe. This name clash blocks installation of emgd user land
> binaries in
On Thursday 20 September 2012 16:08:41 Evade Flow wrote:
> To bring this full circle... if you want to build behind a restrictive
> firewall using pre-mirrored sources and BB_NO_NETWORK, be aware that
> recipes which:
>
> 1. Specify a git repo as the source, and,
>
> 2. Specify the revision t
On Thu, Sep 20, 2012 at 2:32 PM, Darren Hart wrote:
> On 09/20/2012 11:50 AM, Chatre, Reinette wrote:
>> Hi,
>>
>> I am running Yocto 1.2 and would like to include the boost development
>> environment in my SDK. I created a bbappend for the boost recipe that
Do you want your target applications t
> You should not need to be specifying the revision within SRC_URI as you are
> doing, however, it is correct that you must specify the revision in
> SRCREV...
This doesn't appear to be done in a couple of the Yocto recipes:
- meta/recipes-devtools/btrfs-tools/btrfs-tools_git.bb
- meta/recipe
On Thu, Sep 20, 2012 at 3:12 PM, Evade Flow wrote:
> This doesn't appear to be done in a couple of the Yocto recipes:
>
> - meta/recipes-devtools/btrfs-tools/btrfs-tools_git.bb
> - meta/recipes-devtools/mtd/mtd-utils_1.4.9.bb
>
good. Send patches we will accept.
> SRCREV is not set in either
Simple: tags aren't guaranteed to not change what it references, the
hash is guaranteed to always point to the same thing. Thus, git is
double checking that the meaning of the tag hasn't changed.
On Thu, 2012-09-20 at 16:32 -0400, William Mills wrote:
> On 09/20/2012 04:08 PM, Evade Flow wrote:
Hi Khem,
On Thu, 2012-09-20 at 14:49 -0700, Khem Raj wrote:
> On Thu, Sep 20, 2012 at 2:32 PM, Darren Hart wrote:
> > On 09/20/2012 11:50 AM, Chatre, Reinette wrote:
> >> Hi,
> >>
> >> I am running Yocto 1.2 and would like to include the boost development
> >> environment in my SDK. I created a b
60 matches
Mail list logo
