**** BEGIN LOGGING AT Sat Jul 07 03:00:00 2018
Jul 07 08:38:19 <timm1> I
Jul 07 08:38:59 <timm1> I'm currently trying to build a gutenprint recipe based on the recipe from buildroot: https://github.com/buildroot/buildroot/blob/master/package/gutenprint/gutenprint.mk
Jul 07 08:39:38 <timm1> one task I'm currently failing is that the makefile generates binary and the binary is executed to generate files
Jul 07 08:40:03 <timm1> I'm on a x86 platform and ARM code is generated
Jul 07 08:40:12 <timm1> so the binaries cannot be executed
Jul 07 08:41:19 <timm1> As far as I understand the gutenprint-native recipe will be responsible to generate the binaries which can be executed by x86
Jul 07 08:43:43 <timm1> So far I didn't manage that the gutenprint uses the result of gutenprint-native
Jul 07 08:44:22 <timm1> Is there any good sample/documentation about working with native/non native recipes?
Jul 07 09:40:19 <timm1> the program "extract-strings" has not to be cross compiled. The native compiled tool has to be used instead: https://github.com/FranciscoBorges/openwrt-printing-packages/blob/master/net/gutenprint/Makefile
Jul 07 09:41:11 <timm1> maybe I find the answer in the QT recipes as Qt requires a native version of qmake
Jul 07 11:10:59 <abelloni> timm1: DEPENDS = "gutenprint-native" should be enough to get the native programs in the sysroot when cross compiling
Jul 07 11:12:07 <abelloni> timm1: you can have a look at groff_1.22.3.bb
Jul 07 11:33:30 <timm1> abelloni: thanks :-)
Jul 07 14:08:47 <timm1> ${STAGING_BINDIR_NATIVE} is the binary path where I get the binary in non native build?
Jul 07 14:47:57 <khem> timm1: you dont need to specify path for accessing native tools it will already be preferred path
Jul 07 21:25:13 <timm1> the wifi firmware for rpi3b+ is the same as for rpi3b? i have read that the rpi3b+ uses the CYW43455 instead of brcm43430 for wifi.
Jul 07 23:59:20 <khem> timm1: its not same, there are some additional blobs it will install
**** ENDING LOGGING AT Sun Jul 08 03:00:00 2018