[quote=“1vanK”]> Also I have tried to install VS2015 without Update 1. Then I couldn’t open Urho3D solution at all, i got error like this - “this project is incompatible with this version of visual studio 2015”.
u need remove build dir and cmake again with another version of VS[/quote]
Ok, i will try it.
I think there was my stupid mistake, I simply forgot run cmake for another version of VS.
Before you jump to that conclusion, it may be worth a try to build the nanodbc library as a standlone using its own build system. Things were much simpler last year when we first integrate nanodbc library into Urho3D. Now it seems the project has acquired some traction and contributions from other devs. In the past their CMakeLists.txt (or they didn’t have one before, cannot remember now) was simpler, and we actually just use our own version of the CMakeLists.txt calling our own macros. That CMakeLists.txt has not been updated much since then. Thus, I won’t rule out the possibility that the root cause of your problem is with us (with our integration). Best is if you could ascertain the root cause before filing a bug to any of the project, if possible.
Could you retry again. I have attempted a fix by re implementing the VS2015 workaround for the linker error. IMHO, this is a regression issue on nanodbc side. i.e. their workaround code was overwritten by subsequent enhancement. After you have verified that the fix works (connection to database and query a field with text conversion, etc) then probably I can submit my patch to nanodbc upstream. Thanks.
Yes, they are totally different issue. As for your 64-bit VS issue, I thought I have explained it in that thread. It is how CMake generator for VS works and there is nothing we can help it. It happens to any VS, not just VS2015. The key things to remember:
[ol][li]CMake does not allow changes of compiler and/or generator after the build tree has been generated.[/li]
[li]CMake has different generators for 32-bit and 64-bit for each version of VS because MSVC compiler is not multilib-capable.[/li][/ol]
If you use cmake-gui all the way then when CMake prompted to choose a generator to use, choose one carefully. If you use CMake CLI all the way then pass the URHO3D_64BIT build option properly during the initial configuration. Changing this cache value after the fact is asking for trouble when using VS.
That’s too bad. Until you can confirm everything is working fine, I think I will hold to submit my patch upstream. Do let me know if @lexicalunit has fixed your other issue and I will make another pull afterwards.