LNK2019 Error

[bipul-mohanto]

There are three linking errors, e.g.,

Severity Code Description Project File Line Suppression State
Error LNK2019 unresolved external symbol "__declspec(dllimport) class optix::Handle __cdecl sutil::createOutputBuffer(class optix::Handle,enum RTformat,unsigned int,unsigned int,bool)" (_imp?createOutputBuffer@sutil@@ya?AV?$Handle@VBufferObj@optix@@@Optix@@v?$Handle@VContextObj@optix@@@3@W4RTformat@@II_N@Z) referenced in function "private: void __cdecl PathTracer::init_buffers(void)" (?init_buffers@PathTracer@@AEAAXXZ) Foveated Rendering using Ray Tracing C:\Users\local-admin\Desktop\Foveated-Rendering-using-Ray-Tracing\Foveated Rendering using Ray Tracing\PathTracer.obj 1

could you please give any suggestion?

[ohseokkwon]

In my opinion, the LNK2019 error appears to be a function references failure. Same error as function name mismatch when using DLL. I recommended you perform a Build->Clean Solution and then Rebuild Solution in Visual Studio. If you still have the same problem, please send your comment again.

[bipul-mohanto]

Thank you @ohseokkwon , I have actually already tried that. But it did not work. To keep it simple, I have used visual studio 2015 (2017,2019 all have same linking problem), and the same OptiX version, and CUDA toolkit you used. I think the PathTracer file may be have the problem.

[bipul-mohanto]

Configuration Properties >> Linker >> Command Line >> add /WHOLEARCHIVE option to the Additional Options solved those three linker errors that lead to another linking error, ```LNK1000 Internal error during CImplib::EmitThunk´´´. To solve this, download and install the hotfix .exe file. Now that again leads to 288 Errors. However, finally I have solved all linking problem in another way. But it is now leading to exception error.

[ohseokkwon]

Did you build the Optix SDK?
After installing Optix, you need to build the SDK with Cmake.
This project is using the API of the Sutil library.
Then you need to modify the file path related to Sutil.

[bipul-mohanto]

Yes, I did that already. However, now stopped in this exception handling. However, building was successful