[yocto] [meta-selinux][PATCH] attr: fix ptest failures when selinux enabled
From: Kai Kang
When selinux is enabled, a file has a default attribute
"security.selinux" and the output of getfattr shows:
# file: here
security.selinux="system_u:object_r:lib_t:s0"
That always causes more output of command getfattr than expected.
Filter out selinux related attribute info, and if the file has only
selinux attribute info, remove its whole output.
Signed-off-by: Kai Kang
---
.../fix-ptest-failures-when-selinux-enabled.patch | 41 ++
recipes-support/attr/attr_%.bbappend | 5 +++
2 files changed, 46 insertions(+)
create mode 100644
recipes-support/attr/attr/fix-ptest-failures-when-selinux-enabled.patch
create mode 100644 recipes-support/attr/attr_%.bbappend
diff --git
a/recipes-support/attr/attr/fix-ptest-failures-when-selinux-enabled.patch
b/recipes-support/attr/attr/fix-ptest-failures-when-selinux-enabled.patch
new file mode 100644
index 000..e1eefa7
--- /dev/null
+++ b/recipes-support/attr/attr/fix-ptest-failures-when-selinux-enabled.patch
@@ -0,0 +1,41 @@
+Upstream-Status: Pending
+
+When enable selinux, file has a default attribute:
+
+# file: here
+security.selinux="system_u:object_r:lib_t:s0"
+
+That cause there is always more output than expected.
+
+Filter out selinux related attribute info to make ptest pass.
+
+Signed-off-by: Kai Kang
+---
+diff --git a/test/run b/test/run
+index cf15252..945741e 100755
+--- a/test/run
b/test/run
+@@ -132,6 +132,23 @@ sub process_test() {
+print "[$prog_line] \$ ", join(' ',
+ map { s/\s/\\$&/g; $_ } @$p), " -- ";
+my $result = exec_test($prog, $in);
++
++ # filter selinux related attributes info
++ my @strip1;
++ my @strip2;
++ foreach (@$result) {
++ unless (/security.selinux=.*\n/) {
++ push @strip1, $_;
++ }
++ }
++ for (my $i = 0; $i <= $#strip1; $i++) {
++ if ($strip1[$i] =~ /^# file:.*/ && $strip1[$i+1] =~ /^\n$/) {
++ $i++;
++ } else {
++ push @strip2, $strip1[$i];
++ }
++ }
++ $result = \@strip2;
+my @good = ();
+my $nmax = (@$out > @$result) ? @$out : @$result;
+for (my $n=0; $n < $nmax; $n++) {
diff --git a/recipes-support/attr/attr_%.bbappend
b/recipes-support/attr/attr_%.bbappend
new file mode 100644
index 000..6be8191
--- /dev/null
+++ b/recipes-support/attr/attr_%.bbappend
@@ -0,0 +1,5 @@
+inherit selinux
+
+FILESEXTRAPATHS_prepend := "${THISDIR}/${BPN}:"
+
+SRC_URI += "${@target_selinux(d,
'file://fix-ptest-failures-when-selinux-enabled.patch')}"
--
2.14.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] The differences between rpm 4.x and rpm 5.x in Morty (Poky 2.2)
Hello Ross, Copy that. I can add smartpm for now for Morty, there is still time to experiment. I guess, I'll even wait for Rocko (Poky 2.4). I guess, this one will come October/November time frame. I still need to learn (much) more, to understand beyond classical Linux environment I am very well familiar with. Yocto is yet another, different beast for configuring and making final distros... :-) Thank you, Zoran On Mon, Sep 4, 2017 at 4:33 PM, Burton, Ross wrote: > On 4 September 2017 at 14:25, Zoran Stojsavljevic < > zoran.stojsavlje...@gmail.com> wrote: > >> How can I achieve this for Morty? I know that I need to place DNF recipes >> into recipes-devtools/. >> >> Where should I place rpm 4.x, so it'll have only DNF to be dependent from >> it? >> > > There were about 30 patches involved in the smart to DNF migration and > you'd need to backport most of them if you wanted to use dnf with morty. > > If you *need* to use Morty then you'll have to use RPM+Smart (or dpkg, or > opkg). If you want to use RPM+DNF then upgrading to Pyro is the only > sensible way. > > Ross > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-oracle-java] Is oracle-jse-jre broken on arm target ?
Hello everyone, I'm trying to add embedded JRE to a custom i.MX6 board, and when I add oracle-jse-jre recipe to my image, it starts to add a lot of native stuff so I think it's broken? As I understand it, the recipe downloads JDK and run jrecreate.sh to generate needed JRE. For me, the only thing needed by jrecreate is a valid java installation on host with JAVA_HOME set? Someone is using that recipe on arm? Best Regards, Vincent -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH] nmap: update to 7.60
LIC_CHKSUM_FILES changed do to yr update.
add a few more PACKCONFIG
Signed-off-by: Armin Kuster
---
recipes-security/nmap/{nmap_7.50.bb => nmap_7.60.bb} | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
rename recipes-security/nmap/{nmap_7.50.bb => nmap_7.60.bb} (84%)
diff --git a/recipes-security/nmap/nmap_7.50.bb
b/recipes-security/nmap/nmap_7.60.bb
similarity index 84%
rename from recipes-security/nmap/nmap_7.50.bb
rename to recipes-security/nmap/nmap_7.60.bb
index 30ae06f..a6616eb 100644
--- a/recipes-security/nmap/nmap_7.50.bb
+++ b/recipes-security/nmap/nmap_7.60.bb
@@ -3,15 +3,15 @@ DESCRIPTION = "Nmap ("Network Mapper") is a free and open
source (license) utili
SECTION = "security"
LICENSE = "GPL-2.0"
-LIC_FILES_CHKSUM =
"file://COPYING;beginline=7;endline=12;md5=87c6956e28c3603a0a1dda11bcdc227a"
+LIC_FILES_CHKSUM =
"file://COPYING;beginline=7;endline=12;md5=700c690f4ca6b1754f3f1db8645e42d9"
SRC_URI = "http://nmap.org/dist/${BP}.tar.bz2 \
file://nmap-redefine-the-python-library-dir.patch \
file://nmap-replace-shtool-mkdir-with-coreutils-mkdir-command.patch
\
"
-SRC_URI[md5sum] = "435c7e095bdd4565e0f69c41743a45be"
-SRC_URI[sha256sum] =
"e9a96a8e02bfc9e80c617932acc61112c23089521ee7d6b1502ecf8e3b1674b2"
+SRC_URI[md5sum] = "4e454266559ddf2c4e2109866c62560c"
+SRC_URI[sha256sum] =
"a8796ecc4fa6c38aad6139d9515dc8113023a82e9d787e5a5fb5fa1b05516f21"
inherit autotools-brokensep pkgconfig pythonnative distro_features_check
@@ -21,6 +21,8 @@ PACKAGECONFIG += " ${@bb.utils.contains('IMAGE_FEATURES',
'x11-base', 'zenmap',
PACKAGECONFIG[pcap] = "--with-pcap=linux, --without-pcap, libpcap, libpcap"
PACKAGECONFIG[pcre] = "--with-libpcre=${STAGING_LIBDIR}/..,
--with-libpcre=included, libpre"
PACKAGECONFIG[ssl] = "--with-openssl=${STAGING_LIBDIR}/.., --without-openssl,
openssl, openssl"
+PACKAGECONFIG[ssh2] = "--with-openssh2=${STAGING_LIBDIR}/..,
--without-openssh2, libssh2, libssh2"
+PACKAGECONFIG[libz] = "--with-libz=${STAGING_LIBDIR}/.., --without-libz, zlib,
zlib"
#disable/enable packages
PACKAGECONFIG[nping] = ",--without-nping,"
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Minutes: Yocto Project Technical Team Meeting
Attendees: Richard, Joshua L., Ross, Saul, Trevor, Stephano, Stephen, Leo, Joshua W., Michael, Bill Mills, Mark, Agenda: * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) YP 2.4 M3 released last Friday. https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.4_Status https://wiki.yoctoproject.org/wiki/Yocto_2.4_Schedule https://wiki.yoctoproject.org/wiki/Yocto_2.4_Features * Opens - 10 min * Team Sharing - 10 min * YP 2.4 M4 is in process, we are feature frozen. Richard discussed the features which were accepted into YP 2.4 and those which will push to YP 2.5. Discussed issues we are having with Autobuilder. * We discussed Pseudo issues. We have lost ongoing support for Pseudo and are struggling with issues. * YP 2.2.2 is now almost ready to be tested, most all the issues have been fixed. This should go in soon. * YP 2.3.2 is also being prepared to be tested. * Build times have improved with the new Autobuilders. * Discussed the need to test layers with YP Compatible testing. Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 * Work Telephone: (503) 712-0534 *Cell: (208) 244-4460 * Email:stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto Project Status WW36’17
Current Dev Position: YP 2.4 M4 Next Deadline: YP 2.4 Final Cut off is Sept. 18, 2017 SWAT team rotation: Todor -> Tracy on Sept. 1, 2017. SWAT team rotation: Tracy -> Alejandro on Sept. 8, 2017 https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: ·M3 rc1 was released, there were some issues found but nothing which couldn’t be addressed in M4 so we’re on track for release. ·We’ve found and fixed a number of BB_SERVER_TIMEOUT issues to the point that it can now be used with oe-selftest which gives us a good confidence level in the functionality for release. If anyone does see issues with the bitbake server changes please report them as we’ve resolved most of the known issues (the remaining ones are with the xmlrpc server). ·We are seeing intermittent qemu issues on the autobuilder and also intermittent failures particularly on qemuppc. We’re doing what we can to investigate these. ·Huge thanks to Armin for finding out the issues we were seeing on the autobuilder for morty. We continue to see some issues with one of the newest autobuilder workers but believe that many of the other issues we were seeing have been resolved and hope that the 2.2.2 release can proceed soon and be given to QA. ·Pyro has also seen many patches recently and is likely heading to a new point release once these have been tested and merged. Planned upcoming dot releases: YP 2.2.2 Cut off June 5, 2017 - Not ready to do an rc2 yet. YP 2.2.2 Release by June, 16 2017 YP 2.3.2 Cut off Sept. 1, 2017 YP 2.3.2 Release by Sept. 15, 2017 Key YP 2.4 Dates are: YP 2.4 M4 (Final) Cut off is Sept. 18, 2017 YP 2.4 M4 (Final) Release by Oct. 20, 2017 Tracking Metrics: WDD 2529 (last week 2504) (https://wiki.yoctoproject.org/charts/combo.html) Key Status Links for YP: https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.4_Status https://wiki.yoctoproject.org/wiki/Yocto_2.4_Schedule https://wiki.yoctoproject.org/wiki/Yocto_2.4_Features [If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!] Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 • Work Telephone:(503) 712-0534 •Cell: (208) 244-4460 • Email: stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Adding dependency to recipe, when dependency ins't in build system
Hello,
I have a custom recipe which has been building just fine. I am now
trying to add a runtime dependency (debian dependency) on the package,
and I can't seem to figure it out. The main issue is the dependency
isn't in the yocto build system.
I started off with what I know, and added below to the recipe.
RDEPENDS_${PN} = ""
And I received the following error.
ERROR: Nothing RPROVIDES 'package_dependency' (but
/home/yocto/fsl-release-bsp/sources/meta-custom/recipes-connectivity/ntpd-config/ntpd-config_1.0.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'miraclemax' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['miraclemax']
ERROR: Required build target 'ntpd-config' has no buildable providers.
Missing or unbuildable dependency chain was: ['ntpd-config', 'miraclemax']
After reading through some of the documentation. I found that RDEPENDS
will through an error if the package isn't in the build system.
I then tried some INSANE_SKIP
INSANE_SKIP_${PN} += "build-deps"
And was still getting the above error.
Is there any way for me to add a dependency to a package without it
being in the build system?
--
Regards,
Demetrius Pampouktsis
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Build RPi without wireless?
How do I build a Raspberry Pi image without WiFi or Bluetooth, or any of the related utilities? There seem to be lots of packages involved in this, and I can't figure out what's pulling them in in the first place. -- Ciao, Paul D. DeRocco Paulmailto:pdero...@ix.netcom.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Project Status WW35’17
And do not forget the OpenEmbedded Developer Meeting in Prague before ELCE: https://www.openembedded.org/wiki/OEDEM_2017 Philip On 08/28/2017 10:42 AM, Jolley, Stephen K wrote: > Current Dev Position: YP 2.4 M3 > > Next Deadline: YP 2.4 M3 (In QA) > > > SWAT team rotation: Paul -> Todor on Aug. 25, 2017. > > SWAT team rotation: Todor -> Tracy on Aug. 18, 2017. > > https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team > > > Key Status/Updates: > > ·We’ve reached feature freeze for 2.4 and the M3 rc1 build is in QA. > See: https://wiki.yoctoproject.org/wiki/2.4_QA_Status > > ·Some things did not make 2.4. In particular, the python manifest > rework didn’t, nor did the multiple kernels work or the switch to pkgconf by > default. These patchsets were too late in the cycle and potentially caused > too many issues. I’ve started queueing some things on master-next-2.5 in the > meantime. > > ·We’ve continued to struggle with various autobuilder reported > failures although current master appears to be working better than we’ve had > things for a while. > > ·Some fixes were merged for the bitbake server reconnection issues > and this should remove the traceback many people were seeing and generally > clean up some of the behavior for reconnections. > > ·There were some staging.bbclass fixes that have recently merged > which allow the system to cope much better with changing things like the > pkgconfig provider. > > > Planned upcoming dot releases: > > YP 2.2.2 Cut off June 5, 2017 - Not ready to do an rc2 yet. > > YP 2.2.2 Release by June, 16 2017 > > YP 2.3.2 Cut off Sept. 1, 2017 > > YP 2.3.2 Release by Sept. 15, 2017 > > > Key YP 2.4 Dates are: > > YP 2.4 M3 Cut off is Aug. 21, 2017 (In QA) > > YP 2.4 M3 Release by Sept. 1, 2017 > > YP 2.4 M4 (Final) Cut off is Sept. 18, 2017 > > YP 2.4 M4 (Final) Release by Oct. 20, 2017 > > > Tracking Metrics: > > WDD 2504 (last week 2476) > > (https://wiki.yoctoproject.org/charts/combo.html) > > > Key Status Links for YP: > > https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.4_Status > > https://wiki.yoctoproject.org/wiki/Yocto_2.4_Schedule > > https://wiki.yoctoproject.org/wiki/Yocto_2.4_Features > > > [If anyone has suggestions for other information you’d like to see on this > weekly status update, let us know!] > > > Thanks, > > Stephen K. Jolley > Yocto Project Program Manager > INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 > • Work Telephone:(503) 712-0534 > •Cell: (208) 244-4460 > • Email: stephen.k.jol...@intel.com > > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH] bluez5: add functions for raspberrypi0-wifi
Sorry I am late.
I could not get time enough for this work.
I will send patches soon.
By the way, If the Michal's work that Andrei pointed and my patches are
similar, please drop my patches.
2017-09-04 20:05 GMT+09:00 Andrei Gherzan :
>
>
> On Fri, Aug 25, 2017 at 9:17 PM, Yusuke Mitsuki <
> mickey.happygolu...@gmail.com> wrote:
>
>> okay. I will try.
>>
>> 2017-08-25 17:51 GMT+09:00 Paul Barker :
>>
>>> On Thu, Aug 24, 2017 at 1:05 PM, Yusuke Mitsuki
>>> wrote:
>>> > hciattach on raspberrypi0-wifi failed because BCM43430A1.hcd is not
>>> found.
>>> >
>>> > Paches that in order to use bluetooth with BCM43430 are not enabled.
>>> > Functions are only enabled with raspberrypi3 in bluez5_%.bbappend like
>>> as follows:
>>> >
>>> > - SRC_URI_append_raspberrypi3
>>> > - do_install_append_raspberrypi3()
>>> > - FILES_${PN}_append_raspberrypi3
>>> > - SYSTEMD_SERVICE_${PN}_append_raspberrypi3
>>> >
>>> > These should be enabled with raspberrypi0-wifi too.
>>> >
>>> > Signed-off-by: Yusuke Mitsuki
>>> > ---
>>> > recipes-connectivity/bluez5/bluez5_%.bbappend | 25
>>> +
>>> > 1 file changed, 25 insertions(+)
>>> >
>>> > diff --git a/recipes-connectivity/bluez5/bluez5_%.bbappend
>>> b/recipes-connectivity/bluez5/bluez5_%.bbappend
>>> > index 956d776..075dc2b 100644
>>> > --- a/recipes-connectivity/bluez5/bluez5_%.bbappend
>>> > +++ b/recipes-connectivity/bluez5/bluez5_%.bbappend
>>> > @@ -24,3 +24,28 @@ FILES_${PN}_append_raspberrypi3 = " \
>>> > "
>>> >
>>> > SYSTEMD_SERVICE_${PN}_append_raspberrypi3 = " brcm43438.service"
>>> > +
>>> > +SRC_URI_append_raspberrypi0-wifi = " \
>>> > +file://BCM43430A1.hcd \
>>> > +file://0001-bcm43xx-Add-bcm43xx-3wire-variant.patch \
>>> > +
>>> > file://0002-bcm43xx-The-UART-speed-must-be-reset-after-the-firmw.patch
>>> \
>>> > +file://0003-Increase-firmware-load-timeout-to-30s.patch \
>>> > +file://0004-Move-the-43xx-firmware-into-lib-firmware.patch \
>>> > +file://brcm43438.service \
>>> > +"
>>> > +
>>> > +do_install_append_raspberrypi0-wifi() {
>>> > +install -d ${D}/lib/firmware/brcm/
>>> > +install -m 0644 ${WORKDIR}/BCM43430A1.hcd
>>> ${D}/lib/firmware/brcm/BCM43430A1.hcd
>>> > +
>>> > +if ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'true',
>>> 'false', d)}; then
>>> > +install -d ${D}${systemd_unitdir}/system
>>> > +install -m 0644 ${WORKDIR}/brcm43438.service
>>> ${D}${systemd_unitdir}/system
>>> > +fi
>>> > +}
>>> > +
>>> > +FILES_${PN}_append_raspberrypi0-wifi = " \
>>> > +/lib/firmware/brcm/BCM43430A1.hcd \
>>> > +"
>>> > +
>>> > +SYSTEMD_SERVICE_${PN}_append_raspberrypi0-wifi = " brcm43438.service"
>>>
>>> I don't like the amount of duplication here. Could you define some
>>> common variables and use those in the appends? This will make it
>>> easier to change/upgrade in the future and avoid risk of the
>>> duplicates falling out of sync with each other.
>>>
>>> Eg.
>>>
>>> RPI_WIFI_SOURCES = ""
>>>
>>> SRC_URI_append_raspberrypi3 = "${RPI_WIFI_SOURCES}"
>>> SRC_URI_append_raspberrypi0-wifi = "${RPI_WIFI_SOURCES}"
>>>
>>>
> I know Michal worked on this not long ago. Michal, could you give us some
> hints here? Maybe backport the changes in resinOS?
>
>
> --
> Andrei Gherzan
>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH v2 1/2] bluez5: add functions/variables to enabling bluetooth on another raspberrypi
functions/variables in this bbappend implemented for only raspberrypi3.
But these must be able to used to enabling bluetooth on another raspberrypi
that has bluetooth feature such as raspberrypi0-wifi.
The simple solution is a duplicating these but it is not good ideas for
maintainance.
Add functions/variables follows to simplify to enabling bluetooth on another
raspberrypi that has bluetooth.
- BCM_BT_SOURCES
- enable_bcm_bluetooth()
- BCM_BT_FIRMWARE
- BCM_BT_SERVICE
Signed-off-by: Yusuke Mitsuki
---
recipes-connectivity/bluez5/bluez5_%.bbappend | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/recipes-connectivity/bluez5/bluez5_%.bbappend
b/recipes-connectivity/bluez5/bluez5_%.bbappend
index 956d776..b2fbf22 100644
--- a/recipes-connectivity/bluez5/bluez5_%.bbappend
+++ b/recipes-connectivity/bluez5/bluez5_%.bbappend
@@ -1,6 +1,6 @@
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-SRC_URI_append_raspberrypi3 = " \
+BCM_BT_SOURCES = " \
file://BCM43430A1.hcd \
file://0001-bcm43xx-Add-bcm43xx-3wire-variant.patch \
file://0002-bcm43xx-The-UART-speed-must-be-reset-after-the-firmw.patch \
@@ -9,7 +9,7 @@ SRC_URI_append_raspberrypi3 = " \
file://brcm43438.service \
"
-do_install_append_raspberrypi3() {
+enable_bcm_bluetooth() {
install -d ${D}/lib/firmware/brcm/
install -m 0644 ${WORKDIR}/BCM43430A1.hcd
${D}/lib/firmware/brcm/BCM43430A1.hcd
@@ -19,8 +19,18 @@ do_install_append_raspberrypi3() {
fi
}
-FILES_${PN}_append_raspberrypi3 = " \
+BCM_BT_FIRMWARE = " \
/lib/firmware/brcm/BCM43430A1.hcd \
"
-SYSTEMD_SERVICE_${PN}_append_raspberrypi3 = " brcm43438.service"
+BCM_BT_SERVICE = " brcm43438.service"
+
+SRC_URI_append_raspberrypi3 = " ${BCM_BT_SOURCES}"
+
+do_install_append_raspberrypi3() {
+enable_bcm_bluetooth
+}
+
+FILES_${PN}_append_raspberrypi3 = " ${BCM_BT_FIRMWARE}"
+
+SYSTEMD_SERVICE_${PN}_append_raspberrypi3 = " ${BCM_BT_SERVICE}"
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH v2 2/2] bluez5: enable bluetooth on raspberrypi0-wifi
Add functions/variable to enabling bluetooth on raspberrypi0-wifi.
Signed-off-by: Yusuke Mitsuki
---
recipes-connectivity/bluez5/bluez5_%.bbappend | 12
1 file changed, 12 insertions(+)
diff --git a/recipes-connectivity/bluez5/bluez5_%.bbappend
b/recipes-connectivity/bluez5/bluez5_%.bbappend
index b2fbf22..03efd5c 100644
--- a/recipes-connectivity/bluez5/bluez5_%.bbappend
+++ b/recipes-connectivity/bluez5/bluez5_%.bbappend
@@ -25,6 +25,7 @@ BCM_BT_FIRMWARE = " \
BCM_BT_SERVICE = " brcm43438.service"
+# for raspberrypi3
SRC_URI_append_raspberrypi3 = " ${BCM_BT_SOURCES}"
do_install_append_raspberrypi3() {
@@ -34,3 +35,14 @@ do_install_append_raspberrypi3() {
FILES_${PN}_append_raspberrypi3 = " ${BCM_BT_FIRMWARE}"
SYSTEMD_SERVICE_${PN}_append_raspberrypi3 = " ${BCM_BT_SERVICE}"
+
+# for raspberrypi0-wifi
+SRC_URI_append_raspberrypi0-wifi = " ${BCM_BT_SOURCES}"
+
+do_install_append_raspberrypi0-wifi() {
+enable_bcm_bluetooth
+}
+
+FILES_${PN}_append_raspberrypi0-wifi = " ${BCM_BT_FIRMWARE}"
+
+SYSTEMD_SERVICE_${PN}_append_raspberrypi0-wifi = " ${BCM_BT_SERVICE}"
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Building Custom Python 3 Packages
On Saturday, 2 September 2017 12:42:09 AM NZST Alexander Kanavin wrote:
> On 08/31/2017 04:54 PM, Seilis, Aaron wrote:
> > This clearly indicates that the issue is that the build is looking
> > for setup.py in the ${B} location, but it is only present in the ${S}
> > location when `devtool modify` has been run. I have tried setting
> > ${B} to ${S} explicitly in the recipe, but this doesn't result in
> > ${B} being changed when I run `bitbake -e mytool`. I could always
> > copy ${S} to ${B} in the recipe, but that seems a bit hack-ish.
> >
> > Did I miss something or is there another way that Python builds are
> > intended to work?
>
> I think this might be a limitation of setuptools: they do not support
> out-of-tree builds (which is a must for devtool modify'). If you can
> figure out how to solve it, that would be nice!
devtool modify does not require out-of-tree builds - I think in this instance
it's assuming that's OK, and it's supposed to be following what the recipe
originally used so that may be a bug. The workaround is to tell it to use the
same directory with the -s/--same-dir option.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
