ViewVC Help
View File | Revision Log | Show Annotations | Root Listing
root/cvsroot/COMP/SCRAM/doc/html/export.html
Revision: 1.1.2.2
Committed: Wed Oct 20 09:04:39 1999 UTC (25 years, 7 months ago) by williamc
Content type: text/html
Branch: V0_9branch
Changes since 1.1.2.1: +13 -3 lines
Log Message:
Update export tag info - new autoexport=

File Contents

# User Rev Content
1 williamc 1.1 <! Style Sheet Header>
2     <html>
3     <head>
4     <title>SCRAM - Exporting Software Units</title>
5     <body>
6     <! End Style Sheet Header -----------Insert Text Here --------------------->
7     <h1>Exporting Software Units</h1>
8     <hr>
9     This section describes how to configure a software unit for use by other
10     software units. This interface then provides functionality to the
11     &lt;Use name=unit_name> tag specified elsewhere in the project.
12     <h2>Defining the Interface</h2>
13     The interface is defined in the BuildFile in the software unit. Anything
14     between <b>&lt;export></b> and <b>&lt;/export></b> tags will be
15     taken as defining the interface.<p>
16     <p>
17     e.g A BuildFile in a SubSystem called CARF.
18     <font color=green>
19     <pre>
20     &lt;export>
21     &lt;lib name=G3Main>
22     &lt;lib name=G3Event>
23     &lt;lib name=Reco>
24     &lt;lib name=G3SimEvent>
25     &lt;lib name=G3Interface>
26     &lt;/export>
27     </pre>
28     </font>
29     <p>
30     Any file that then wishes to use the subsytem CARF simply has to add the
31     following line to their BuildFile.
32     <font color=green>
33     <pre>
34     &lt;Use name=CARF>
35     </pre>
36     </font>
37     <p>
38     to get all the apporpriate CARF libraries.<p>
39 williamc 1.1.2.1 <h2>Package Application</h2>
40     By default the specifications between the &lt;export> tags do not propogate
41     down into the package. Thus a package will have to use a &lt;Use> tag to
42     get its own libraries. <p>
43     An alternative model (and the default before version 0_10_0) is to automatically
44     propogate the appropriate interface to each of its corresponding packages.
45 williamc 1.1.2.2 This can be done in the following ways
46     <ol><li>Specify in the &lt;export> tag. <p>
47     e.g.
48     <font color=green>
49     <pre>
50     &lt;export autoexport=true>
51     </pre>
52     <li>If this is to be the default behaviour then set
53 williamc 1.1.2.1 <pre>
54     scram_autoexport=true
55     </pre>
56 williamc 1.1.2.2 either in the project level BuildFile. This default can be overridden by
57     with <font color=green>
58     <pre>
59     &lt;export autoexport=false>
60     </pre>
61 williamc 1.1 <! Style Sheet Footer ---------------Do not change anything after this line-->
62     <hr>
63     <table border=1 width=100%>
64     <td align=left>
65     <a href=mailto:Christopher.Williams@cern.ch
66     >Chris Williams</a>
67     </td>
68     <td align=center>
69     <script language="JavaScript">
70     <!---//hide script from old browsers
71     document.write( "<br>Last updated "+ document.lastModified
72     );
73     //end hiding contents --->
74     </script>
75     </td>
76     <td align=right>Show <a href=/cgi-cmc/pagestat>Stats</a>
77     </td>
78     </table>
79     </body> </html>
80     <! End Style Sheet Footer>