1 <!-- Copyright (C) 2003 Red Hat, Inc. -->
2 <!-- This material may be distributed only subject to the terms -->
3 <!-- and conditions set forth in the Open Publication License, v1.0 -->
4 <!-- or later (the latest version is presently available at -->
5 <!-- http://www.opencontent.org/openpub/). -->
6 <!-- Distribution of the work or derivative of the work in any -->
7 <!-- standard (paper) book form is prohibited unless prior -->
8 <!-- permission is obtained from the copyright holder. -->
13 ><meta name="MSSmartTagsPreventParsing" content="TRUE">
16 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
19 TITLE="The eCos Component Writer's Guide"
20 HREF="cdl-guide.html"><LINK
22 TITLE="CDL Language Specification"
23 HREF="reference.html"><LINK
26 HREF="ref.implements.html"><LINK
29 HREF="ref.include-files.html"></HEAD
40 SUMMARY="Header navigation table"
52 > Component Writer's Guide</TH
60 HREF="ref.implements.html"
74 HREF="ref.include-files.html"
85 NAME="REF.INCLUDE-DIR"><SPAN
99 > -- Specify the desired location of a package's exported
100 header files in the install tree.</DIV
102 CLASS="REFSYNOPSISDIV"
114 >cdl_package <name> {
115 include_dir <sub-directory>
130 >Most packages export one or more header files defining their public
131 interface. For example the C library exports header files such as
140 If the package follows the <A
141 HREF="package.html#PACKAGE.HIERARCHY"
143 layout conventions</A
144 > then the exported header files will normally
145 be found in the package's
150 Alternatively the <SPAN
153 > property can be used to specify
154 which header files should be exported.</P
156 >By default a package's exported header files will be copied to
161 the install tree. This is correct for packages like the C library
162 because that is the correct location for files such as
166 >. However to reduce the
167 probability of name clashes it is desirable for packages to use
168 different sub-directories, for example infrastructure header files get
171 >include/cyg/infra</TT
173 rather than to the top-level
177 > directory itself.</P
179 >It would be possible to replicate these sub-directories in each
180 package's source tree, such that the infrastructure header file
184 >include/cyg/infra</TT
186 tree as well as in the install tree. This would make things more
187 difficult for the package developers. Instead it is possible to
188 specify the desired install tree sub-directory using an <SPAN
192 property, for example <TT
194 >include_dir cyg/infra</TT
200 > property can only be used in the body of a
204 > command, since it applies to all of the header files
205 exported by a package, and only one <SPAN
209 used. If there is no <SPAN
212 > property then exported header files
213 will end up in the top-level <TT
217 directory of the install tree.</P
233 CLASS="PROGRAMLISTING"
234 >cdl_package CYGPKG_INFRA {
235 display "Infrastructure"
236 include_dir cyg/infra
238 Common types and useful macros.
239 Tracing and assertion facilities.
240 Package startup options."
256 HREF="ref.include-files.html"
263 HREF="ref.cdl-package.html"
275 SUMMARY="Footer navigation table"
286 HREF="ref.implements.html"
295 HREF="cdl-guide.html"
304 HREF="ref.include-files.html"
323 HREF="reference.html"