don't you? If
it's expanded it will take up 4GB minus the boot partition size so you're into
a large dd again...
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Wednesday 05 September 2012 22:57:22 Jack Mitchell wrote:
> On 05/09/2012 22:46, Paul Eggleton wrote:
> > On Wednesday 05 September 2012 12:16:44 Gary Thomas wrote:
> >> Also, is it possible to just build the SD image much like I do for
> >> other devices like t
confuse the reader.
Looks like this still needs to be addressed. Scott, would you mind taking a
look at this? Seems to me that BB_ENV_WHITELIST just ought to be changed to
BB_ENV_EXTRAWHITE to make this make sense.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
__
t files output by "bitbake -g busybox". They are
usually too large to visualise using graphviz but they are plain text so you
can just view/search them directly.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
; $ cd /tool/yocto/poky;source oe-init-build-env build
> $ bitbake icecc-create-env-native
>
> The icecc-create-env script will automatically be copied to the build output
> staging folder.
>
> Step 02.02: Start a bit bake build.
>
> $ bitbake core-image-minimal
>
Elvis, did you have any further luck with this?
Otherwise, Dmitry, any suggestions? I'm assuming you made use of icecc.bbclass
since you made some changes to it a while ago...
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
> Who can tell me the cause and how to solve the question?
Not sure if I already noted this, but I reproduced the issue here and filed bug
2933 since it affects anything that uses the BBCLASSEXTENDS mechanism:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2933
Cheers,
Paul
--
Signed-off-by: Paul Eggleton
---
meta-tlk/README | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/meta-tlk/README b/meta-tlk/README
index 5ff4d3b..07cbd76 100644
--- a/meta-tlk/README
+++ b/meta-tlk/README
@@ -1,6 +1,9 @@
-meta-autobuilder
-===
+meta
ble-auth-pam \
> + --build=${BUILD_SYS} \
> + --host=${HOST_SYS} \
> + --target=${TARGET_SYS} \
> + --prefix=/usr \
> +--sysconfdir=/etc \
> +--sharedstatedir=/com \
> +
d these already. FYI there is a short reference to the
available options for the new OE_TERMINAL in the example config file which
you should be able to copy and adapt:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/local.conf.sample
Please let me know if you need any more info.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
recipes.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Thursday 06 September 2012 09:33:26 Gary Thomas wrote:
> On 2012-09-06 09:29, Paul Eggleton wrote:
> > On Thursday 06 September 2012 19:23:53 Elvis Dowson wrote:
> >> Unfortunately no. I've got two machines, both with quad-core intel i7
> >> processors, but I
On Wednesday 12 September 2012 00:40:36 Khem Raj wrote:
> NAK
Please do not reply to patches like this. If you object to a patch you need to
provide some reasoning.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mail
to the connman developers and their position is that you shouldn't
use connman at all with nfsroot, so the solution [1] was not to start
connmand if nfsroot is detected.
Cheers,
Paul
[1]
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=c6fda196cbbfd749b8bf10ad97dc373217d8ed2e
--
-C
That's correct. This has been implemented in master (and will be in the
upcoming stable release).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
r some further
details.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
it's new functionality, requires
support in the metadata to work, and led to several further cleanup patches
for the metadata to avoid warnings being raised.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
A few points:
1) Re contrib.patch - surely it would be valid to pass DESTDIR through for
everyone? If so we should be able to consider sending this patch upstream, in
which case Upstream-Status should be Pending.
2) When LIC_FILES_CHKSUM changes for any reason we need to mention clearly w
On Thursday 13 September 2012 16:37:59 Saxena, Rahul wrote:
> Ross, the definition of RPROVIDES is not given in the Yocto project
> reference manual. Perhaps it should be added to the manual ?
Good catch - yes, it should. Scott R - I can send you some info.
Cheers,
Paul
--
Paul Eggleton
strassek/baryon-updates
>
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=strassek/baryon-up
> dates
Merged to meta-baryon master, thanks.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing l
ctionality without
breaking existing machine configurations by disabling the existing
functionality because the configuration doesn't include it. (In older versions
of busybox the hwclock feature was on by default - an hwclock item was added
at the MACHINE_FEATURES level to be able to control it).
To fix this, just add hwclock to MACHINE_FEATURES_BACKFILL_CONSIDERED in your
machine configuration.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Monday 17 September 2012 09:37:13 Raul Rosetto Munoz wrote:
> I know that habe a bitbake command that list all packages.
Do you mean list all recipes? If so, one of the following may be helpful:
bitbake -s
bitbake-layers show-recipes
Cheers,
Paul
--
Paul Eggleton
Intel Open Sou
d.org/patch/36547/
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
quot;do_build","do_package". I think there
> exist the task dependency chain,but can hardly find how to remove the tasks
> I do not want to do.Can anyone tell me something detailed about this
> question ?
If you mean for a single execution, just run "bitbake -c co
fter do_build? There should not be any, at least
not for the same target.
There are several ways of disabling tasks - the first that comes to mind is to
mark the task as noexec, for example:
do_package[noexec] = "1"
My question would be though, what are you trying to achieve by doing t
are stepping outside of the bounds of what is normally
supported with the metadata we provide (although it is not outside of
supported BitBake behaviour).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
- but the good news is there is an up-to-
date and comprehensive set of documentation set provided by the Yocto Project
here:
http://www.yoctoproject.org/documentation
FYI you can do "bitbake -c listtasks " which will list all of the
valid tasks, you can remove do_ from the start of th
where you will end up with your current approach but it sounds like
you won't get much benefit by just calling into the original Buildroot
makefiles
over just continuing to use Buildroot on its own.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
SRC_URI as you are
doing, however, it is correct that you must specify the revision in SRCREV and
that revision must be the full SHA1 hash and not just a tag or branch name.
The reason for this is that tags are not fixed and could change, therefore if
one is used we must query the server
en using 6.3 here on my build machine for some time with no ill effects.
I believe we have some interest in preserving 5.x; should we be adding 6.3 and
removing 6.2? What about the rest?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
_
On Monday 24 September 2012 12:29:07 Trevor Woerner wrote:
> On Mon, Sep 24, 2012 at 7:10 AM, Paul Eggleton
>
> wrote:
> > openSUSE 11.4 \n \
> > openSUSE 12.1 \n \
>
> openSUSE 12.2 was released on September 5th. I have been using it
>
eaudio being in DISTRO_FEATURES after
I added that feature. I think we should still do that, not sure if it's too
late for the current development cycle though - at least it's not too
intrusive since pulseaudio is a backfilled feature.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
need to follow the instructions and
make the appropriate changes to your conf/bblayers.conf. However, there is a
patch out for review that we would like to include for the 1.3 final release
which will take care of this automatically for you.
Cheers,
Paul
--
Paul Eggleton
In
is not as helpful as it could be, hence why we are working
to do this automatically for the user.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
gt;
> > I appreciate this is not as helpful as it could be, hence why we are
> > working to do this automatically for the user.
>
> Ah, OK. Well, I decided to update meta/conf/sanity.conf to have a
> matching value of LAYER_CONF_VERSION, so this is solved.
That will wor
On Wednesday 26 September 2012 16:20:45 Wolfgang Denk wrote:
> Dear Paul Eggleton,
> In message <2428256.OTjtN2nWn5@helios> you wrote:
> > > Ah, OK. Well, I decided to update meta/conf/sanity.conf to have a
> > > matching value of LAYER_CONF_VERSION, so this is s
verify it built by just checking under tmp/sysroots//usr/bin/ to see if tar exists there.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
changed, 8 insertions(+), 5 deletions(-)
Merged to meta-baryon master, thanks.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
test() {
echo | awk 'END { exit ( !( '"$1"')); }'
}
# Tar version 1.24 and onwards handle overwriting symlinks correctly
# but earlier versions do not; this needs to work properly for sstate
float_test "$TARVERSION > 1.23" && needtar="0&q
t; executed. (Is it really supposed to?)
No, but the rest of the script (the bit following the blank line that you've
omitted) is... I wanted to ensure that both the stripping out of the version
and float_test were working.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Cent
tar: Error is not
> recoverable: exiting now
>
>
> Weird. Anyway, I have a workaround, so it's not a big deal--especially given
> that Ubuntu 10.04 isn't officially supported. I'm happy to run any other
> tests you can think of to hunt down the cause of this
an interesting point of history, I'm not sure
anyone really needs to know this in the manual, particularly if we've replaced
all historical use of the word "package" when we mean "recipe" (as I think we
now have for this release).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
cost - it would certainly cause a massive amount of churn, with
the potential for problems with layer interaction where one layer has done the
big rename and another that bbappends recipes in the first hasn't.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology C
.2.3.bbappend new file mode
> 100644
> index 000..2c91a93
> --- /dev/null
> +++ b/recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bbappend
> @@ -0,0 +1,8 @@
> +PR = "r5"
This needs to be:
PRINC = "1"
or, to ensure other layers can also increm
ported upstream for some time now.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Monday 01 October 2012 14:21:47 McClintock Matthew-B29882 wrote:
> On Mon, Oct 1, 2012 at 3:00 AM, Paul Eggleton
>
> wrote:
> > On Monday 24 September 2012 19:03:57 McClintock Matthew-B29882 wrote:
> >> CentOS release 5.8 (Final)
> >
> > OK, so do we kee
://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/doc-fixes-4
Paul Eggleton (11):
documentation/poky-ref-manual: the G in GPL is "General"
documentation/poky-ref-manual: add staticdev-pkgs
documentation/poky-ref-manual: add SDKIMAGE_FEATURES
documentation/poky-ref-manual: minor im
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-images.xml |4 ++--
documentation/poky-ref-manual/usingpoky.xml |6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/documentation/poky-ref-manual/ref-images.xml
b/documentation/poky-ref-manual/ref
Add new SDKIMAGE_FEATURES to variable reference.
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-variables.xml | 10 ++
1 file changed, 10 insertions(+)
diff --git a/documentation/poky-ref-manual/ref-variables.xml
b/documentation/poky-ref-manual/ref-variables.xml
Document the new staticdev-pkgs IMAGE_FEATURES item.
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-features.xml |2 ++
1 file changed, 2 insertions(+)
diff --git a/documentation/poky-ref-manual/ref-features.xml
b/documentation/poky-ref-manual/ref-features.xml
index
Adjust a few sentences so that they make sense.
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-variables.xml | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/documentation/poky-ref-manual/ref-variables.xml
b/documentation/poky-ref
We haven't supported Ubuntu Intrepid (8.04) for some time now.
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/faq.xml | 22 --
1 file changed, 22 deletions(-)
diff --git a/documentation/poky-ref-manual/faq.xml
b/documentation/poky-ref-manual/faq.xml
Update references to the netbase recipe to the current version (5.0).
Signed-off-by: Paul Eggleton
---
documentation/bsp-guide/bsp.xml |2 +-
documentation/poky-ref-manual/faq.xml |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/bsp-guide/bsp.xml
Setting PR = "r0" isn't mandatory, but is recommended. Also, there isn't
really any restriction on its format.
Signed-off-by: Paul Eggleton
---
.../dev-manual/dev-manual-common-tasks.xml |7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git
Since we are using a layer-based approach, people do not need to rely
upon us to add support for new boards.
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/faq.xml | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/documentation/poky-ref-manual
r the definition of OE-Core.
Signed-off-by: Paul Eggleton
---
documentation/dev-manual/dev-manual-newbie.xml |2 +-
documentation/poky-ref-manual/faq.xml | 14 --
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/documentation/dev-manual/dev-manual-newbie.x
Adjust language slightly so that it reads correctly, and avoid
conflating the terms OpenEmbedded and Poky.
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/faq.xml |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/documentation/poky-ref-manual/faq.xml
Ensure that this section correctly and accurately describes how Poky and
OE relate to eachother currently.
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/faq.xml | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/documentation/poky-ref-manual
t;> > I ran into the same issue a few days ago. It seems yocto only supports
> >> > git fetch through servers providing the repositories through the git
> >> > protocol. A way to use git repositories which are provided through
> >> > http or https would be quite a goo
l.cfg"
You should use SRC_URI_append = " file://time-limited-kernel.cfg" (note leading
space) here. Obviously what you have done does work, but we want to avoid
_append += as it can be confusing.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology
there will be only one layer at
some point?
Cheers,
Paul
[4] http://www.openembedded.org/wiki/LayerIndex
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
903aeef57c85314f5083:
documentation: dev-manual - mentioned SRC_URI in the kernel example
(2012-10-05 11:25:03 -0700)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/doc-fixes-5
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/doc-fixes-
sence -> sense
Signed-off-by: Paul Eggleton
---
documentation/dev-manual/dev-manual-newbie.xml |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/dev-manual/dev-manual-newbie.xml
b/documentation/dev-manual/dev-manual-newbie.xml
index 9b922b1..20cf234 100
usage scenarios for these variables.
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-variables.xml | 124 +++
1 file changed, 60 insertions(+), 64 deletions(-)
diff --git a/documentation/poky-ref-manual/ref-variables.xml
b/documentation/poky-ref-manua
LICENSE_PATH is the correct variable to use for 1.3 - see:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=3118
Fixes documentation for [YOCTO #3118].
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-variables.xml |6 +++---
1 file changed, 3 insertions(+), 3 deletions
Add a description of the PACKAGECONFIG variable to the variable
glossary.
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-variables.xml | 31 +++
1 file changed, 31 insertions(+)
diff --git a/documentation/poky-ref-manual/ref-variables.xml
b
Extend the description of the DISTRO variable so that it mentions that
this points to a .conf file under conf/distro and mentions what happens
if the value is left blank.
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-variables.xml | 11 ++-
1 file changed, 10
Extend the description of the MACHINE variable so that it mentions that
this points to a .conf file under conf/machine.
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-variables.xml |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/documentation/poky
-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-features.xml | 46 +++
documentation/poky-ref-manual/ref-variables.xml | 54 ++-
2 files changed, 99 insertions(+), 1 deletion(-)
diff --git a/documentation/poky-ref-manual/ref-features.xml
b
* Use correct/up-to-date names of package systems
* SUMMARY does not default to the value of DESCRIPTION, it's the other
way around (although the logic may be improved in future so that this
is the effect).
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-variable
We haven't supported ipkg for some time now - it was replaced by opkg
(whilst still using the ipk package format).
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/faq.xml |2 +-
documentation/poky-ref-manual/ref-variables.xml |4 ++--
2 files chang
* Add meta-yocto, meta-yocto-bsp and meta-hob
* Remove meta-rt - this was merged into OE-Core (meta)
* Remove meta-demoapps - this was dropped
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-structure.xml | 30 ---
1 file changed, 21 insertions(+), 9
We have to take care when using "package" to avoid confusion, even when
referring to variables with a historical package association (PV, PN
etc.).
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-variables.xml | 25 ---
1 file changed, 13
On Monday 08 October 2012 16:38:06 Paul Eggleton wrote:
> Add some missing variables to the variable reference and improve
> the descriptions of others. Also fix references to "package" where
> we mean "recipe" and a couple of other issues I noticed at the same
s
one was missed out. Fortunately though the new version of the Quick Start
Guide for 1.3 in which that section has been rewritten does however include
chrpath in the list of packages for CentOS.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
sting buildhistory-diff command line
utility) may benefit from some further work also. I'm by no means a web
development expert either so if you have any suggestions or patches in that
regard I'd be happy for those as well.
Cheers,
Paul
[1] http://wiki.yoctoproject.org/wiki/Buildhis
gt; This needs to be:
> >
> > PRINC = "1"
> >
> > or, to ensure other layers can also increment the value:
> >
> > PRINC := "${@int(PRINC) + 1}"
>
> OK, that makes sense. I've made the changes and pushed them again to:
>
> git://g
Significant cleanup of X server recipes
- Start to add regression tests for BitBake
Is there anything that belongs here that I have missed? I know we've done a
lot of other bugfixes and package upgrades, we're really after the
highlights.
Cheers,
Paul
--
Paul Eggleton
Signed-off-by: Paul Eggleton
---
common/recipes-multimedia/ffmpeg/ffmpeg.inc |2 ++
1 file changed, 2 insertions(+)
diff --git a/common/recipes-multimedia/ffmpeg/ffmpeg.inc
b/common/recipes-multimedia/ffmpeg/ffmpeg.inc
index 96da7c2..3ce950e 100644
--- a/common/recipes-multimedia/ffmpeg
current commits SHA1 into the file /etc/build. This will
> > give me all info I need.
>
> FYI, I was able to put the SHA1 of each meta data layer by doing:
>
> def print_layers_version(d):
> layertext = "Configured metadata layers:\n%s\n" %
> '\n'.jo
based on PE if PE is set and greater than zero for the recipe, or
else will be empty. e.g. if PE is "1" then EXTENDPE will be "1_", whereas if
PE is not set (the default) or 0 then EXTENDPE will be "".
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Techn
e have opened a bug to
track it - you may wish to add yourself to the CC list:
http://bugzilla.yoctoproject.org/show_bug.cgi?id=3263
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@
recipe from OE-Classic here:
http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core
If you do come up with an updated recipe we'd love to have it added to meta-oe
or some other layer ;)
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
owever, what I hope we can do in the 1.4 timeframe would be to implement my
proposal here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=3272
This would provide us with a way to search all published layers down to the
recipe level from the web.
Cheers,
Paul
--
Paul Eggl
cal to define the dependency chains in the documentation, but
> providing the user with the background and tools to discover them seems
> appropriate.
>
>
> Scott Rifenbark
> Intel Corporation
> Yocto Project Documentation
> 503.712.2702
> 503.341.0418 (cell)
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Wednesday 17 October 2012 21:07:20 Rifenbark, Scott M wrote:
> Thanks for the added investigation here. The original bug report listed
> COMMON_FEATURES as an undocumented variable. I see, however, that the
> variable referred to by both you and Paul Eggleton is COMBINED_FEATURES.
t;
> >>
> >> The module gets built correctly and is included in the images. Running
> >> 'modprobe foo' works as intended on the target hardware.
> >>
> >> Did I fall in some edge case?
> >
> > Does foo have any '-' or &
g the combo-layer tool to pull them back down when they are
merged.
Long term however I'd rather see the additional unique recipes in meta-
guacamayo itself go into more official OE community layers. meta-dlna would
continue to take them from there using combo-layer though I suspect. (This is
t
On Monday 22 October 2012 09:06:41 Tomas Frydrych wrote:
> On 20/10/12 13:16, Paul Eggleton wrote:
> > On Friday 19 October 2012 11:01:09 Saul Wold wrote:
> > Long term however I'd rather see the additional unique recipes in meta-
> > guacamayo itself go into more of
newer version of git needs to be built (if the host's version of git is
older than 1.7.5); if so we build one (git-replacement-native). The denzil /
1.2 release does not have this, however.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
://git.yoctoproject.org/poky-contrib paule/proftpd
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/proftpd
Paul Eggleton (1):
proftpd: add initscript and tidy up recipe
recipes-extended/proftpd/files/basic.conf.patch |2 +-
recipes-extended/proftpd/files/contrib.patch |4
which sets DESCRIPTION) and base it on the short
description from the website
* Add HOMEPAGE
* Add/fix description in some patches and improve recipe indentation
* Remove unnecessary chown of proftpd binary in postinst script
Signed-off-by: Paul Eggleton
---
recipes-extended/proftpd/files/basic.conf.patc
gt; > do not want to extract the full repo for each modules either.
> >
> > I am now looking into writing my own unpack function to move my code
> > under S manually, but I was wondering if yocto had something to support
> > this model and I simply missed it or if wri
amples but at the moment there is
no actual reference for them (which we should have).
> and i already mentioned that [recideptask] was missing from that list.
> are there any others?
It's not unlikely that there are others, yes.
itbake-layers show-appends
If it's not listed there, check that the layer shows up in:
bitbake-layers show-layers
If the layer doesn't show there, check if it has been correctly added to
bblayers.conf. If it is, check that your layer.conf is setting BBFILES such
that bbappends in th
ibed in our kernel development manual:
http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#working-with-your-own-sources
Note that you must not have SRCPV included in the recipe's value of PV, or
you will get the error you mentioned.
Cheers,
Paul
--
Paul Eggleton
Intel
;
> do_patch_class-target[noexec] = "1"
> do_compile_class-target[noexec] = "1"
>
> It appears the OVERRIDES do not apply here, any hint on how I can achieve
> this?
Probably the easiest way would be to just null out the tasks just for the
tar
expert there).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
ures will incorporate the values of all of the things
your bbappend is setting, so this doesn't really account for the behaviour you
are describing. Can you reproduce the issue?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
o didn't see the echo output on the console when the package is being
> installed or post installation activity is being performed.
Is the output package that you are installing actually called "test"?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
packagegroup recipe within
your custom layer to pull in all the packages you want installed, and then you
just need to add that packagegroup to your image.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
701 - 800 of 1699 matches
Mail list logo
