If it's just a single simple binary that you need to run at build time
then you can build it manually in the target recipe before invoking
make.
The Pango recipe has an example of doing this.
Ross
On 7 July 2018 at 11:17, Alexander Kanavin wrote:
> How to do this is specific to each project. Ge
I do not recommend that you copy the binary over; it's better to clearly
separate native and target. Just patch the makefile.
Alex
2018-07-07 13:30 GMT+02:00 Timm :
> Am 07.07.2018 um 12:17 schrieb Alexander Kanavin:
>
> How to do this is specific to each project. Generally, you want the
> targe
Am 07.07.2018 um 12:17 schrieb Alexander Kanavin:
> How to do this is specific to each project. Generally, you want the
> target recipe to depend on the native recipe (so that the necessary
> native tools show up in the target sysroot),
Done that: gutenprint depends on gutenprint-native.
> and the
How to do this is specific to each project. Generally, you want the
target recipe to depend on the native recipe (so that the necessary
native tools show up in the target sysroot), and then you need to
study the build system of the upstream component project (makefiles
etc.) to see how it can be in
There was a gutenprint recipe back in OE-Classic:
https://layers.openembedded.org/layerindex/oe-classic/recipe/12076/
But currently there is no gutenprint available for Yocto.
I tried to build my own recipe. But I got stuck at the stage where the
build process wants to call some generated binarie
