2018-06-01 8:46 GMT+03:00 Damien LEFEVRE <lefevre.da@...>: Make two separate recipes for the configuration, and list one, or the other in the image recipes. Alternatively, do the needed tweaks v

I have to say defining multiple distros and then tweaking recipes according to those definitions is not a good practice, as recipes should generally only access DISTRO_FEATURES and otherwise be distro

If a build is 'a single bitbake invocation', then yes - it builds for a single distro and for a specific target machine, but it can build multiple recipes (which includes multiple images, as images ar

2018-06-01 13:38 GMT+03:00 Alan Martinovic <alan.martinovic@...>: By applying code archaeology skills obviously, which are a must-have for anyone involved in Yocto :) Specifically here: where an

It probably goes to some log file? Alex

You start by defining 'works'. It can be anything from quickly building an image and booting it on the target hardware to see a login prompt, to running a massive test suite and achieving 100% pass ra

2018-06-14 7:02 GMT+03:00 Tim Hammer <tdhammer99@...>: Devtool should add newly added patches to the recipe in the same order as the commits you created in workdir repo. If that is not the case,

2018-06-15 2:11 GMT+03:00 Peter Kjellerstedt <peter.kjellerstedt@...>: Wait, what would be the correct thing for devtool to do here? The original patches are already added to the recipe in the or

2018-06-24 20:44 GMT+02:00 Selvaraj V <selvabe99@...>: We've had an open bug for it for a while, and I think Derek has done a bit of work, but it was half-done: https://bugzilla.yoctoproject.org

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 t

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 <timm@...>:

If the issue is that openssl is 'out of date', then oe-core already provides a 1.1 version that can be selected via PREFERRED_VERSION as well. What is the specific need for the 3rd party version? Alex

Just fix the build issue. Look into how opensslconf.h gets created and where the -32 suffix comes from and why the included file is absent. Seriously - that is less effort than trying to make Yocto do

The error message you've provided is caused by an openssl header referring to another header file that doesn't exist. It does not come from application code, but is due to openssl being incorrectly co

Ah, so are you attempting to build 32 bit apps against a 64 bit openssl from poky? I'd say you need to either enable multilib and build the apps against lib32-openssl: https://www.yoctoproject.org/doc

Yes. Implement a class and inherit it from the recipes. Alex 2018-07-10 20:50 GMT+02:00 Michael Habibi <mikehabibi@...>:

You probably need to do this for openssl 1.1 as well as it soon will be the default. Alex 2018-07-12 0:42 GMT+02:00 Juro Bystricky <juro.bystricky@...>:

You are building something that requires openssl 1.0 (most likely openssh, which is not compatible with 1.1). You have to exclude it from your builds first. Alex 2018-07-16 3:19 GMT+02:00 Russell Pete

2018-07-18 13:37 GMT+02:00 Zoran Stojsavljevic <zoran.stojsavljevic@...>: You are installing only the executable binary here, but not the corresponding library. Just remove the do_install functi

This page has a tip on what might be causing 'git ls-remote': https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_create_my_own_source_download_mirror_.3F Alex 2018-07-21 10:32 GMT+02:00 MOHAMMAD