ITK Release 4/Video/HowToBuildVideoModules: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
(Created page with "Make sure you have the newer versions of OpenCV and VXl installed on your system with the following instructions: 1. Build OpenCV: We recommend to use opencv 2.4.2 or later. Ge...")
 
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
Make sure you have the newer versions of OpenCV and VXl installed on your system
There are five video modules in ITKv4 at the moment: Core, Filtering, IO, BridgeOpenCV and BridgeOpenVXL.
with the following instructions:


The first three modules(Core, Filtering and IO) do not depend on third party libraries.
By default (when ITK_BUILD_ALL_MODULES is ON), the three modules are included in the build tree.
However, if you want to use BridgeOpenCV and BridgeOpenVXL,  make sure you have the newer versions
of OpenCV and VXl installed on your system with the following instructions:
== Build BridgeOpenCV ==
1. Build OpenCV:
1. Build OpenCV:
We recommend to use opencv 2.4.2 or later.
We recommend to use opencv 2.4.2 or later.
Get the source code using Git:
Get the source code using Git:
git clone git@github.com:Itseez/opencv.git
        git clone git@github.com:Itseez/opencv.git
         git checkout 2.4.2
         git checkout 2.4.2
Use CMake to build opencv with the following configuration:
Use CMake to build opencv with the following configuration:
Line 13: Line 18:
         WITH_FFMPEG = ON
         WITH_FFMPEG = ON


2. Enable BridgeOpenCV module when configuring ITK in CMake:
        Module_ITKVideoBridgeOpenCV = ON (need to manually toggle this option ON)
Then, set system library Paths for OpenCV accordingly:
        OpenCV_DIR = <the path where you build the OpenCV>
       


2. Build VXL:     
 
        svn co https://vxl.svn.sourceforge.net/svnroot/vxl/trunk vxl
 
The revision number tested is 34805 ( 2012-04-23). Later version should work (but not tested).
== Build BridgeVXL ==
se CMake to build opencv with the following configuration:
1. Build VXL:     
        svn co https://vxl.svn.sourceforge.net/svnroot/vxl/trunk vxl
The revision number tested is 34805 ( 2012-04-23). Later version should work (not validated).
Use CMake to build opencv with the following configuration:
         BUILD_EXAMPLES = OFF
         BUILD_EXAMPLES = OFF
         BUILD_DOCUMENTATION = OFF
         BUILD_DOCUMENTATION = OFF
The minimum libraries needed in VXL configuration to build
ITKVideoBridgeVXL are:
        BUILD_CORE_VIDEO = ON
        BUILD_CORE_UTILITIES = ON (contains vil)
        BUILD_CORE_IMAGING = ON (contains vul)
        BUILD_CORE_NUMERICS = ON (contains vnl)
Also make sure you have FFMPEG installed that the following paths were found:
        FFMPEG_avcodec_LIBRARY
        FFMPEG_avformat_LIBRARY
        FFMPEG_avutil_LIBRARY
        FFMPEG_swscale_LIBRARY
2. Enable BridgeOpenVXL when configuring ITK in CMake:
        Module_ITKVideoBridgeVXL = ON  (need to manually toggle this option ON)
Then, set system library Paths for VXL accordingly :
        VXL_DIR = <the path where you build the VXL>




3. Enable Video modules when configure ITK in CMake:
== Dashboard submission ==
        Module_ITKVideoCore = ON (turn on by default)
Currently, there is a linux nightly dashboard submission in [http://open.cdash.org/index.php?project=Insight].
        Module_ITKVideoFiltering = ON (turn on by default)
Search for "Ubuntu-gcc-Release-Video" on the build name.
        Module_ITKVideoIO = ON (turn on by default)
        Module_ITKVideoBridgeOpenCV = ON (need to manually toggle this option ON)
        Module_ITKVideoBridgeVXL =ON  (need to manually toggle this option ON)
Then, set system library Paths for OpenCV and VXL accordingly:
        OpenCV_DIR = <the path where you build the OpenCV>
        VXL_DIR = <the path where you build the VXL>

Latest revision as of 16:08, 3 September 2013

There are five video modules in ITKv4 at the moment: Core, Filtering, IO, BridgeOpenCV and BridgeOpenVXL.

The first three modules(Core, Filtering and IO) do not depend on third party libraries. By default (when ITK_BUILD_ALL_MODULES is ON), the three modules are included in the build tree.

However, if you want to use BridgeOpenCV and BridgeOpenVXL, make sure you have the newer versions of OpenCV and VXl installed on your system with the following instructions:

Build BridgeOpenCV

1. Build OpenCV: We recommend to use opencv 2.4.2 or later. Get the source code using Git:

       git clone git@github.com:Itseez/opencv.git
       git checkout 2.4.2

Use CMake to build opencv with the following configuration:

       BUILD_EXAMPLES = OFF
       BUILD_TESTS = OFF
       WITH_FFMPEG = ON

2. Enable BridgeOpenCV module when configuring ITK in CMake:

        Module_ITKVideoBridgeOpenCV = ON (need to manually toggle this option ON)

Then, set system library Paths for OpenCV accordingly:

        OpenCV_DIR = <the path where you build the OpenCV>
        


Build BridgeVXL

1. Build VXL:

       svn co https://vxl.svn.sourceforge.net/svnroot/vxl/trunk vxl

The revision number tested is 34805 ( 2012-04-23). Later version should work (not validated). Use CMake to build opencv with the following configuration:

       BUILD_EXAMPLES = OFF
       BUILD_DOCUMENTATION = OFF

The minimum libraries needed in VXL configuration to build ITKVideoBridgeVXL are:

       BUILD_CORE_VIDEO = ON
       BUILD_CORE_UTILITIES = ON (contains vil)
       BUILD_CORE_IMAGING = ON (contains vul)
       BUILD_CORE_NUMERICS = ON (contains vnl)

Also make sure you have FFMPEG installed that the following paths were found:

       FFMPEG_avcodec_LIBRARY
       FFMPEG_avformat_LIBRARY
       FFMPEG_avutil_LIBRARY
       FFMPEG_swscale_LIBRARY

2. Enable BridgeOpenVXL when configuring ITK in CMake:

        Module_ITKVideoBridgeVXL = ON  (need to manually toggle this option ON)

Then, set system library Paths for VXL accordingly :

        VXL_DIR = <the path where you build the VXL>


Dashboard submission

Currently, there is a linux nightly dashboard submission in [1]. Search for "Ubuntu-gcc-Release-Video" on the build name.