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.flavor.html"><LINK
29 HREF="ref.if-define.html"></HEAD
40 SUMMARY="Header navigation table"
52 > Component Writer's Guide</TH
60 HREF="ref.flavor.html"
74 HREF="ref.if-define.html"
85 NAME="REF.HARDWARE"><SPAN
99 > -- Specify that a package is tied to specific hardware.</DIV
101 CLASS="REFSYNOPSISDIV"
113 >cdl_option <name> {
114 active_if <condition>
129 >Some packages such as device drivers and HAL packages are
130 hardware-specific, and generally it makes no sense to add such
131 packages to a configuration unless the corresponding hardware is
132 present on your target system. Typically hardware package selection
133 happens automatically when you select your target. The <SPAN
137 property can be used in the body of a <TT
141 indicate that the package is hardware-specific.</P
149 >At the time of writing the <SPAN
152 > property is largely ignored by
153 the configuration tools, but this may change in future. Amongst other
154 possible changes, for hardware-specific packages such as device
155 drivers and HAL packages, the current scheme of generating a
156 configuration header file name based purely on the package name may be
157 abandoned. Instead all hardware packages would send their
158 configuration data to a single header file, <TT
160 >pkgconf/hardware.h</TT
161 >. This would make it
162 easier for code to obtain details of the current hardware, but
163 obviously there are compatibility issues. For now it is recommended
164 that all hardware packages specify their configuration header file
183 CLASS="PROGRAMLISTING"
184 >cdl_package CYGPKG_HAL_ARM {
185 display "ARM architecture"
189 define_header hal_arm.h
205 HREF="ref.define-header.html"
212 HREF="ref.cdl-package.html"
224 SUMMARY="Footer navigation table"
235 HREF="ref.flavor.html"
244 HREF="cdl-guide.html"
253 HREF="ref.if-define.html"
272 HREF="reference.html"