Issues compiling with VS 2017 about daggergpuminer HOT 8 CLOSED

@HansOlavS I push a commit a while ago, so now you can use any directory for OpenCL SDK without changing project configuration.
"unresolved external symbol void __cdecl shamod::shasha..." Lol, thanks. I will fix it. Seems to be broken a day ago.
UPDATE: fixed.

from daggergpuminer.

Oh, I also changed the boost nuget packages from vc140 til vc141.

from daggergpuminer.

how to include the opencl sdk?
and openssl not found? New at VC, please give more advice how to include the required SDK and libs.. tthx

from daggergpuminer.

@HansOlavS it seems you have a problem with OpenSSL library. You can just turn off using OpenSSL. It is not so necessary. Just remove USE_OPENSSL_SHA from Preprocessor definitions.

from daggergpuminer.

@themaxx2k You have to download OpenCL SDK and install it to any directory, then create environment variable with name OPENCL_SDK and write the path to SDK in the value field.
By the way, I will upload compiled version tomorrow.

from daggergpuminer.

Thx @jonano614.

I'm still getting link errors, now for "unresolved external symbol void __cdecl shamod::shasha...".
What dir should OPENCL_SDK point to? The Program Files-dir or the local user SDK dir where libs and includes are.
I have these two locations:

• C:\Program Files (x86)\AMD APP SDK\3.0
• C:\Users\Hansol\AMD APP SDK\3.0

from daggergpuminer.

Was able to get it to compile when getting latest now.
But had to manually change all the vc140 refs to vc141 and also add include and libs directories for hand. I don't think this project runs very well on VS 2017 right now.

from daggergpuminer.

I am also experiencing a failed build in VS 2017- is the suggestion to use VS 2015?

from daggergpuminer.