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.legal-values.html"><LINK
29 HREF="ref.make.html"></HEAD
40 SUMMARY="Header navigation table"
52 > Component Writer's Guide</TH
60 HREF="ref.legal-values.html"
85 NAME="REF.LIBRARY"><SPAN
99 > -- Specify which library should contain the object files
100 generated by building this package.</DIV
102 CLASS="REFSYNOPSISDIV"
114 >cdl_package <name> {
115 library <library name>
130 >By default all object files that get built for all packages end up in
131 a single library, <TT
135 easier for the typical application developer because it is only
136 necessary to link with a single library, rather than with separate
137 libraries for each package. It is possible to specify an alternative
138 library for specific files as an option to the <SPAN
145 > properties, and there is one library <A
152 specific purpose in the build system. The <SPAN
156 alternative library to be specified for all the object files that will
157 be generated for a given package.</P
159 >The use of the <SPAN
162 > property should be avoided, since it makes
163 things more difficult for application developers. The property is
164 intended only for special cases, for example if there are legal
165 objections to mingling object files from different packages in a
166 single library. It could also be used to work around name clash
167 problems if two packages happen to define an exported symbol with the
168 same name, but any attempt to use multiple libraries in this way is
169 error-prone and should be avoided.</P
174 > property takes a single argument, the name of a library,
175 which should follow the standard naming convention of
178 >lib<something>.a</TT
183 only occur in the body of a <TT
186 > command and applies to all
187 object files generated for that package (except where explicitly
188 overwritten with a <TT
191 > option to one of the
192 build-related properties). A <TT
195 > body can contain at most
215 CLASS="PROGRAMLISTING"
216 >cdl_package <SOME_PACKAGE> {
218 library libSomePackage.a
233 HREF="ref.compile.html"
247 HREF="ref.make-object.html"
254 HREF="ref.cdl-package.html"
266 SUMMARY="Footer navigation table"
277 HREF="ref.legal-values.html"
286 HREF="cdl-guide.html"
314 HREF="reference.html"