On Thu, Sep 19, 2019 at 9:48 AM <Mikko.Rapeli@...> wrote:
One possibility is to provide these keys as host native tools and data to build of target recipes. This makes the files available in the build environment but does not expose them to target.
Create a -native recipe which has and installs the files and use via DEPENDS to the -native recipe.
Hope this helps,
-Mikko
Thank you. That feels like the better answer all around. Ultimately, that's where I was going, but hadn't thought of the fact that I only really need this data on my native build environment.
