[转载]Windows部署Caffe-Backup Best Guidence

Caffe + vs2013 + OpenCV in Windows Tutorial (I) – Setup

Posted on July 15, 2015 by Neil Z. Shao

The purpose of this series it to get caffe working in windows in the most quick and dirty way: I’ll provide 1) the modified file that can be compiled in windows right away; 2) the vs2013 project that I’m currently using. In short:

1. Install CUDA, Boost, OpenCV.
2. Download caffe code with vs2013 from GitHub.
3. Download 3ryparty.zip and unzip to ‘3rdparty’ folder.
4. Edit ‘Caffe-vs2013 – Debug.props’ and ‘Caffe-vs2013 – Release.props’ files so that the path of CUDA, Boost and OpenCV make sense for you. Also, the given ‘compute_50,sm_50’ is for Maxwell GPU. Change 50 to 20 for Fermiand 30 for Kepler.
5. Open caffe-vs2013.sln.
6. Set platform to Release, x64 and change ‘caffe’ project’s ‘Configuration Type’ to ‘Application (.exe)’.
7. Right click on ‘caffe’ project and ‘compile’.
8. Run test on MNIST.

---

• For caffe.exe, please use Release|x64 mode. Debug version of caffe.exe makes no sense and is slow.
• 32 bit version should work but lacking support for lmdb and hdf5 because I didn’t compile them. lol

---

Setup:

1. CUDA 6.5
   • You have to have a Nvidia GPU on your PC to enable GPU version of Caffe. My impression was that you get maybe 10x speed-up using GPU over CPU, and another 10x speed-up by enable CuDNN library.
   • The installation will create system variable for you, e.g. CUDA_PATH_V6_5.
   • If you are using a GPU with the architecture of Fermi or Kepler: CUDA 6.5
   • If you are using a GeForce GTX9xx GPU with the architecture of Maxwell: CUDA 6.5 for Maxwell
   • Newer version of CUDA should be fine also.
2. Boost
   • Pre-built version of boost are available. I’m using boost 1.56.0 myself. Get pre-built boost and install.
   • Add boost’s path to system’s path. I added BOOST_1_56_0:
     • 
3. OpenCV
   • Since we are not using GPU supported OpenCV here, e.g. GpuMat, etc. Pre-built version of OpenCV are good enough for a quick start.
   • I use OpenCV 3.0 here as example. Add system path variable for OpenCV also:
     • 
4. System variable need ‘log off’ or ‘restart’ your system to take effect
5. Download the code for caffe from my GitHub
   • The original code was forded from 7e465f2. Then I manually added the changes from #1416 to support “vector<Mat>”.
6. Download the 3rdparty.zip and unzip its content to 3rdpary folder
   • 3rdparty.zip (Version 2015.7.18) [Google Drive] [360 YunPan (code:  6147)]
   • 3rdparty.zip (Version 2015.7.15)
   • Included is the support for gflags, glog, google/protobuf, hdf5, leveldb, liblmdb, openblas, cudnn, etc.

---

Before compile (skip if you’re familiar with vs2013 already):

• When it comes to a big project, many errors can happen. Let’s get things a bit clear first.
• In a project, usually functions are declared in .h/.hpp files and implemented in .c/.cpp files. Missing .hpp file is usually shown in the editor and missing .cpp file usually gives linking error.
• All .cpp files added to the vs project will be compiled to .obj files which can be linked later. While no .hpp files will be compiled. Adding .hpp files to the vs project or not makes no difference to the compiling.
• If you want to include .hpp file from another project, e.g. OpenCV. You need to add the path of the header files to ‘AdditionalIncludeDirectories’.
  • Adding header files to the vs project does NOT add the path automatically.
  • Adding the path of .cpp files to ‘AdditionalIncludeDirectories’ is NOT needed and has NO effect.
  • For example if the file path is “D:\toolkits\opencv-3.0.0\build\include\opencv2\opencv.hpp”, you can either:
    • 1) add “D:\toolkits\opencv-3.0.0\build\include” to ‘AdditionalIncludeDirectories’ and write #include “opencv2/opencv.hpp”; or
    • 2) add “D:\toolkits\opencv-3.0.0\build\include\opencv2” to ‘AdditionalIncludeDirectories’ and write #include “opencv.hpp”;
• After the .hpp file is included, the compiler knows that these functions exist so ‘unknown namespace cv’ kind of error will not happen any more.
• After all .cpp files in your project are compiled, here comes the linking. The implementation of functions have to be either in .cpp files of your project or .lib files generated by other projects.
  • Enabling lib files requires 1) path to be added to ‘AdditionalLibraryDirectories’; and 2) file names to be added to ‘AdditionalDependencies’.
  • For example, you might add “D:\toolkits\opencv-3.0.0\build\x86\vc12\lib” to ‘AdditionalLibraryDirectories’ and add “opencv_ts300.lib; opencv_world300.lib;” to ‘AdditionalDependencies’.
  • Usually the path of lib files changes according to the ‘PlatformTarget’, i.e. ‘x86’, and the ‘Configuration’, i.e. ‘Debug’. I usually let Visual Studio handle the difference, e.g. I add “$(OPENCV_3_0_0)\$(PlatformTarget)\vc12\lib” for OpenCV in later sections.
• If you solve compile error by having proper .hpp files and solve linking error by have proper .lib files, you program will run. Yet it might have missing .dll error.
  • Some library are compiled in the static way to generate .lib files only, like gflags, protobuf, etc.
  • Some library are compiled in the dynamic way to generate both .lib and .dll files. In this case your program will require .dll files on run-time.
  • Personally I like to copy required .dll files to the same folder of the .exe file for simplicity.