Open jackyko1991 opened 7 years ago
building with Gflags, Glog, LevelDB and Snappy is rather easy as well, under Windows VS2015 ... But remember you have to build only with MT Code generation option for all the 3rd part dependencies. Also, in order to make it work under python you will have to build ProtoBuf python source and add it to your PYTHONPATH. https://github.com/google/protobuf/releases/download/v3.2.0/protobuf-python-3.2.0.zip.
Also, it is recommended to use MKL for blas (for CPU purposes at least).
I am having a hard time achieving Good run times when using CUDA and CUDNN, has anybody managed to achieve good run time in that ? See performance evaluation i did: https://github.com/caffe2/caffe2/issues/921
@ugionet - how did you get gflags/glog/leveldb to build? Any time I deviate from the default settings (USE_GLOG OFF, USE_GFLAGS=OFF, USE_LEVELDB=OFF), I get thousands of linker errors. When you say "build only with MT Code generation" for all 3rd party dependencies, where do I specify that?
@ctraina I'm sure you've solved this problem by now, but you can configure options in VS.
In Solution Explorer, right click on project name and go to properties -> C/C++ -> Code Generation Change the option under 'Runtime Library'.
I have successfully build using MSVC 2015 with caffe 2. The installation instruction asks users to build with the .bat file in
caffe2/scripts
. However, I found this is not a good practice as sometimes we need use external dependencies. Configuring CMake with the GUI version would be much convenient under windows usage.In Caffe windows version it will automatically download all dependency required in forms of pre-built library. It would be good if users want to quickly deploy Caffe.
For whom want to build from source, or using specific version of third party library, the submodule file format in Caffe 2 will much do the favor. But problem comes in when in CMake configuration.
Here is a temporary solution to build with customized CMake:
One thing I think the development group should notify is in
operator_schema.h
line 288, std::bind to std::function conversion. Though building is successful, but type conversion is not properly defined.