1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE>Compiler Requirements for Building VP3 Library on Windows PC
</TITLE>
5 <META HTTP-EQUIV=
"Content-Type" CONTENT=
"text/html; charset=iso-8859-1">
6 <META NAME=
"GENERATOR" CONTENT=
"Mozilla/3.04Gold (Win95; I) [Netscape]">
8 <BODY LINK=
"#0000FF" VLINK=
"#800080" lang=
"EN-US" style=
"tab-interval:.5in">
10 <H1><A HREF=
"#_Building_VP3_Code_1">Building VP3 Code Modules on the PC
</A></H1>
12 <H1><A HREF=
"#_Building_VP3_Code">Building VP3 Code Modules on the MAC
</A></H1>
14 <H1><A HREF=
"#_Documentation">Getting Support
& Additional Documentation
</A></H1>
18 <H1>Building VP3 Code Modules on the PC
</H1>
20 <P><B><FONT SIZE=+
1>Prerequisite Steps:
<BR>
21 </FONT></B>To compile the VP3 code modules on windows PC, the following
22 compilers/software with proper configurations are required.
</P>
25 <LI><B>Microsoft Visual C++
6.0 (Visual Studio
6.0)
</B><BR>
29 <LI><B>Microsoft Visual Studio
6.0 Service Pack
4<BR>
30 </B>The installation of the Service Pack is required by the installation
31 of Microsoft Visual C++ Processor Pack (VCPP). The SP4 provides the support
32 to view the MMX and XMM registers in debug window.
<BR>
36 <LI><B>Microsoft Visual C++ Processor Pack (VCPP)
<BR>
37 </B>Its available at
<A HREF=
"http://msdn.microsoft.com/vstudio/downloads/ppack/default.asp">http://msdn.microsoft.com/vstudio/downloads/ppack/default.asp
</A>)
<BR>
38 <FONT SIZE=-
1>The Processor pack provides support for Intel and AMD’s newest
39 instruction sets on their newest processors in form of both C Intrinsic
40 and inline assembly code. However, the previous version of the Processor
41 Pack will generate “Internal Compiler Error” in compiling the VP3 library
42 with default optimization settings.
</FONT> <BR>
46 <LI><B>Macro File for Microsoft Macro Assembler for Intel
® Streaming
47 SIMD Extensions
</B> “iaxmm.inc”.
<BR>
48 Its available at:
<A HREF=
"http://developer.intel.com/vtune/macropak/download.htm">http://developer.intel.com/vtune/macropak/download.htm
</A>)
<BR>
49 Microsoft now includes the MASM compiler version
6.15, ML.exe and H2inc.exe,
50 as part of the processor pack, so a separate installation of MASM is not
51 required. However, the macro file for Intel
® Streaming SIMD Extensions
52 is required to compile assembly files( *.asm ) using SSE instructions.
54 The path to “iaxmm.inc” should be added to the settings of Visual studio
55 through “tools-
>options-
>directories-
>include”
<BR>
59 <LI><B>QuickTime for Windows SDK (
4.0 ,
5.x or
6.x).
</B> <BR>
60 Its available from
<A HREF=
"http://developer.apple.com/quicktime">http://developer.apple.com/quicktime
<BR>
61 </A>QuickTime requires entries to Executable, Include and Lib Paths as
64 <TABLE BORDER=
1 CELLSPACING=
0 >
66 <TD BGCOLOR=
"#E1FFFF">tools-
>options-
>directories
</TD>
68 <TD BGCOLOR=
"#E1FFFF">QuickTime SDK
directory
</TD>
74 <TD><I>CIncludes, ComponentIncludes
</I></TD>
80 <TD><I>libraries
</I></TD>
93 <LI><B>resource include files must be setup correctly for building the
94 quicktime codec
<BR>
95 </B><I>NT or Win2K
</I>: add a new environment variable ( to your autoexec.bat
96 on win98 or ME or to your system environment variables on NT, or
2000 :
<BR>
97 Rincludes = C:\qtwsdk\rincludes ( or wherever you have the rincludes
98 directory of the QuickTime SDK )
<BR>
99 <I>Other
</I>:
<I> </I>add the following to the custom build line of dxlqt_codec.r
<BR>
100 -i c:\qtwsdk\rincludes ( or wherever you have the rincludes directory of
101 the QuickTime SDK )
<BR>
106 <FONT SIZE=+
1>Build
Steps:
<BR>
107 </FONT>Once the system has been configured :
</P>
110 <LI>open the workspace \vp32\vp32.dsw using Microsoft Visual Studio
</LI>
112 <LI>select the video for windows codec project and then project\build
</LI>
114 <LI>register the vp31 fourCC with the resulting vfw dll (System specific
115 process, try using the .inf file).
</LI>
117 <LI>select the quicktime codec and then project\build
</LI>
119 <LI>move components to proper system directories.
<BR>
123 <H1><A NAME=
"_Building_VP3_Code"></A><B>Building VP3 Code Modules on the
126 <P><FONT SIZE=+
1>The Requirements for Building On2 VP3.2 Libraries on MacOS
127 9.1 and Below:
</FONT> </P>
130 <LI>You must use Codewarrior
5.3 or higher to build the libraries.
</LI>
132 <LI>You cannot build the VP3.2 libraries in Codewarrior
6.x.
</LI>
134 <LI>In Control Panels, Internet, Advanced, File
Mappings:
May
135 need to add entries for .s and .ash file extensions mapping both to TEXT
136 file type, CWIE
Creator.
</LI>
139 <P><FONT SIZE=+
1>The Requirements for Building On2 VP3.2 QuickTime Component
140 for MacOS
9.1 and Below:
</FONT> </P>
143 <LI>Codewarrior
5.3</LI>
145 <LI>Universal Interfaces
3.3.2 or higher.
</LI>
149 <FONT SIZE=+
1>The Requirements for Building MacOS X On2 VP3.2 QuickTime
150 Component:
</FONT> </P>
153 <LI>Codewarrior
8, patched to
8.3.
</LI>
157 <FONT SIZE=+
1>Once the system has been configured (MacOS
8.x/
9.x):
</FONT>
161 <LI>open the project \vp32\vp32.mcp using CodeWarrior
</LI>
163 <LI>select the vp32 target and then build the library
</LI>
165 <LI>open the project file \vp32\Codecs\quicktime\mac\VP3QTCodec.CW53.mcp
</LI>
167 <LI>select the quicktime codec and then build
</LI>
169 <LI>Drag codec to Extensions folder, reboot(see Notes).
<BR>
173 <P><FONT SIZE=+
1>Testing MacOS X QuickTime Codec:
</FONT> </P>
176 <LI>Login as administrator.
</LI>
178 <LI>Drag the component into /Library/Components
</LI>
180 <LI>Do NOT
attempt to move the file using cp and/or mv in the terminal,
181 cp and mv do not maintain resource forks.
</LI>
184 <P><FONT SIZE=+
1>Notes:
</FONT></P>
187 <LI>When testing on MacOS
8.x and
9.x, using Reinstaller to install the
188 component will allow you to test the component without rebooting.
</LI>
191 <H1><A NAME=
"_Documentation"></A>Getting Support
& Additional
194 <P>VP3 is being maintained by Xiph, Inc, as part of the Theora project. Go to
195 www.theora.org for more information..
</P>