Re: should "ntp-dev" package have header files in it, or not?


Robert P. J. Day
 

On Tue, 26 Oct 2021, Alex Kiernan wrote:

On Mon, Oct 25, 2021 at 4:11 PM Robert P. J. Day <rpjday@crashcourse.ca> wrote:

On Mon, 25 Oct 2021, Alex Kiernan wrote:

On Mon, Oct 25, 2021 at 11:51 AM Robert P. J. Day <rpjday@crashcourse.ca> wrote:

On Sun, 24 Oct 2021, Khem Raj wrote:

On Sun, Oct 24, 2021 at 5:51 AM Robert P. J. Day <rpjday@crashcourse.ca> wrote:


colleague recently asked me how to get access to one or more header
files associated with "ntp", so he could:

#include <ntp.h>

from some other code. casually, i suggested the standard way was to
add ntp to his recipe's DEPENDS, but that didn't do it, so i built ntp
in my own aarch64 project, then took a look under packages-split to
see what got packaged in ntp-dev, and was puzzled to see it was
absolutely empty.

is this deliberate? are other recipes not entitled to ntp's header
files? am i overlooking something?
While the header seems to be meant for public consumption, the build
explicitly does not export it, so perhaps thats not expected to be
used this way anymore.
just to tie this back to a question i once asked on (i believe) the
YP mailing list, this wind river build is using ntpsec instead of
regular ntp, but it would appear this would still have the same
problem -- while the ntpsec source contains an "include" directory
with lots of ntp-related header files, if one comes up with an ntpsec
recipe, nothing would be solved if it also does not install those
headers into ntpsec-dev.

so, simple question: does anyone have a bitbake recipe for current
ntpsec?
I do, it's unfinished as I realised part way through that the python
dependency meant it wasn't going to fit for my use case, but the
basics of the build are there.
so is there a link for this?
Have a look at this:

https://github.com/akiernan/meta-openembedded/commit/b1464c4b8dcab4a9dfaebbb7116b1c8462a198c4

Seems like it works for me. Will send a patch if it looks good.
setting up to test build right now: poky/aarch64/core-image-base.
will let you know. thank you kindly.

rday

Join openembedded-devel@lists.openembedded.org to automatically receive all group messages.