[yocto] Building boost-python

2017-06-07 Thread Jakob Hasse 

Hello,

One of my layers needs boost-python.
When I try to build boost-python with bitbake, it complains:

ERROR: Nothing PROVIDES 'boost-python'

How can I fix this?
Boost itself builds and I also included
PACKAGECONFIG_pn_boost = "python"
without any effect.

My bblayers.conf is here:

# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "6"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
  /usr/local/dey-2.0/sources/poky/meta \
  /usr/local/dey-2.0/sources/poky/meta-yocto \
  /usr/local/dey-2.0/sources/poky/meta-yocto-bsp \
  /usr/local/dey-2.0/sources/meta-openembedded/meta-oe \
  /usr/local/dey-2.0/sources/meta-openembedded/meta-python \
/usr/local/dey-2.0/sources/meta-openembedded/meta-networking \
/usr/local/dey-2.0/sources/meta-openembedded/meta-webserver \
  /usr/local/dey-2.0/sources/meta-qt5 \
  /usr/local/dey-2.0/sources/meta-swupdate \
  /usr/local/dey-2.0/sources/meta-fsl-arm \
  /usr/local/dey-2.0/sources/meta-fsl-demos \
  /usr/local/dey-2.0/sources/meta-digi/meta-digi-arm \
  /usr/local/dey-2.0/sources/meta-digi/meta-digi-dey \
  /usr/local/dey-2.0/sources/meta-java/ \
  /usr/local/dey-2.0/sources/meta-iot-cloud/ \

  "
BBLAYERS_NON_REMOVABLE ?= " \
  /usr/local/dey-2.0/sources/poky/meta \
  /usr/local/dey-2.0/sources/poky/meta-yocto \
  "

Any help is welcome!
Jakob

--
Jakob Hasse
Software Developement

E: jakob.ha...@smart-home-technology.ch
T: +41 44 552 02 66

Smart Home Technology GmbH
www.smart-home-technology.ch

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

Re: [yocto] Building boost-python

2017-06-07 Thread VanCutsem, Geoffroy 


> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Jakob Hasse
> Sent: Wednesday, June 7, 2017 11:48 AM
> To: Yocto List 
> Subject: [yocto] Building boost-python
> 
> Hello,
> 
> One of my layers needs boost-python.
> When I try to build boost-python with bitbake, it complains:
> 
> ERROR: Nothing PROVIDES 'boost-python'
> 
> How can I fix this?
> Boost itself builds and I also included
> PACKAGECONFIG_pn_boost = "python"
> without any effect.

I believe the correct spelling is:
PACKAGECONFIG_pn-boost = "python"
(note the hyphen instead of underscore)

> 
> My bblayers.conf is here:
> 
> # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf #
> changes incompatibly LCONF_VERSION = "6"
> 
> BBPATH = "${TOPDIR}"
> BBFILES ?= ""
> 
> BBLAYERS ?= " \
>/usr/local/dey-2.0/sources/poky/meta \
>/usr/local/dey-2.0/sources/poky/meta-yocto \
>/usr/local/dey-2.0/sources/poky/meta-yocto-bsp \
>/usr/local/dey-2.0/sources/meta-openembedded/meta-oe \
>/usr/local/dey-2.0/sources/meta-openembedded/meta-python \
> /usr/local/dey-2.0/sources/meta-openembedded/meta-networking \
> /usr/local/dey-2.0/sources/meta-openembedded/meta-webserver \
>/usr/local/dey-2.0/sources/meta-qt5 \
>/usr/local/dey-2.0/sources/meta-swupdate \
>/usr/local/dey-2.0/sources/meta-fsl-arm \
>/usr/local/dey-2.0/sources/meta-fsl-demos \
>/usr/local/dey-2.0/sources/meta-digi/meta-digi-arm \
>/usr/local/dey-2.0/sources/meta-digi/meta-digi-dey \
>/usr/local/dey-2.0/sources/meta-java/ \
>/usr/local/dey-2.0/sources/meta-iot-cloud/ \
> 
>"
> BBLAYERS_NON_REMOVABLE ?= " \
>/usr/local/dey-2.0/sources/poky/meta \
>/usr/local/dey-2.0/sources/poky/meta-yocto \
>"
> 
> Any help is welcome!
> Jakob
> 
> --
> Jakob Hasse
> Software Developement
> 
> E: jakob.ha...@smart-home-technology.ch
> T: +41 44 552 02 66
> 
> Smart Home Technology GmbH
> www.smart-home-technology.ch
> 
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Building boost-python

2017-06-07 Thread Jakob Hasse 



On 07.06.2017 11:59, VanCutsem, Geoffroy wrote:



-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Jakob Hasse
Sent: Wednesday, June 7, 2017 11:48 AM
To: Yocto List 
Subject: [yocto] Building boost-python

Hello,

One of my layers needs boost-python.
When I try to build boost-python with bitbake, it complains:

ERROR: Nothing PROVIDES 'boost-python'

How can I fix this?
Boost itself builds and I also included
PACKAGECONFIG_pn_boost = "python"
without any effect.

I believe the correct spelling is:
PACKAGECONFIG_pn-boost = "python"
(note the hyphen instead of underscore)
Yes, I saw it somewhere else now with a hyphen, too, but even with the 
corrected local.conf, the problem still remains.

Bitbake quits with the same error message as before



