public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: "libc-help@sourceware.org" <libc-help@sourceware.org>,
	Florian Weimer <fweimer@redhat.com>
Subject: Re: Question regarding headers to be exported
Date: Thu, 12 Nov 2020 08:11:06 +0000	[thread overview]
Message-ID: <20201112081106.GA8693@arm.com> (raw)
In-Reply-To: <20201110172705.455af5e5@jawa>

The 11/10/2020 17:27, Lukasz Majewski wrote:
> Dear Community,
> 
> Recently, I've been delving into Makefiles to understand the idea
> behind the way headers are exported (installed) on the target system.
> 
> There is sysdep_headers variable, which adds some files (like
> sys/timerfd.h, bits/shmlba.h) but also some files are exported when
> they are placed in the ./include/* directory (includedir variable).
> 
> One example is struct_timespec.h:
> 
> ./include/bits/types/struct_timespec.h -> here we just have #include to
> 					  exported one
> ./time/bits/types/struct_timespec.h
> 
> 
> I'm wondering why all exported files are not just added to
> "sysdep_headers" (or any other variable)?
> 
> Why do we have some indirection with "includedir" variable (and
> repetition of directory tree) ?

i'd expect sysdep_headers to be installed from
the sysdep directories (with a precedence order
based on current config)

and other headers are installed from generic
directories.

(but i havent checked the details)

> 
> Thanks in advance for the explanation.
> 
> 
> Best regards,
> 
> Lukasz Majewski
> 
> --
> 
> DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

      reply	other threads:[~2020-11-12  8:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 16:27 Lukasz Majewski
2020-11-12  8:11 ` Szabolcs Nagy [this message]

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=20201112081106.GA8693@arm.com \
    --to=szabolcs.nagy@arm.com \
    --cc=fweimer@redhat.com \
    --cc=libc-help@sourceware.org \
    --cc=lukma@denx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).