Open hesamfaraji opened 8 years ago
The reason should be the lack of 64bit libraries for boost, tbb and OpenCV which you will need to compile yourself. The compiler error should tell you which file in particular is having issues, don't forget you will need to change all the location of the lib files and their names if the x64 versions for them differ.
hi tadas. do you plan to migrate to x64 or provide both versions together? so one can simply switch between x64 and 32 in visual studio. for such flexibility you must use micros in build variables like $(platform). this way we can estimate performance in both versions.
I was thinking of trying the x64 version to see if it has any impact on performance and if it does I might include it in the later versions. The reason I did not consider including it initially was that the libraries take up quite a bit of space already and including both x86 and x64 might be a bit excessive.
Hi Tadas, Thanks for thanks for sharing your code.
I created a branch that builds on x64 and x86: https://github.com/lmurmann/CLM-framework/tree/x64build. In my case, I want to link CLM with an existing x64 project, and converting that project to x86 is not an option.
It is set up to build into directories like Release-x64, Debug-x86 and so on. Works on vs2013.
Awesome work, I'll have a look once I got the time. I'm slowly moving my code to vs2015 and adding support for x64, will have a look how you set it up and might borrow some ideas :)
Thanks, Tadas
in visual studio i changed target platform to x64. but every time i compile it says "Error LNK1112 module machine type 'X86' conflicts with target machine type 'x64' ". i think it is because of 32 bit versions of tbb and openVC binaries. i changed those but still no success.