My bblayers.conf is here:

# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf #
changes incompatibly LCONF_VERSION = "6"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
/usr/local/dey-2.0/sources/poky/meta \
/usr/local/dey-2.0/sources/poky/meta-yocto \
/usr/local/dey-2.0/sources/poky/meta-yocto-bsp \
/usr/local/dey-2.0/sources/meta-openembedded/meta-oe \
/usr/local/dey-2.0/sources/meta-openembedded/meta-python \
/usr/local/dey-2.0/sources/meta-openembedded/meta-networking \
/usr/local/dey-2.0/sources/meta-openembedded/meta-webserver \
/usr/local/dey-2.0/sources/meta-qt5 \
/usr/local/dey-2.0/sources/meta-swupdate \
/usr/local/dey-2.0/sources/meta-fsl-arm \
/usr/local/dey-2.0/sources/meta-fsl-demos \
/usr/local/dey-2.0/sources/meta-digi/meta-digi-arm \
/usr/local/dey-2.0/sources/meta-digi/meta-digi-dey \
/usr/local/dey-2.0/sources/meta-java/ \
/usr/local/dey-2.0/sources/meta-iot-cloud/ \

"
BBLAYERS_NON_REMOVABLE ?= " \
/usr/local/dey-2.0/sources/poky/meta \
/usr/local/dey-2.0/sources/poky/meta-yocto \
"

Any help is welcome!
Jakob

--
Jakob Hasse
Software Developement

E: jakob.ha...@smart-home-technology.ch
T: +41 44 552 02 66

Smart Home Technology GmbH
www.smart-home-technology.ch

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


--
Jakob Hasse
Software Developement

E: jakob.ha...@smart-home-technology.ch
T: +41 44 552 02 66

Smart Home Technology GmbH
www.smart-home-technology.ch

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

Re: [yocto] [PATCH] qt4-native: depend on icu-native to fix build on systems with icu >=59

2017-06-07 Thread Alexander Kanavin 

On 06/07/2017 07:19 AM, Cody P Schafer wrote:

Previously, qt4-native would use the system icu to build.

Trying to build against a system ICU 59, however, fails with this root
error:

| In file included from /usr/include/unicode/uversion.h:30:0,
|  from tools/qlocale_icu.cpp:46:
| /usr/include/unicode/umachine.h:347:13: error: ‘char16_t’ does not name a 
type; did you mean ‘wchar_t’?
|  typedef char16_t UChar;
|  ^~~~
|  wchar_t



We will introduce icu 59 to oe-core at some point (in fact, I have a 
patch queued), and then this fix will no longer work.


You need to fix Qt4 itself.

Alex

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

Re: [yocto] [PATCH] qt4-native: depend on icu-native to fix build on systems with icu >=59

2017-06-07 Thread Cody P Schafer 
Yep, for `master` that is certainly true.

For `morty` & `pyro` though, meta-qt4 could keep working by using icu-native.

The source of this issue being qt4's general incompatibility with C++
11 (we build with c++98 because of build errors with the newer std)
makes me wonder if it will even be possible to continue supporting qt4
going forward.

This may turn out like the openssl conflicts in that we'll need to
disable qt4's use of icu entirely.


On Wed, Jun 7, 2017 at 8:24 AM, Alexander Kanavin
 wrote:
> On 06/07/2017 07:19 AM, Cody P Schafer wrote:
>>
>> Previously, qt4-native would use the system icu to build.
>>
>> Trying to build against a system ICU 59, however, fails with this root
>> error:
>>
>> | In file included from /usr/include/unicode/uversion.h:30:0,
>> |  from tools/qlocale_icu.cpp:46:
>> | /usr/include/unicode/umachine.h:347:13: error: ‘char16_t’ does not name
>> a type; did you mean ‘wchar_t’?
>> |  typedef char16_t UChar;
>> |  ^~~~
>> |  wchar_t
>>
>
> We will introduce icu 59 to oe-core at some point (in fact, I have a patch
> queued), and then this fix will no longer work.
>
> You need to fix Qt4 itself.
>
> Alex
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Getting linker -l into a bbappend

2017-06-07 Thread colin.helliwell 
I have an autotools (C++) app which builds fine with my default recipe. But
for a particular platform an additional (C) library is needed, so I have a
bbappend.
I can add in the additional compiler flag here, but I'm struggling to
specify the additional library linkage - I think it's because the ordering
on the linker command line is wrong.

If I add '-lfoo' to the base Makefile.am then it builds fine (though
strangely, "-lfoo" isn't anywhere in the linker command line?). 
But I'm trying to put this into just the 'append' rather than altering the
base [non-platform-specific] Makefile.

I've tried 
EXTRA_OEMAKE += " LDFLAGS+="-lfoo" " 
and
LDFLAGS+="-lrfctrl"
but these don't seem to construct the correct linkage order (functions from
the library are undefined references)

Is there a way to append this in the right way?
Thanks


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

Re: [yocto] Getting linker -l into a bbappend

