Building VP3 Code Modules on the PC
Prerequisite Steps:
To compile the VP3 code modules on windows PC, the following
compilers/software with proper configurations are required.
- Microsoft Visual C++ 6.0 (Visual Studio 6.0)
- Microsoft Visual Studio 6.0 Service Pack 4
The installation of the Service Pack is required by the installation
of Microsoft Visual C++ Processor Pack (VCPP). The SP4 provides the support
to view the MMX and XMM registers in debug window.
- Microsoft Visual C++ Processor Pack (VCPP)
Its available at http://msdn.microsoft.com/vstudio/downloads/ppack/default.asp)
The Processor pack provides support for Intel and AMD’s newest
instruction sets on their newest processors in form of both C Intrinsic
and inline assembly code. However, the previous version of the Processor
Pack will generate “Internal Compiler Error” in compiling the VP3 library
with default optimization settings.
- Macro File for Microsoft Macro Assembler for Intel® Streaming
SIMD Extensions “iaxmm.inc”.
Its available at: http://developer.intel.com/vtune/macropak/download.htm)
Microsoft now includes the MASM compiler version 6.15, ML.exe and H2inc.exe,
as part of the processor pack, so a separate installation of MASM is not
required. However, the macro file for Intel® Streaming SIMD Extensions
is required to compile assembly files( *.asm ) using SSE instructions.
The path to “iaxmm.inc” should be added to the settings of Visual studio
through “tools->options->directories->include”
- QuickTime for Windows SDK (4.0 , 5.x or 6.x).
Its available from http://developer.apple.com/quicktime
QuickTime requires entries to Executable, Include and Lib Paths as
follows:
| tools->options->directories |
QuickTime SDK directory |
| include |
CIncludes, ComponentIncludes |
| libraries |
libraries |
| executables |
tools |
- resource include files must be setup correctly for building the
quicktime codec
NT or Win2K: add a new environment variable ( to your autoexec.bat
on win98 or ME or to your system environment variables on NT, or 2000 :
Rincludes = C:\qtwsdk\rincludes ( or wherever you have the rincludes
directory of the QuickTime SDK )
Other: add the following to the custom build line of dxlqt_codec.r
-i c:\qtwsdk\rincludes ( or wherever you have the rincludes directory of
the QuickTime SDK )
Build Steps:
Once the system has been configured :
- open the workspace \vp32\vp32.dsw using Microsoft Visual Studio
- select the video for windows codec project and then project\build
- register the vp31 fourCC with the resulting vfw dll (System specific
process, try using the .inf file).
- select the quicktime codec and then project\build
- move components to proper system directories.
Building VP3 Code Modules on the
MAC
The Requirements for Building On2 VP3.2 Libraries on MacOS
9.1 and Below:
- You must use Codewarrior 5.3 or higher to build the libraries.
- You cannot build the VP3.2 libraries in Codewarrior 6.x.
- In Control Panels, Internet, Advanced, File Mappings: May
need to add entries for .s and .ash file extensions mapping both to TEXT
file type, CWIE Creator.
The Requirements for Building On2 VP3.2 QuickTime Component
for MacOS 9.1 and Below:
- Codewarrior 5.3
- Universal Interfaces 3.3.2 or higher.
The Requirements for Building MacOS X On2 VP3.2 QuickTime
Component:
- Codewarrior 8, patched to 8.3.
Once the system has been configured (MacOS 8.x/9.x):
- open the project \vp32\vp32.mcp using CodeWarrior
- select the vp32 target and then build the library
- open the project file \vp32\Codecs\quicktime\mac\VP3QTCodec.CW53.mcp
- select the quicktime codec and then build
- Drag codec to Extensions folder, reboot(see Notes).
Testing MacOS X QuickTime Codec:
- Login as administrator.
- Drag the component into /Library/Components
- Do NOT attempt to move the file using cp and/or mv in the terminal,
cp and mv do not maintain resource forks.
Notes:
- When testing on MacOS 8.x and 9.x, using Reinstaller to install the
component will allow you to test the component without rebooting.
Getting Support & Additional
Documentation
VP3 is being maintained by Xiph, Inc, as part of the Theora project. Go to
www.theora.org for more information..