개미핥기님의 이글루

:: Abstract ::
This article explains the steps needed to successfully installing DirectShow SDK into Microsoft Windows on the desktop. It guides you all the way from obtaining and installing the required SDKs, to configuring the environment, and finally, building a DirectShow application to verify the installation of the SDK.

:: Prerequisite ::
The environment that this article was based on was Visual Studio 2005 with Microsoft XP SP2.

:: Directshow SDK Installation Steps ::
Step 1 - Obtaining the required SDKs
Assuming you already have Visual Studio 2005 in place, you now need to download two SDKs.

1.1 Obtain Windows Vista SDK
The first one is called Windows Vista SDK, this is where DirectShow SDK can be found. Don´t get fooled by its name, the SDK included supports in creating applications for Windows XP.
You can download Windows Vista SDK here.

1.2 Obtain DirectX SDK
The second SDK you’ll need is DirectX SDK. You need this since DirectShow uses DirectDraw to render its content onto the screen, and DirectDraw is part of DirectX SDK.
You can download the latest DirectX SDK as of today here.

Step 2 - Installing the Required SDKs
This step involves the installation of the two SDKs downloaded in step 1.

2.1 Install Windows Vista SDK
Install Windows Vista SDK to the default directory. To save storage space, i only installed the options which I believe is the absolute necessity as shown in the image below

Since I only want to develop my applications on native environment, I have diselected all options required for .net framework. I have deselected most of the developer tools as they are already part of Visual Studio 2005. At a bare minimum, you need to select “Windows Vista Headers and Libraries” since it is this option that contains the required SDK for DirectShow.

2.2 Install DirectX SDK
After Windows Vista SDK is done, you need to install DirectX SDK downloaded earlier. This step is straightforward as only the default options are needed to install the SDK into your system. So click next next next to install it.

2.3 Verify the Installed Directories
When DirectX SDK is done, you should have two directories, one for each of the SDKs. Provided that you have installed them to the default directory and have the same version as the one linked in this page, verify that you have

Program Files\Microsoft SDKs

and

C:\Program Files\Microsoft DirectX SDK (April 2007)

Step 3 - Configuring the Environment
This step involves the setting up of various environment variables and helping you import the necessary libraries in order to build your Directshow applications properly.

3.1 Set Up the Environment Variables
In order for Visual Studio’s build process to find the necessary header and library files to build your DirectShow application, you need to add those directories to Visual Studio’s directory search path.
Open Visual Studio 2005, go to

Tools -> Options -> Projects and Solutions -> VC++ Directories

3.1.1 Set Up Include Paths
Select “Win32″ platform and show directories for “Include files”. Add a new line and enter the path to your Windows Vista SDK’s include folder’s path,
which in my case is

C:\Program Files\Microsoft SDKs\Windows\v6.0\Include

Add another line to the include path for DirectX,
which in my case is

C:\Program Files\Microsoft DirectX SDK (April 2007)\Include

Add another line to the include path for BaseClasses,
which in my case is

C:\Program Files\Microsoft SDKs\Windows\v6.0\Samples\Multimedia\DirectShow\BaseClasses

Please double check the ordering.
Include path for BaseClasses should be at the top, then DirectX, then finally Windows Vista SDK.

3.1.2 Set Up Library Paths
Show directories for “Library files”. Repeat it with library folders for Windows Vista SDK and DirectX SDK, In my case is

C:\Program Files\Microsoft SDKs\Windows\v6.0\Lib

and

C:\Program Files\Microsoft DirectX SDK (April 2007)\Lib\x86

Make sure you have DirectX’s path on top else the compiler may choose those now outdated versions that come as part of the Windows Vista SDK.

3.2 Build the BaseClasses Sample
If you try to build the sample Directshow application (see the end of this document), you will receive these errors.

1>main.obj : error LNK2001: unresolved external symbol _IID_IMediaEvent
1>main.obj : error LNK2001: unresolved external symbol _IID_IMediaControl
1>main.obj : error LNK2001: unresolved external symbol _CLSID_FilterGraph
1>main.obj : error LNK2001: unresolved external symbol _IID_IGraphBuilder

The reason for this to happen is because these symbols were defined in

strmbase.lib for release
and
strmbasd.lib for debug

So intuitively, you need these two library files in order to build your application.

To generate these files, build

C:\Program Files\Microsoft SDKs\Windows\v6.0\Samples\Multimedia\DirectShow\BaseClasses

for both release and debug.
Copy both strmbase.lib (from release folder) and strmbasd.lib (from debug folder) to

C:\Program Files\Microsoft SDKs\Windows\v6.0\Lib

3.3 Link Your Application With the Required Library Files
To link with library files, open your DirectShow application project, go to

Project -> Properties -> Configuration Properties -> Linker -> Input

in “Additional Dependencies” field, fill in strmbase.lib for release configuration and strmbasd.lib for debug configuration.

An alternative approach, and my preferred approach, is to add the following code to the beginning of your code.

#if defined( _DEBUG )
#pragma comment( lib, "strmbasd" )
#else
#pragma comment( lib, "strmbase" )
#endif // _DEBUG


The main advantage of this approach is that the dependencies are put directly into the code, making it easier to share it without having the dependency on the project file.Please be aware that on your course of writing DirectShow applications, there will be a good chance that you will be faced with similar problem that symbols cannot be resolved. A general approach in solving this problem is to use a tool called “dumpbin.exe” located in your vc\bin directory.
By running the command

dumpbin /SYMBOLS strmbase.lib > output.txt

i can see that _IID_IMediaControl, _IID_IMediaEvent, and _CLSID_FilterGraph are all defined in .rdata section of the library file. You can use this approach to look inside which library files contain the definition of the symbol you want to use.

The library files you will likely to use are
dmoguids.lib
strmiids.lib
strmbase.lib

Step 4 - Verify Your Installation
Verify your installation by building and running this VS2005 solution.

If everything goes well, you should see and hear clock.avi rendered to your screen and speaker.