2017-06-07 Thread Khem Raj 
On Wed, Jun 7, 2017 at 9:37 AM,   wrote:
> I have an autotools (C++) app which builds fine with my default recipe. But
> for a particular platform an additional (C) library is needed, so I have a
> bbappend.
> I can add in the additional compiler flag here, but I'm struggling to
> specify the additional library linkage - I think it's because the ordering
> on the linker command line is wrong.
>
> If I add '-lfoo' to the base Makefile.am then it builds fine (though
> strangely, "-lfoo" isn't anywhere in the linker command line?).
> But I'm trying to put this into just the 'append' rather than altering the
> base [non-platform-specific] Makefile.
>
> I've tried
> EXTRA_OEMAKE += " LDFLAGS+="-lfoo" "
> and
> LDFLAGS+="-lrfctrl"
> but these don't seem to construct the correct linkage order (functions from
> the library are undefined references)
>
> Is there a way to append this in the right way?

it depends on components build systems some are more accommodating of
the env passed to them some are not. So in many
cases you have to patch the make system of the component to
allow it to accept changes to variables passed from bitbake env
from what you explain it seems you might have to look into
component's build system to accommodate it.

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

Re: [yocto] Getting linker -l into a bbappend

2017-06-07 Thread Khem Raj 
On Wed, Jun 7, 2017 at 10:14 AM, Colin Helliwell
 wrote:
>
>> On 07 June 2017 at 18:12 Khem Raj  wrote:
>>
>> On Wed, Jun 7, 2017 at 9:37 AM,  wrote:
>>
>> > I have an autotools (C++) app which builds fine with my default recipe. But
>> > for a particular platform an additional (C) library is needed, so I have a
>> > bbappend.
>> > I can add in the additional compiler flag here, but I'm struggling to
>> > specify the additional library linkage - I think it's because the ordering
>> > on the linker command line is wrong.
>> >
>> > If I add '-lfoo' to the base Makefile.am then it builds fine (though
>> > strangely, "-lfoo" isn't anywhere in the linker command line?).
>> > But I'm trying to put this into just the 'append' rather than altering the
>> > base [non-platform-specific] Makefile.
>> >
>> > I've tried
>> >  EXTRA_OEMAKE += " LDFLAGS+="-lfoo" "
>> > and
>> >  LDFLAGS+="-lrfctrl"
>> > but these don't seem to construct the correct linkage order (functions from
>> > the library are undefined references)
>> >
>> > Is there a way to append this in the right way?
>>
>> it depends on components build systems some are more accommodating of
>> the env passed to them some are not. So in many
>> cases you have to patch the make system of the component to
>> allow it to accept changes to variables passed from bitbake env
>> from what you explain it seems you might have to look into
>> component's build system to accommodate it.
>>
>
> Thanks Khem. I *could* patch the Makefile.am, if there's no other way

the components makefiles have to accept it, bitbake can only delegate
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Getting linker -l into a bbappend

2017-06-07 Thread Colin Helliwell 

> On 07 June 2017 at 18:12 Khem Raj  wrote:
> 
> On Wed, Jun 7, 2017 at 9:37 AM,  wrote:
> 
> > I have an autotools (C++) app which builds fine with my default recipe. But
> > for a particular platform an additional (C) library is needed, so I have a
> > bbappend.
> > I can add in the additional compiler flag here, but I'm struggling to
> > specify the additional library linkage - I think it's because the ordering
> > on the linker command line is wrong.
> > 
> > If I add '-lfoo' to the base Makefile.am then it builds fine (though
> > strangely, "-lfoo" isn't anywhere in the linker command line?).
> > But I'm trying to put this into just the 'append' rather than altering the
> > base [non-platform-specific] Makefile.
> > 
> > I've tried
> >  EXTRA_OEMAKE += " LDFLAGS+="-lfoo" "
> > and
> >  LDFLAGS+="-lrfctrl"
> > but these don't seem to construct the correct linkage order (functions from
> > the library are undefined references)
> > 
> > Is there a way to append this in the right way?
> 
> it depends on components build systems some are more accommodating of
> the env passed to them some are not. So in many
> cases you have to patch the make system of the component to
> allow it to accept changes to variables passed from bitbake env
> from what you explain it seems you might have to look into
> component's build system to accommodate it.
> 

Thanks Khem. I *could* patch the Makefile.am, if there's no other way
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH] pi-blaster: update to include proper rpi3 support

2017-06-07 Thread Petter Mabäcker 
Update to latest available revision, in order to include proper rpi3
support as well as latest fixes.

Signed-off-by: Petter Mabäcker 
---
 .../files/remove-initscript-lsb-dependency.patch   | 37 --
 recipes-devtools/pi-blaster/pi-blaster.inc |  2 +-
 recipes-devtools/pi-blaster/pi-blaster_git.bb  |  2 +-
 3 files changed, 30 insertions(+), 11 deletions(-)

diff --git 
a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch 
b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
index 7ea9a3b..c8afe60 100644
--- a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
+++ b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
@@ -1,13 +1,28 @@
-Remove dependencies on LSB functions
+From 1338f98a279616f4e5e9ea30a25d1dfa0c7df5d6 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
+Date: Sun, 4 Jun 2017 12:22:40 +0200
+Subject: [PATCH] Remove dependencies on LSB functions
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+See this as a rebase of the previous 'Remove dependencies on LSB
+functions patch' with only minor modifications from the original version,
+based on the work done by Alex Lennon  in
+'25fd817 pi-blaster: Added recipe'.
 
 Upstream-Status: Inappropriate [configuration]
 
-Signed-off-by: Alex Lennon 
+Signed-off-by: Petter Mabäcker 
+---
+ debian/pi-blaster.init | 38 +++---
+ 1 file changed, 7 insertions(+), 31 deletions(-)
 
-diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
 git.org/pi-blaster.boot.sh 2014-05-20 14:49:44.378582168 +0100
-+++ git/pi-blaster.boot.sh 2014-05-20 14:51:08.330582386 +0100
-@@ -28,12 +28,12 @@
+diff --git a/debian/pi-blaster.init b/debian/pi-blaster.init
+index b142d70..01a686c 100644
+--- a/debian/pi-blaster.init
 b/debian/pi-blaster.init
+@@ -28,12 +28,12 @@ SCRIPTNAME=/etc/init.d/$NAME
  [ -r /etc/default/$NAME ] && . /etc/default/$NAME
  
  # Load the VERBOSE setting and other rcS variables
@@ -22,7 +37,7 @@ diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
  
  #
  # Function that starts the daemon/service
-@@ -77,48 +77,23 @@
+@@ -77,48 +77,24 @@ do_stop()
  
  case "$1" in
start)
@@ -52,6 +67,7 @@ diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
# 'force-reload' alias
#
 -  log_daemon_msg "Restarting $DESC" "$NAME"
++  echo "Restarting $DESC" "$NAME"
do_stop
 -  case "$?" in
 -0|1)
@@ -67,11 +83,14 @@ diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
 -  log_end_msg 1
 -  ;;
 -  esac
-+  do_start
++do_start
;;
*)
 -  echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
-+  echo "Usage: $SCRIPTNAME {start|stop|restart}" >&2
++  echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload}" >&2
exit 3
;;
  esac
+-- 
+1.9.1
+
diff --git a/recipes-devtools/pi-blaster/pi-blaster.inc 
b/recipes-devtools/pi-blaster/pi-blaster.inc
index a3beccc..a548957 100644
--- a/recipes-devtools/pi-blaster/pi-blaster.inc
+++ b/recipes-devtools/pi-blaster/pi-blaster.inc
@@ -2,7 +2,7 @@ DESCRIPTION = "This project enables PWM on the GPIO pins you 
request of a Raspbe
 HOMEPAGE = "https://github.com/sarfata/pi-blaster/";
 SECTION = "devel/libs"
 LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://README.md;beginline=157;endline=170;md5=f20832f31126609af5a7bf2340014540"
+LIC_FILES_CHKSUM = 
"file://README.md;beginline=212;endline=239;md5=a012868ef5f83b9f257af253d7cb07a3"
 
 SRC_URI = "git://github.com/sarfata/pi-blaster \
file://remove-initscript-lsb-dependency.patch \
diff --git a/recipes-devtools/pi-blaster/pi-blaster_git.bb 
b/recipes-devtools/pi-blaster/pi-blaster_git.bb
index 263852b..ac812ab 100644
--- a/recipes-devtools/pi-blaster/pi-blaster_git.bb
+++ b/recipes-devtools/pi-blaster/pi-blaster_git.bb
@@ -1,3 +1,3 @@
 require pi-blaster.inc
 
-SRCREV = "ec5e1b4c6191d8f9a538497dbbb86f9cf0de7016"
+SRCREV = "9f45eb23a8a3b2d1c08d08a6d68f206fe91ecf4c"
-- 
1.9.1

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

Re: [yocto] [meta-raspberrypi][PATCH] pi-blaster: update to include proper rpi3 support

2017-06-07 Thread Khem Raj 
On Wed, Jun 7, 2017 at 2:17 PM Petter Mabäcker  wrote:

