Comments (13)
Not sure why I opted for 3.5 at the time, there is no specific reason that I can recall.
To use python 3.6 you will have to rebuild boost python with python 3.6. Having python 3.6 on path should be enough for cmake to use this version.
The easiest way would be to rebuild every dependency using caffe-builder and use the caffe-builder-config.cmake as a cache file as documented here: https://github.com/willyd/caffe-builder#using-the-built-libraries-in-your-project
As a side note, I started, some time ago, some work to port the dependency management to vcpkg to ease customization for every user. You can have a look at that if you are interested. Any help on that matter would be greatly appreciated.
from caffe-builder.
@Coderx7 Thanks. Next time I work on the vcpkg port I will try to document better what is left to be done.
from caffe-builder.
I suppose that some CMake target exposes it's dependency to the caffezlib library. Look for any reference to caffezlib in .cmake files generated by the dependencies. I tried to make the paths relative to the top level directory of the install of caffe-builder but I may have missed something somewhere.
from caffe-builder.
Thanks, I'll have a look,
By the way, having a quick simple look at your branches, it seemed to me it would be much more helpful if you could update your branches readmes, and give a description of what is complete and what is not and pretty much what is needed
from caffe-builder.
@Coderx7 thanks for your constructive comments.
By the way, having a quick simple look at your branches, it seemed to me it would be much more helpful if you could update your branches readmes, and give a description of what is complete and what is not and pretty much what is needed
Could you elaborate more on that? Are you talking about my caffe or caffe-builder branches? It is really hard to support every possible setup a developer might have and I have myself very limited time to dedicate to caffe-windows.
What kind of information are you missing?
from caffe-builder.
@willyd : I specifically meant https://github.com/willyd/vcpkg/tree/caffe
:
I need to know what is needed and see if I can, help in any way.
by the way I do know what you mean and I really appreciate all the hard work you have put on caffe-windows specifically.
Best Regards
from caffe-builder.
By the way I have added some batch files for the windows examples (downloading and running the examples), how do I submit a PR ( in case you think its a good idea) , Do I submit the whole branch or should I only submit the folders that I added some files to?
Here is the caffe-branch
from caffe-builder.
The smaller the PR the easier it is for me to review it. So more smaller PRs is a better idea than a huge single one. No sure how to create a PR from a repo that was not forked using the Fork button though.
from caffe-builder.
@willyd submitted a pr today :here is the link , I had to remove my older MS based repository and then re-fork Caffe and then submit my pr.
Please have a look.
from caffe-builder.
@willyd : Hi, I created the libraires successfully and everything seem to work at least on my PC, however when I tried to use the built libraries on a system other than the one by which I built the libraries , it gives me linker errors pointing to the lib files in the caffe-builder-master build directory!
I am getting erros like :
Why is this happening? How can I get around this?
by the way I have uploaded the libraries on my branch if you need a quick look, here it is
Update:
I noticed under share/pkgconfig there is a zlib.pc file which is the file that contains these address:
prefix=D:/CodingStuff/caffe-builder-master/build_v140_x64/libraries
exec_prefix=D:/CodingStuff/caffe-builder-master/build_v140_x64/libraries
libdir=D:/CodingStuff/caffe-builder-master/build_v140_x64/libraries/lib
sharedlibdir=D:/CodingStuff/caffe-builder-master/build_v140_x64/libraries/lib
includedir=D:/CodingStuff/caffe-builder-master/build_v140_x64/libraries/include
Name: zlib
Description: zlib compression library
Version: 1.2.8
Requires:
Libs: -L${libdir} -L${sharedlibdir} -lz
Cflags: -I${includedir}
The same file exists in your libraries as well, however, I have no idea why I'm facing such error!!
Any help is greatly appreciated
from caffe-builder.
I just noticed the last command in i.e. :
cmd> cd myproject
cmd> mkdir build
cmd> cd build
cmd> cmake -G <generator name> -C %caffe_builder_root%\caffe-builder\build\libraries\caffe-build-config.cmake
I dont remember executing this part! is it the reason I'm facing such errors? Anyway, I tried to run this like :
cmake -G "Visual Studio 14 2015" -C D:\CodingStuff\caffe-builder-master_\build_v140_x64_\libraries\caffe-builder-config.cmake
but faced a weird error :
loading initial cache file D:\CodingStuff\caffe-builder-master_\build_v140_x64_\libraries\caffe-builder-config.cmake
CMake Error: The source directory "D:/CodingStuff/caffe-builder-master_/build_v140_x64_/libraries/caffe-builder-config.cmake" is a file, not a directory.
Specify --help for usage, or press the help button on the CMake GUI.
What am I missing here?
from caffe-builder.
@willyd : That was it !, the culprit was in the hdf5-targets.cmake
. changed them to the relative path and bingo ;)
God bless you man 😉
from caffe-builder.
Hello @willyd @Coderx7, when i create libraires, i get this errors:
My envs:
win10
python3.5(not anaconda)
cuda10.0
cudnn7
vs2015
Ninja v1.9.0
So, how to solve the problem? Any help is greatly appreciated.
from caffe-builder.
Related Issues (20)
- download prebuilt dependencies failed
- How to make it support x86? HOT 2
- url download for hdf5 package has changed HOT 6
- After I SET the Matlab_DIR in FindMatlabMex.cmake anthoer mistake happen, this mistake border me 5days plz help me
- downloading protobuf fails with hash missmatch HOT 3
- ninja: error: caffezlibd.lib', needed by 'snappy_unittest.exe'
- boost minor problem: cannot find 'pyconfig.h' HOT 1
- nvcc.hpp(22): fatal error C1017: HOT 4
- fatal error LNK1181: 无法打开输入文件“gflags_shared.lib” HOT 1
- how to support cuda 9.0
- compiler erro
- Build with VTK
- Python 3.6 is not supported
- Caffe builder in Visual studio 2017 HOT 1
- ninja: build stopped: subcommand failed?
- Warning during caffe installation
- How can I stop always download new files and remove old file? HOT 1
- Hi, I want to know how to add an new layer type to caffe(python version)(install by anaconda)
- -- Selecting Windows SDK version to target Windows 10.0.19041. CMake Error at cmake/WindowsDownloadPrebuiltDependencies.cmake:40 (message): Could not find url for MSVC version = 1900 and Python version = 3.6. Call Stack (most recent call first): CMakeLists.txt:77 (include) HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from caffe-builder.