bombomby
commented
2 years ago Hi. VS2008 has super old compiler and it doesn't support nullptr. I'd recommend to upgrade your project to a more modern version. If that's not possible - you could just replace nullptr with 0 in the source code of optick to get it working. In order to solve linker problems you'll need to build x86 version of library and dll. Optick has deprecated x86 build a while ago, however you should be able to generate x86 solution with the following command:
cmake -H"." -B"build\cmake" -G "Visual Studio 15 2017 Win32"
After building 32-bit DLL you should be able to resolve the linker errors. Hope it helps.
DeVaughn97
Currently I am attempting to use Optick C++ Profiler to track the performance of some of my latest project builds. Visual Studio Version: Microsoft Visual Studio C++ 2008 Express Edition Initial issue adding Optick C++ Profiler to project: Null Pointer was missing due to Visual Studio version
To solve null pointer issue what I attempted to do: Download and add Boost C++to project to be able to use Null Pointers Add nullptr_emulation.h to use a null pointers for Optick and current project
Result: no longer seeing null pointer error
Current Issue: I'm confident that the null pointer issue is solved as I am no longer getting error's for it with my visual studio version however I am now getting Lnk2019 errors (check attached screenshot)
What I think the issue is: Currently for Optick C++ Profiler the Debug and Release folders are for x64 however due to the Visual Studio version I might need x86 Debug and Release version for Optick C++ Profiler if there are available
What's my question for this issue? What is the root cause for the Lnk2019 errors
Reason for Microsoft Visual C++ 2008 Express: Using Development Kit built for Microsoft Visual C++ 2008 Express "DarkGDK"
Below is my text file source
Moving Ball Source.txt