> Update to latest available revision, in order to include proper rpi3
> support as well as latest fixes.
>
> Signed-off-by: Petter Mabäcker 
> ---
>  .../files/remove-initscript-lsb-dependency.patch   | 37
> --
>  recipes-devtools/pi-blaster/pi-blaster.inc |  2 +-
>  recipes-devtools/pi-blaster/pi-blaster_git.bb  |  2 +-
>  3 files changed, 30 insertions(+), 11 deletions(-)
>
> diff --git
> a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
> b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
> index 7ea9a3b..c8afe60 100644
> ---
> a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
> +++
> b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
> @@ -1,13 +1,28 @@
> -Remove dependencies on LSB functions
> +From 1338f98a279616f4e5e9ea30a25d1dfa0c7df5d6 Mon Sep 17 00:00:00 2001
> +From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
> +Date: Sun, 4 Jun 2017 12:22:40 +0200
> +Subject: [PATCH] Remove dependencies on LSB functions
> +MIME-Version: 1.0
> +Content-Type: text/plain; charset=UTF-8
> +Content-Transfer-Encoding: 8bit
> +
> +See this as a rebase of the previous 'Remove dependencies on LSB
> +functions patch' with only minor modifications from the original version,
> +based on the work done by Alex Lennon  in
> +'25fd817 pi-blaster: Added recipe'.
>
>  Upstream-Status: Inappropriate [configuration]
>
> -Signed-off-by: Alex Lennon 
> +Signed-off-by: Petter Mabäcker 
> +---
> + debian/pi-blaster.init | 38 +++---
> + 1 file changed, 7 insertions(+), 31 deletions(-)
>
> -diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
>  git.org/pi-blaster.boot.sh 2014-05-20 14:49:44.378582168 +0100
> -+++ git/pi-blaster.boot.sh 2014-05-20 14:51:08.330582386 +0100
> -@@ -28,12 +28,12 @@
> +diff --git a/debian/pi-blaster.init b/debian/pi-blaster.init
> +index b142d70..01a686c 100644
> +--- a/debian/pi-blaster.init
>  b/debian/pi-blaster.init
> +@@ -28,12 +28,12 @@ SCRIPTNAME=/etc/init.d/$NAME
>   [ -r /etc/default/$NAME ] && . /etc/default/$NAME
>
>   # Load the VERBOSE setting and other rcS variables
> @@ -22,7 +37,7 @@ diff -ur git.org/pi-blaster.boot.sh git/
> pi-blaster.boot.sh
>
>   #
>   # Function that starts the daemon/service
> -@@ -77,48 +77,23 @@
> +@@ -77,48 +77,24 @@ do_stop()
>
>   case "$1" in
> start)
> @@ -52,6 +67,7 @@ diff -ur git.org/pi-blaster.boot.sh git/
> pi-blaster.boot.sh
> # 'force-reload' alias
> #
>  -  log_daemon_msg "Restarting $DESC" "$NAME"
> ++  echo "Restarting $DESC" "$NAME"
> do_stop
>  -  case "$?" in
>  -0|1)
> @@ -67,11 +83,14 @@ diff -ur git.org/pi-blaster.boot.sh git/
> pi-blaster.boot.sh
>  -  log_end_msg 1
>  -  ;;
>  -  esac
> -+  do_start
> ++do_start
> ;;
> *)
>  -  echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}"
> >&2
> -+  echo "Usage: $SCRIPTNAME {start|stop|restart}" >&2
> ++  echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload}" >&2
> exit 3
> ;;
>   esac
> +--
> +1.9.1
> +
> diff --git a/recipes-devtools/pi-blaster/pi-blaster.inc
> b/recipes-devtools/pi-blaster/pi-blaster.inc
> index a3beccc..a548957 100644
> --- a/recipes-devtools/pi-blaster/pi-blaster.inc
> +++ b/recipes-devtools/pi-blaster/pi-blaster.inc
> @@ -2,7 +2,7 @@ DESCRIPTION = "This project enables PWM on the GPIO pins
> you request of a Raspbe
>  HOMEPAGE = "https://github.com/sarfata/pi-blaster/";
>  SECTION = "devel/libs"
>  LICENSE = "MIT"
> -LIC_FILES_CHKSUM =
> "file://README.md;beginline=157;endline=170;md5=f20832f31126609af5a7bf2340014540"
> +LIC_FILES_CHKSUM =
> "file://README.md;beginline=212;endline=239;md5=a012868ef5f83b9f257af253d7cb07a3"


What changed here ?

>
>
>  SRC_URI = "git://github.com/sarfata/pi-blaster \
> file://remove-initscript-lsb-dependency.patch \
> diff --git a/recipes-devtools/pi-blaster/pi-blaster_git.bb
> b/recipes-devtools/pi-blaster/pi-blaster_git.bb
> index 263852b..ac812ab 100644
> --- a/recipes-devtools/pi-blaster/pi-blaster_git.bb
> +++ b/recipes-devtools/pi-blaster/pi-blaster_git.bb
> @@ -1,3 +1,3 @@
>  require pi-blaster.inc
>
> -SRCREV = "ec5e1b4c6191d8f9a538497dbbb86f9cf0de7016"
> +SRCREV = "9f45eb23a8a3b2d1c08d08a6d68f206fe91ecf4c"
> --
> 1.9.1
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] pi-blaster: update to include proper rpi3 support

2017-06-07 Thread Petter Mabäcker 
 

2017-06-08 00:54 skrev Khem Raj: 

> On Wed, Jun 7, 2017 at 2:17 PM
Petter Mabäcker  wrote: 
> 
>> Update to latest
available revision, in order to include proper rpi3
>> support as well
as latest fixes.
>> 
>> Signed-off-by: Petter Mabäcker

>> ---
>>
.../files/remove-initscript-lsb-dependency.patch | 37
--
>> recipes-devtools/pi-blaster/pi-blaster.inc | 2
+-
>> recipes-devtools/pi-blaster/pi-blaster_git.bb [1] | 2 +-
>> 3
files changed, 30 insertions(+), 11 deletions(-)
>> 
>> diff --git
a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>>
index 7ea9a3b..c8afe60 100644
>> ---
a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>>
+++
b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>>
@@ -1,13 +1,28 @@
>> -Remove dependencies on LSB functions
>> +From
1338f98a279616f4e5e9ea30a25d1dfa0c7df5d6 Mon Sep 17 00:00:00 2001
>>
+From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
>> +Date:
Sun, 4 Jun 2017 12:22:40 +0200
>> +Subject: [PATCH] Remove dependencies
on LSB functions
>> +MIME-Version: 1.0
>> +Content-Type: text/plain;
charset=UTF-8
>> +Content-Transfer-Encoding: 8bit
>> +
>> +See this as a
rebase of the previous 'Remove dependencies on LSB
>> +functions patch'
with only minor modifications from the original version,
>> +based on
the work done by Alex Lennon  in
>>
+'25fd817 pi-blaster: Added recipe'.
>> 
>> Upstream-Status:
Inappropriate [configuration]
>> 
>> -Signed-off-by: Alex Lennon

>> +Signed-off-by: Petter Mabäcker

