Changes between Version 51 and Version 52 of Video_Users_Guide

Timestamp:

May 17, 2012 9:03:47 AM (13 years ago)

Author:

ismangil

Comment:

--

Video_Users_Guide

@@ -97 +97 @@
 === Windows Desktop (Visual Studio) ===
 
-Visual Studio users will need to configure things manually as explained below.
-
-==== 1. Requirements ==== #win-reqs
-
-Windows requirements:
- 1. The components in [#reqdesk common requirements] above.
-    [[BR]]
-  Here are sample steps for building SDL, libx264, and ffmpeg:
-    a. SDL 1.3 comes with VS project settings, e.g: for VS2005 just open {{{VisualC\SDL_VS2005.sln}}} and build.
-    a. Get [http://www.mingw.org/wiki/MSYS MSYS|MinGW] for building libx264 and ffmpeg, and also its [http://www.mingw.org/wiki/InstallationHOWTOforMinGW gcc compiler suite]. Note:
-       - It is recommended to use gcc 4 or above to build ffmpeg.
-       - To avoid problems, put MSYS, libx264, and ffmpeg in folders that do not contain space, e.g: {{{C:\msys, C:\devlib\ffmpeg}}}.
-    a. libx264 (optional, if H264 is wanted), in MSYS console, as detailed in [#reqdesk common requirements].
-    a. ffmpeg, in MSYS console, as detailed in [#reqdesk common requirements].
-       - To use ffmpeg with VS, {{{inttypes.h}}} and {{{stdint.h}}} will be needed, check [http://ffmpeg.arrozcru.org/wiki/index.php?title=Inttypes.h here].
-       
- 2. !DirectShow SDK, included in Windows SDK. The minimum component required within the SDK is ''Windows Development Headers and Libraris'' and ''Samples''. As there are several versions of SDK we found they have different issues:
-   a. If you don't need Windows 7 features, the recommended SDK is [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ff6467e6-5bba-4bf5-b562-9199be864d29 Windows SDK Update for Windows Vista]. This is because it doesn't have [wiki:FAQ#vs2008 IP Helper API header bug].
-   a. If you need Windows 7 features then use [http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=6B6C21D2-2006-4AFA-9702-529FA782D63B Windows SDK for Windows 7 and .NET Framework 4] and follow the instructions on [wiki:FAQ#vs2008 fixing IP Helper API header bug]. Also if you are using Visual Studio 2005 then you will need to patch it using [http://support.microsoft.com/kb/949009/ MS Knowledge Base 949009]
-
-
-==== 2. Configure directories ====
-
-Configure Visual Studio directories:
- 1. Add include and library paths for the required components:
-    a. !DirectShow SDK
-    a. SDL
-    a. ffmpeg
- 2. ~~
-    Build Baseclasses sample and add the path to Visual Studio:
-    a. Look for the Baseclasses project, and add the include path to Visual Studio configuration. '''Important:''' the include path for the Baseclasses must be higher than Windows SDK include path.
-    a. In the property of the Baseclasses project, change the code generation to Multi-threaded Debug, instead of the default Multi-threaded DLL. 
-    a. Compile the baseclasses project in the samples, and add the resulting library to the path of Visual Studio configuration.
-    ~~
-
-    '''Update''': Baseclasses !DirectShow project is bundled in the package since 2.0 (see ticket #1276).
-
-==== 3. Configure Video Settings ====
-
-Add these to your {{{config_site.h}}}:
-
-{{{
-#define PJMEDIA_HAS_VIDEO               1
-#define PJMEDIA_HAS_FFMPEG              1
-#define PJMEDIA_VIDEO_DEV_HAS_SDL       1
-#define PJMEDIA_VIDEO_DEV_HAS_DSHOW     1
-}}}
-
-==== 4. Rebuild the Solution ====
-
-Once the build is successful, you will have '''pjsua''' executable containing video support. Additionally, you may want to build the [#vidgui GUI sample application] too.
-
+See [wiki:Getting-Started/Windows Getting Started for Windows] on building pjsip with video support.
 
 [[BR]]