-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compile with Visual Studio 2015 on Windows 10 #17
Comments
Did you have soleved this issue? I also to run it, on windows. |
I did not resolve this issue and my project was closed. |
are you windows cuda ? |
Did you have compile this, success, in windows:
|
I also want to solved it ? Could you send me your all projection, let me have a try, include all External libraries? My email address is: [email protected] |
could you send me your compiled projection, let me foucus on the soleved main problem? I compile it, but so many compile errors.My email address is: [email protected] |
I am sorry that this project is in history now and I don't have anything left to provide. As far as I remember, I did not solve this issue and I turned to another framework called Ranger and eventually did not use Cuda. My project was about empowering random forest with genetic algorithms. You can see my repository for more information. |
Hello,
I understand this project has probably only been tested on Linux, but all the dependent libraries are also available on Windows and therefore I created a fork for this task. My environment is Visual Studio 2015 Win64 on Windows 10. I apply it to CMake commands and create VC projects. The main modification in code is to change path strings into type boost::filesystem::path::string_type for the sake that Boost uses self-defined string_type (equivalent to wide chars), instead of string, for path variables. My modified version can be successfully compiled, and I can generate curfil.lib. However, I cannot resolve the numerous linking errors while building curfil_train and curfil_predict. In general, there are only two types LNK2001 and LNK2019:
I don't think it is an OS-related issue, rather an incorrect setup for the linker. Here is the list of input for the linker:
I have been stuck for more than a week. I'd heartily appreciate it f anyone has an idea about this or has more knowledge about linking to share.
Cheers,
ifeng
The text was updated successfully, but these errors were encountered: