public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: ylyuan <ylyuan.@davform.com>
Cc: ecos-discuss <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] about the location of package's  header file
Date: Fri, 12 Jan 2001 01:34:00 -0000	[thread overview]
Message-ID: <3A5ECF9E.809D1FE8@redhat.com> (raw)
In-Reply-To: <003801c07563$1e7a7d90$8664a8c0@yyl2000>

ylyuan wrote:
> 
> Hi,from the document I know that includ_dir specify the desired location of a package's exported header files in the install tree. So from the cdl
> hal_i386_pc.cdl,
>  cdl_package CYGPKG_HAL_I386_PC {
>     display  "i386 PC target"
>     parent        CYGPKG_HAL_I386
>     define_header hal_i386_pc.h
>     include_dir   cyg/hal
>     description   "
>            The i386 PC Target HAL package provides the
>            support needed to run eCos binaries on an i386 PC."
>     .....
> },
> I think the hal_i386_pc.h should locate in the include/cyg/hal,but in fact
> it in include/pkgconf.Why?
> Thanks a lot!

Configuration files (that go in include/pkgconf) are not the same as the
exported header files. Configuration header files are generated by the
configuration system and so live centrally in include/pkgconf.

Exported package header files go wherever include_dir says they should go.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine

      reply	other threads:[~2001-01-12  1:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-12  0:54 ylyuan
2001-01-12  1:34 ` Jonathan Larmour [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=3A5ECF9E.809D1FE8@redhat.com \
    --to=jlarmour@redhat.com \
    --cc="ylyuan."@davform.com \
    --cc=ecos-discuss@sourceware.cygnus.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 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).