Great. So when I have this recipe set up -- how do I make sure, or tell
other people who write a recipe depending on this -- how to find a header
file built by it?
Specifically, I see this header file in a (non-standard?) location which is
normally linked by others:
| #include <open62541.h>
and this header file is at ${B}/open62541.h
(tmp/work/aarch64-poky-linux/open62541/0.3-r0/build/open62541.h). Is this
something that I just handle with a `do_install_append()` line? The
documentation here
https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html isn't
very clear to me.
e.g. for another recipe that just adds "open62541" in it's DEPENDS.
Giordon
On Tue, Mar 6, 2018 at 2:32 PM Burton, Ross <ross.bur...@intel.com> wrote:
> On 6 March 2018 at 20:24, Giordon Stark <kra...@gmail.com> wrote:
>
>> You can drop the S assignment as that is the default value.
>>>
>>
>> Didn't realize, neat. I knew I needed to set it for `git` clones since it
>> always throws it into a ${WORKDIR}/git folder.
>>
>
> Yes, for git clones you need to override it.
>
>
>>
>>> Github /archive/ tarballs can and do change over time, which gets very
>>> annoying when you need to go and change the checksums.
>>>
>>
>> Really? Dang...
>>
>
> Yeah. :/ Took us ages to verify this happens but it definitely does.
>
>
>> My hunch without reading the upstream CMake files is that they don't
>>> support out-of-tree builds. If it worked from git then that's another
>>> reason to switch back.
>>>
>>
>> It seems like this is the case here. I'm ok using git clones for now.
>> Thanks.
>>
>
> It *shouldn't* matter here as the /archive/ tarball should have identical
> contents to a clone of the same tag, but it's possible that the build
> system looks for a .git/ directory and changes how it builds. That's kind
> of stupid but it wouldn't be the first time I've seen it break builds.
>
> Ross
>
--
Giordon Stark
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