>> +---
>> + debian/pi-blaster.init | 38
+++---
>> + 1 file changed, 7
insertions(+), 31 deletions(-)
>> 
>> -diff -ur
git.org/pi-blaster.boot.sh [2] git/pi-blaster.boot.sh [3]
>> 
git.org/pi-blaster.boot.sh [2] 2014-05-20 14:49:44.378582168 +0100
>>
-+++ git/pi-blaster.boot.sh [3] 2014-05-20 14:51:08.330582386 +0100
>>
-@@ -28,12 +28,12 @@
>> +diff --git a/debian/pi-blaster.init
b/debian/pi-blaster.init
>> +index b142d70..01a686c 100644
>> +---
a/debian/pi-blaster.init
>>  b/debian/pi-blaster.init
>> +@@ -28,12
+28,12 @@ SCRIPTNAME=/etc/init.d/$NAME
>> [ -r /etc/default/$NAME ] && .
/etc/default/$NAME
>> 
>> # Load the VERBOSE setting and other rcS
variables
>> @@ -22,7 +37,7 @@ diff -ur git.org/pi-blaster.boot.sh [2]
git/pi-blaster.boot.sh [3]
>> 
>> #
>> # Function that starts the
daemon/service
>> -@@ -77,48 +77,23 @@
>> +@@ -77,48 +77,24 @@
do_stop()
>> 
>> case "$1" in
>> start)
>> @@ -52,6 +67,7 @@ diff -ur
git.org/pi-blaster.boot.sh [2] git/pi-blaster.boot.sh [3]
>> #
'force-reload' alias
>> #
>> - log_daemon_msg "Restarting $DESC"
"$NAME"
>> ++ echo "Restarting $DESC" "$NAME"
>> do_stop
>> - case "$?"
in
>> - 0|1)
>> @@ -67,11 +83,14 @@ diff -ur git.org/pi-blaster.boot.sh
[2] git/pi-blaster.boot.sh [3]
>> - log_end_msg 1
>> - ;;
>> - esac
>>
-+ do_start
>> ++ do_start
>> ;;
>> *)
>> - echo "Usage: $SCRIPTNAME
{start|stop|status|restart|force-reload}" >&2
>> -+ echo "Usage:
$SCRIPTNAME {start|stop|restart}" >&2
>> ++ echo "Usage: $SCRIPTNAME
{start|stop|restart|force-reload}" >&2
>> exit 3
>> ;;
>> esac
>> +--
>>
+1.9.1
>> +
>> diff --git a/recipes-devtools/pi-blaster/pi-blaster.inc
b/recipes-devtools/pi-blaster/pi-blaster.inc
>> index a3beccc..a548957
100644
>> --- a/recipes-devtools/pi-blaster/pi-blaster.inc
>> +++
b/recipes-devtools/pi-blaster/pi-blaster.inc
>> @@ -2,7 +2,7 @@
DESCRIPTION = "This project enables PWM on the GPIO pins you request of
a Raspbe
>> HOMEPAGE = "https://github.com/sarfata/pi-blaster/ [4]"
>>
SECTION = "devel/libs"
>> LICENSE = "MIT"
>> -LIC_FILES_CHKSUM =
"file://README.md;beginline=157;endline=170;md5=f20832f31126609af5a7bf2340014540"
>>
+LIC_FILES_CHKSUM =
"file://README.md;beginline=212;endline=239;md5=a012868ef5f83b9f257af253d7cb07a3"
>

> What changed here ?

The license is added in the end of the
README.md so in this case some additional description + modifications
earlier in the README.md caused the license text to move place. When it
comes to the license text I could only find changes in whitespace and
newlines. They seems to have been caused by the pi-blaster commit:
'0e1a1df Cleaning up the README' 

BR Petter 

$ diff -Naur
ec5e1b4c.README.md README.md | tail -n 38

 ## License

 Released under
The MIT License.

-Note: This project was initially released by Richard
Hist under the GPL v3 License. Richard gave me explicit permission to
distribute this derivative work under the MIT License.
+Note: This
project was initially released by Richard Hist under the GPL
v3
+License. Richard gave me explicit permission to distribute this
derivative work
+under the MIT License.

 Copyright (c) 2013 Thomas
Sarlandie - Richard Hirst

- Permission is hereby granted, free of
charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without
restriction, including without limitation

Re: [yocto] [meta-raspberrypi][PATCH] pi-blaster: update to include proper rpi3 support

