All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Alex Kiernan <alex.kiernan@gmail.com>
Cc: Khem Raj <raj.khem@gmail.com>,
	OpenEmbedded Development mailing list
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] should "ntp-dev" package have header files in it, or not?
Date: Mon, 25 Oct 2021 11:11:02 -0400 (EDT)	[thread overview]
Message-ID: <d4e0285f-3053-e1a0-146-bf54410cb2a@crashcourse.ca> (raw)
In-Reply-To: <CAO5Uq5Tv+yfED2u7ygvCX1tBcKpnAgpVaiAPGg10uYnXBfEdsw@mail.gmail.com>

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?

rday


  reply	other threads:[~2021-10-25 15:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-24 12:51 should "ntp-dev" package have header files in it, or not? Robert P. J. Day
2021-10-24 17:15 ` [oe] " Khem Raj
2021-10-24 18:24   ` rpjday
2021-10-24 19:10   ` rpjday
2021-10-25 10:50   ` Robert P. J. Day
2021-10-25 14:49     ` Alex Kiernan
2021-10-25 15:11       ` Robert P. J. Day [this message]
2021-10-25 15:20         ` Alex Kiernan
2021-10-26 19:22         ` Alex Kiernan
2021-10-27  9:03           ` Robert P. J. Day
2021-10-27 15:55           ` Robert P. J. Day
2021-10-27 16:30             ` Alex Kiernan
2021-10-27 16:41               ` Robert P. J. Day

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d4e0285f-3053-e1a0-146-bf54410cb2a@crashcourse.ca \
    --to=rpjday@crashcourse.ca \
    --cc=alex.kiernan@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.