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
|
<!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: NeXT Architectures</TITLE>
<META NAME="description" CONTENT="Crystal Space: NeXT Architectures">
<META NAME="keywords" CONTENT="Crystal Space: NeXT Architectures">
<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="SEC101"></A>
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_32.html#SEC100"> < </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_34.html#SEC102"> > </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_29.html#SEC91"> << </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_30.html#SEC98"> Up </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_37.html#SEC105"> >> </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <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>
<H4> 2.4.4.3 Architectures </H4>
<!--docid::SEC101::-->
<P>
This project may be built for any of the architectures which are supported by
the standard developer tools, as summarized below.
</P><P>
<BLOCKQUOTE>
<TABLE>
<TR><TD><EM>Platform</EM> </TD><TD> <EM>Architectures</EM> </TD><TD> <EM>Tested</EM></TD>
</TR>
<TR><TD>MacOS/X </TD><TD> <CODE>ppc</CODE> </TD><TD> <CODE>ppc</CODE></TD>
</TR>
<TR><TD>MacOS/X Server 1.0 </TD><TD> <CODE>i386 ppc</CODE> </TD><TD> <CODE>i386 ppc</CODE></TD>
</TR>
<TR><TD>OpenStep </TD><TD> <CODE>i386 m68k sparc</CODE> </TD><TD> <CODE>i386 m68k</CODE></TD>
</TR>
<TR><TD>NextStep </TD><TD> <CODE>i386 m68k sparc hppa</CODE> </TD><TD> <CODE>i386 m68k sparc</CODE></TD>
</TR></TABLE>
</BLOCKQUOTE>
<P>
Crystal Space and the supporting components may be built as multi-architecture
binaries (MAB), thus allowing a single executable file to be used on
multiple architectures.
</P><P>
When building Crystal Space and its components, multi-architecture binaries
are generated by specifying the standard Apple/NeXT makefile variable
`<SAMP>TARGET_ARCHS</SAMP>' on the command-line.
</P><P>
By using `<SAMP>TARGET_ARCHS</SAMP>', the desired architectures may be specified
during initial configuration of the build system. The chosen architectures
are remembered and automatically applied to all subsequent build operations,
unless manually overridden. If you do not specify `<SAMP>TARGET_ARCHS</SAMP>' at
configuration time, then the project will be compiled for the hardware on
which it is being built.
</P><P>
You can also override the configured choice of architectures by specifying
`<SAMP>TARGET_ARCHS</SAMP>' for a particular makefile target. For instance, to build
the `<TT>walktest</TT>' demonstration program as a MAB executable for Intel,
Motorola, and Sparc, one would type:
</P><P>
<TABLE><tr><td> </td><td class=example><pre>gnumake TARGET_ARCHS="i386 m68k sparc" walk
</pre></td></tr></table></P><P>
When building the supporting libraries (which do not understand
Apple/NeXT's `<SAMP>TARGET_ARCHS</SAMP>' makefile variable), multi-architecture
binaries are generated by specifying an alternate definition for `<SAMP>CC</SAMP>' on
the command-line. For instance, to build the JPEG library for Intel,
Motorola, and Sparc one would type:
</P><P>
<TABLE><tr><td> </td><td class=example><pre>make libjpeg.a CC="cc -arch i386 -arch m68k -arch sparc"
</pre></td></tr></table></P><P>
If `<SAMP>CC</SAMP>' is not specified then the library is compiled for the hardware on
which it is being built.
</P><P>
<A NAME="NeXT Libraries"></A>
<HR SIZE=1>
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_32.html#SEC100"> < </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_34.html#SEC102"> > </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_29.html#SEC91"> << </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_30.html#SEC98"> Up </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="cs_37.html#SEC105"> >> </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <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>
<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>
|
