File: cs_262.html

package info (click to toggle)
crystalspace 0.94-20020412-3
  • links: PTS
  • area: main
  • in suites: woody
  • size: 62,276 kB
  • ctags: 52,843
  • sloc: cpp: 274,783; ansic: 6,608; perl: 6,276; objc: 3,952; asm: 2,942; python: 2,354; php: 542; pascal: 530; sh: 430; makefile: 370; awk: 193
file content (151 lines) | stat: -rw-r--r-- 4,113 bytes parent folder | download
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
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- Created by texi2html 1.64 -->
<!-- 
Written by: Lionel Cons <Lionel.Cons@cern.ch> (original author)
            Karl Berry  <karl@freefriends.org>
            Olaf Bachmann <obachman@mathematik.uni-kl.de>
            and many others.
Maintained by: Olaf Bachmann <obachman@mathematik.uni-kl.de>
Send bugs and suggestions to <texi2html@mathematik.uni-kl.de>
 
-->
<HTML>
<HEAD>
<TITLE>Crystal Space: Dependencies</TITLE>

<META NAME="description" CONTENT="Crystal Space: Dependencies">
<META NAME="keywords" CONTENT="Crystal Space: Dependencies">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<META NAME="Generator" CONTENT="texi2html 1.64">

</HEAD>

<BODY LANG="" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#800080" ALINK="#FF0000">

<A NAME="SEC628"></A>
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_261.html#SEC627"> &lt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_263.html#SEC629"> &gt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_247.html#SEC611"> &lt;&lt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_246.html#SEC610"> Up </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_271.html#SEC637"> &gt;&gt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="index.html#SEC_Top">Top</A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_toc.html#SEC_Contents">Contents</A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_285.html#SEC711">Index</A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_abt.html#SEC_About"> ? </A>]</TD>
</TR></TABLE>
<HR SIZE=1>
<H2> 8.2 Dependencies </H2>
<!--docid::SEC628::-->
<P>

To make sure some parts of Crystal Space can be used by themselves, there is
a philosophy, about which parts of Crystal Space are allowed to use other
parts. You can think of the various modules as sitting on a specific level:
</P><P>

<EM>Note</EM>: This information may not be fully accurate at the time you read
this.  Crystal Space is moving toward a system of plug-in modules which
advertise pure, abstract interfaces which often imply much less dependency
than actually linking with a library.
</P><P>

<UL>
<LI>Level 1: <EM>Utility--Independant of CS</EM>
<P>

<UL>
<LI>
<CODE>libjpeg</CODE>
<LI>
<CODE>libpng</CODE>
<LI>
<CODE>zlib</CODE>
<LI>
<CODE>csgeom</CODE>
<LI>
<CODE>csutil</CODE>
</UL>
<P>

<LI>Level 2: <EM>Basics--Common Base of Various CS Parts</EM>
<P>

<UL>
<LI>
<CODE>cssys</CODE>
</UL>
<P>

<LI>Level 3: <EM>SCF--Various Interchangeable Plug-In Modules of CS</EM>
<P>

<UL>
<LI>
<CODE>video/canvas</CODE>
<LI>
<CODE>video/renderer</CODE>
<LI>
<CODE>network/driver</CODE>
<LI>
<CODE>sound/driver</CODE>
<LI>
<CODE>sound/renderer</CODE>
</UL>
<P>

<LI>Level 4: <EM>Engine--Binds Together Engines Components</EM>
<P>

<UL>
<LI>
<CODE>csengine</CODE>
<LI>
<CODE>csparser</CODE>
</UL>
<P>

<LI>Level 5: <EM>Support--Adds a Common Layer of Engine Abstraction</EM>
<P>

<UL>
<LI>
<CODE>csws</CODE>
<LI>
<CODE>csphyzik</CODE>
</UL>
<P>

<LI>Level 6: <EM>Application</EM>
<P>

<UL>
<LI>
<CODE>walktest</CODE>
<LI>
<CODE>metademo</CODE>
</UL>
</UL>
<P>

Every modules is only allowed to include headers from the same modules or from
lower levels.  So for example, `<TT>csengine</TT>' may include headers from
`<TT>csutil</TT>' but not from `<TT>csws</TT>' or `<TT>csparser</TT>'.
</P><P>

All communication between level 3 libraries happens through SCF
interfaces.  Those are defined in the `<TT>CS/include</TT>' directory.  That is
the <EM>only</EM> way to communicate on level 3.  `<TT>csengine</TT>' can use level
3 libraries only through SCF.
<A NAME="Makefile How-To"></A>
<HR SIZE=1>
<BR>  
<FONT SIZE="-1">
This document was generated

using <A HREF="http://www.mathematik.uni-kl.de/~obachman/Texi2html
"><I>texi2html</I></A>

</BODY>
</HTML>