1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--Converted with LaTeX2HTML 2002-2-1 (1.70)
original version by: Nikos Drakos, CBLU, University of Leeds
* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
* with significant contributions from:
Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
<HTML>
<HEAD>
<TITLE>Layout of Generated Files</TITLE>
<META NAME="description" CONTENT="Layout of Generated Files">
<META NAME="keywords" CONTENT="users_guide">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<META NAME="Generator" CONTENT="LaTeX2HTML v2002-2-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="users_guide.css">
<LINK REL="next" HREF="node189.html">
<LINK REL="previous" HREF="node187.html">
<LINK REL="up" HREF="node187.html">
<LINK REL="next" HREF="node189.html">
</HEAD>
<BODY >
<DIV CLASS="navigation"><!--Navigation Panel-->
<A NAME="tex2html3536"
HREF="node189.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html3530"
HREF="node187.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html3524"
HREF="node187.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html3532"
HREF="node14.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html3534"
HREF="node317.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html3537"
HREF="node189.html">Grouping compiled assets into</A>
<B> Up:</B> <A NAME="tex2html3531"
HREF="node187.html">Building Portable Polyglot Software</A>
<B> Previous:</B> <A NAME="tex2html3525"
HREF="node187.html">Building Portable Polyglot Software</A>
<B> <A NAME="tex2html3533"
HREF="node14.html">Contents</A></B>
<B> <A NAME="tex2html3535"
HREF="node317.html">Index</A></B>
<BR>
<BR></DIV>
<!--End of Navigation Panel-->
<H1><A NAME="SECTION04110000000000000000"></A><A NAME="s:filelayout"></A><A NAME="11135"></A>
<BR>
Layout of Generated Files
</H1>
Babel generates a lot of files. Many of these files you never have to
look at in an editor, but they must all be compiled and properly linked
into an application (see Section <A HREF="node189.html#s:libgrouping">14.2</A>).
In this section we discuss a host of flags that can affect where
files get generated.
<UL>
<LI><TT><B><code>--</code>output-directory<code>=</code></B></TT><I CLASS="sans"><I CLASS="slanted">path</I></I>
<BR>
This sets the root directory of where your files will be generated.
The path can be absolute, or relative to the current working directory.
<P>
</LI>
<LI><TT><B><code>--</code>generate-subdirs</B></TT>
<BR>
This option forces files to be laid out in a directory hierarchy
following the package hierarchy in the SIDL file. This arrangement
is required for the Java and Python languages, so those generators
force this option on and allow no means to turn it off.
For C/C++ and Fortran 77/90, the default is that all files be
generated in the single output directory with no package-named
subdirectories.
<P>
</LI>
<LI><TT><B><code>--</code>language-subdir</B></TT>
<BR>
This option was contributed by a user. This option appends a
language-specific subdirectory (e.g. c, python, f77) to the end
of the path.
<P>
</LI>
<LI><TT><B><code>--</code>hide-glue</B></TT>
<BR>
This option was contributed by a user. The intent here is to separate
the Impl files (which must be modified) from all other files.
If this flag is set, then wherever an Impl file gets generated,
all the corresponding Skels, Stubs, IORs, etc get generated in
a subdirectory named <code>glue</code>.
</LI>
</UL>
<P>
Arbitrary combinations of the above flags are allowed. Regardless
of the order they appear in the commandline, they are applied to the
resulting path in the order they are presented above. For example
if a SIDL file <TT>pkg.sidl</TT> defines a <TT><I CLASS="slanted">Cls</I></TT> class in the <TT><I CLASS="slanted">pkg</I></TT> package,
and the user runs Babel as follows:
<BLOCKQUOTE>
<TT> <TT>%</TT> <TT><B>babel -lugo there -sc</B></TT>
<BR>
</TT></BLOCKQUOTE>Then the majority of the sources will be generated in the <TT>there/pkg/c/glue/</TT> directory
(except the Impl files which will occur one directory up in <TT>there/pkg/c/</TT>).
Note the use of equivalent short-form commands in this example.
If readers wish to review long and short forms of command line arguments,
see Tabel <A HREF="node39.html#tbl:basics_commandline_args">3.1</A> on page <A HREF="node39.html#tbl:basics_commandline_args"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>.
<P>
Note that many of these options were contributed by users and are not
employed in Babel's own build. Instead, we tend to put a SIDL file in
a directory and then generate client-side or server-side bindings in in
either <TT>runXXX/</TT> or <TT>libXXX/</TT> subdirectories, respectively (where <TT>XXX</TT>
is a language name).
We don't use the <TT><B><code>--</code>generate-subdirs</B></TT> or <TT><B><code>--</code>hide-glue</B></TT>
flags because they place source files that belong in the same library in different
directories. Automake, which Babel uses as part of its build system, works much more
reliably when all the sources that go into a library appear in the same directory
as the library to be. The <TT><B><code>--</code>language-subdir</B></TT> has a similar effect
to what we do manually, but doesn't capture if it was client-side or server-side.
In our tests and demos, we tend to build these separately because we want to exercise
different drivers with different implementations.
<P>
<DIV CLASS="navigation"><HR>
<!--Navigation Panel-->
<A NAME="tex2html3536"
HREF="node189.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html3530"
HREF="node187.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html3524"
HREF="node187.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html3532"
HREF="node14.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html3534"
HREF="node317.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html3537"
HREF="node189.html">Grouping compiled assets into</A>
<B> Up:</B> <A NAME="tex2html3531"
HREF="node187.html">Building Portable Polyglot Software</A>
<B> Previous:</B> <A NAME="tex2html3525"
HREF="node187.html">Building Portable Polyglot Software</A>
<B> <A NAME="tex2html3533"
HREF="node14.html">Contents</A></B>
<B> <A NAME="tex2html3535"
HREF="node317.html">Index</A></B> </DIV>
<!--End of Navigation Panel-->
<ADDRESS>
<br><br>babel-0.10.2<br>users_guide Last Modified 2005-03-23<br><br><a href="http://www.llnl.gov/CASC/components">http://www.llnl.gov/CASC/components</a><br><a href="mailto:components@llnl.gov">components@llnl.gov</a>
</ADDRESS>
</BODY>
</HTML>
|