2017-06-07 Thread Khem Raj 
On Wed, Jun 7, 2017 at 9:09 PM, Petter Mabäcker  wrote:
> 2017-06-08 00:54 skrev Khem Raj:
>
>
> On Wed, Jun 7, 2017 at 2:17 PM Petter Mabäcker  wrote:
>>
>> Update to latest available revision, in order to include proper rpi3
>> support as well as latest fixes.
>>
>> Signed-off-by: Petter Mabäcker 
>> ---
>>  .../files/remove-initscript-lsb-dependency.patch   | 37
>> --
>>  recipes-devtools/pi-blaster/pi-blaster.inc |  2 +-
>>  recipes-devtools/pi-blaster/pi-blaster_git.bb  |  2 +-
>>  3 files changed, 30 insertions(+), 11 deletions(-)
>>
>> diff --git
>> a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>> b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>> index 7ea9a3b..c8afe60 100644
>> ---
>> a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>> +++
>> b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>> @@ -1,13 +1,28 @@
>> -Remove dependencies on LSB functions
>> +From 1338f98a279616f4e5e9ea30a25d1dfa0c7df5d6 Mon Sep 17 00:00:00 2001
>> +From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
>> +Date: Sun, 4 Jun 2017 12:22:40 +0200
>> +Subject: [PATCH] Remove dependencies on LSB functions
>> +MIME-Version: 1.0
>> +Content-Type: text/plain; charset=UTF-8
>> +Content-Transfer-Encoding: 8bit
>> +
>> +See this as a rebase of the previous 'Remove dependencies on LSB
>> +functions patch' with only minor modifications from the original version,
>> +based on the work done by Alex Lennon  in
>> +'25fd817 pi-blaster: Added recipe'.
>>
>>  Upstream-Status: Inappropriate [configuration]
>>
>> -Signed-off-by: Alex Lennon 
>> +Signed-off-by: Petter Mabäcker 
>> +---
>> + debian/pi-blaster.init | 38 +++---
>> + 1 file changed, 7 insertions(+), 31 deletions(-)
>>
>> -diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
>>  git.org/pi-blaster.boot.sh 2014-05-20 14:49:44.378582168 +0100
>> -+++ git/pi-blaster.boot.sh 2014-05-20 14:51:08.330582386 +0100
>> -@@ -28,12 +28,12 @@
>> +diff --git a/debian/pi-blaster.init b/debian/pi-blaster.init
>> +index b142d70..01a686c 100644
>> +--- a/debian/pi-blaster.init
>>  b/debian/pi-blaster.init
>> +@@ -28,12 +28,12 @@ SCRIPTNAME=/etc/init.d/$NAME
>>   [ -r /etc/default/$NAME ] && . /etc/default/$NAME
>>
>>   # Load the VERBOSE setting and other rcS variables
>> @@ -22,7 +37,7 @@ diff -ur git.org/pi-blaster.boot.sh
>> git/pi-blaster.boot.sh
>>
>>   #
>>   # Function that starts the daemon/service
>> -@@ -77,48 +77,23 @@
>> +@@ -77,48 +77,24 @@ do_stop()
>>
>>   case "$1" in
>> start)
>> @@ -52,6 +67,7 @@ diff -ur git.org/pi-blaster.boot.sh
>> git/pi-blaster.boot.sh
>> # 'force-reload' alias
>> #
>>  -  log_daemon_msg "Restarting $DESC" "$NAME"
>> ++  echo "Restarting $DESC" "$NAME"
>> do_stop
>>  -  case "$?" in
>>  -0|1)
>> @@ -67,11 +83,14 @@ diff -ur git.org/pi-blaster.boot.sh
>> git/pi-blaster.boot.sh
>>  -  log_end_msg 1
>>  -  ;;
>>  -  esac
>> -+  do_start
>> ++do_start
>> ;;
>> *)
>>  -  echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}"
>> >&2
>> -+  echo "Usage: $SCRIPTNAME {start|stop|restart}" >&2
>> ++  echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload}" >&2
>> exit 3
>> ;;
>>   esac
>> +--
>> +1.9.1
>> +
>> diff --git a/recipes-devtools/pi-blaster/pi-blaster.inc
>> b/recipes-devtools/pi-blaster/pi-blaster.inc
>> index a3beccc..a548957 100644
>> --- a/recipes-devtools/pi-blaster/pi-blaster.inc
>> +++ b/recipes-devtools/pi-blaster/pi-blaster.inc
>> @@ -2,7 +2,7 @@ DESCRIPTION = "This project enables PWM on the GPIO pins
>> you request of a Raspbe
>>  HOMEPAGE = "https://github.com/sarfata/pi-blaster/";
>>  SECTION = "devel/libs"
>>  LICENSE = "MIT"
>> -LIC_FILES_CHKSUM =
>> "file://README.md;beginline=157;endline=170;md5=f20832f31126609af5a7bf2340014540"
>> +LIC_FILES_CHKSUM =
>> "file://README.md;beginline=212;endline=239;md5=a012868ef5f83b9f257af253d7cb07a3"
>
>
> What changed here ?
>
> The license is added in the end of the README.md so in this case some
> additional description + modifications earlier in the README.md caused the
> license text to move place. When it comes to the license text I could only
> find changes in whitespace and newlines. They seems to have been caused by
> the pi-blaster commit: '0e1a1df Cleaning up the README'
>
> BR Petter
>
> $ diff -Naur ec5e1b4c.README.md README.md | tail -n 38
>

perfect add few lines to the commit message about this

>  ## License
>
>  Released under The MIT License.
>
> -Note: This project was initially released by Richard Hist under the GPL v3
> License. Richard gave me explicit permission to distribute this derivative
> work under the MIT License.
> +Note: This project was initially released by Richard Hist under the GPL v3
> +License. Richard gave me explicit permission to distribute this derivati

Re: [yocto] Building boost-python

2017-06-07 Thread Tim Orling 
You should do what meta-ros did:
https://github.com/bmwcarit/meta-ros/blob/master/recipes-support/boost/boost_%25.bbappend


> On Jun 7, 2017, at 3:46 AM, Jakob Hasse 
>  wrote:
> 
> 
> 
>> On 07.06.2017 11:59, VanCutsem, Geoffroy wrote:
>> 
>>> -Original Message-
>>> From: yocto-boun...@yoctoproject.org [mailto:yocto-
>>> boun...@yoctoproject.org] On Behalf Of Jakob Hasse
>>> Sent: Wednesday, June 7, 2017 11:48 AM
>>> To: Yocto List 
>>> Subject: [yocto] Building boost-python
>>> 
>>> Hello,
>>> 
>>> One of my layers needs boost-python.
>>> When I try to build boost-python with bitbake, it complains:
>>> 
>>> ERROR: Nothing PROVIDES 'boost-python'
>>> 
>>> How can I fix this?
>>> Boost itself builds and I also included
>>> PACKAGECONFIG_pn_boost = "python"
>>> without any effect.
>> I believe the correct spelling is:
>> PACKAGECONFIG_pn-boost = "python"
>> (note the hyphen instead of underscore)
> Yes, I saw it somewhere else now with a hyphen, too, but even with the 
> corrected local.conf, the problem still remains.
> Bitbake quits with the same error message as before
>> 
>>> My bblayers.conf is here:
>>> 
>>> # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf #
>>> changes incompatibly LCONF_VERSION = "6"
>>> 
>>> BBPATH = "${TOPDIR}"
>>> BBFILES ?= ""
>>> 
>>> BBLAYERS ?= " \
>>>/usr/local/dey-2.0/sources/poky/meta \
>>>/usr/local/dey-2.0/sources/poky/meta-yocto \
>>>/usr/local/dey-2.0/sources/poky/meta-yocto-bsp \
>>>/usr/local/dey-2.0/sources/meta-openembedded/meta-oe \
>>>/usr/local/dey-2.0/sources/meta-openembedded/meta-python \
>>> /usr/local/dey-2.0/sources/meta-openembedded/meta-networking \
>>> /usr/local/dey-2.0/sources/meta-openembedded/meta-webserver \
>>>/usr/local/dey-2.0/sources/meta-qt5 \
>>>/usr/local/dey-2.0/sources/meta-swupdate \
>>>/usr/local/dey-2.0/sources/meta-fsl-arm \
>>>/usr/local/dey-2.0/sources/meta-fsl-demos \
>>>/usr/local/dey-2.0/sources/meta-digi/meta-digi-arm \
>>>/usr/local/dey-2.0/sources/meta-digi/meta-digi-dey \
>>>/usr/local/dey-2.0/sources/meta-java/ \
>>>/usr/local/dey-2.0/sources/meta-iot-cloud/ \
>>> 
>>>"
>>> BBLAYERS_NON_REMOVABLE ?= " \
>>>/usr/local/dey-2.0/sources/poky/meta \
>>>/usr/local/dey-2.0/sources/poky/meta-yocto \
>>>"
>>> 
>>> Any help is welcome!
>>> Jakob
>>> 
>>> --
>>> Jakob Hasse
>>> Software Developement
>>> 
>>> E: jakob.ha...@smart-home-technology.ch
>>> T: +41 44 552 02 66
>>> 
>>> Smart Home Technology GmbH
>>> www.smart-home-technology.ch
>>> 
>>> --
>>> ___
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
> 
> -- 
> Jakob Hasse
> Software Developement
> 
> E: jakob.ha...@smart-home-technology.ch
> T: +41 44 552 02 66
> 
> Smart Home Technology GmbH
> www.smart-home-technology.ch
> 
> -- 
> ___
> 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] dllmap config for a Mono app

2017-06-07 Thread Craig McQueen 
I have a Mono app that uses DllImport to load some functions from libraries. 
The app can't find the libraries unless I create a Mono config file containing 
dllmap lines to map the library's plain "DLL" name (e.g. "foo") to the real 
name of the .so file (e.g. "libfoo.so.4").

* What would be a good way in the .bb recipe to automatically create the 
required Mono config file? It would need to find the "real" names of the 
library files from the library(s) build output. So it would DEPENDS on the 
library(s).

* Is it better to create a local config file, or write it into 
/etc/mono/config? (My Mono app has the DllImports in a compiled DLL, and so far 
I've found that I need to create a local MyDll.dll.config file; making a 
MyApp.exe.config file doesn't work.)

* Alternatively, the Mono app can find the libraries if plain libfoo.so 
symbolic link to libfoo.so.4 exists in the rootfs. But this symbolic link 
normally is only in the libfoo-dev package, not the libfoo package. Is there 
some reasonable way to create and install the libfoo.so symbolic links on the 
rootfs?

-- 
Craig McQueen

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

[yocto] Python 3 internal package dependencies

2017-06-07 Thread Craig McQueen 
I found that the Python 3 internal package dependencies are incompletely 
specified. For example, I wanted to install python3-asyncio for my Python 
program to use. But when I tried to run it, it was missing some other Python 3 
packages that asyncio depended on. I ended up making a Python 3 bbappend file 
with the following:

RDEPENDS_${PN}-asyncio += "${PN}-selectors"
RDEPENDS_${PN}-misc += "${PN}-multiprocessing"
RDEPENDS_${PN}-io += "${PN}-shell"
RDEPENDS_${PN}-shell += "${PN}-compression"

This just solved my immediate needs; I'm sure it's incomplete.

Is it worth trying to improve the internal package RDEPENDS in the Python 3 
recipe, or is it better for recipes for Python apps to just manually list all 
the sub-dependencies as needed?

-- 
Craig McQueen

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