Hi all,

I've working on a simulation using Project Chrono - it's an old simulation 
that someone else completed in 2018 using a presumably older version of 
Chrono. I'm using Windows 11, Visual Studio 2022 and cmake to build the 
project, and using the most up-to-date version of Chrono to continue 
working on said project. 

When attempting to build the project, I'm getting linker errors 
(unrecognized external symbol) in Visual Studio Code, specifically:

LNK2019 unresolved external symbol "__declspec(dllimport) public: static 
void * __cdecl chrono::ChFrame<double>::operator new(unsigned __int64)" 
(__imp_??2?$ChFrame@N@chrono@@SAPEAX_K@Z) referenced in function "class 
std::shared_ptr<class chrono::ChBodyEasyBox> __cdecl 
chrono_types::make_shared<class chrono::ChBodyEasyBox,double &,double 
&,double &,double,bool,bool,class std::shared_ptr<class 
chrono::ChMaterialSurfaceSMC> &,0>(double &,double &,double &,double 
&&,bool &&,bool &&,class std::shared_ptr<class 
chrono::ChMaterialSurfaceSMC> &)" 
(??$make_shared@VChBodyEasyBox@chrono@@AEANAEANAEANN_N_NAEAV?$shared_ptr@VChMaterialSurfaceSMC@chrono@@@std@@$0A@@chrono_types@@YA?AV?$shared_ptr@VChBodyEasyBox@chrono@@@std@@AEAN00$$QEAN$$QEA_N2AEAV?$shared_ptr@VChMaterialSurfaceSMC@chrono@@@2@@Z)

This error shows a linking problem in that the program could not find the 
new operator in ChFrame. I have 3 other errors denoting linker problems 
with the delete operator for ChFrame, along with the new and delete operators 
for ChLinkLock. I'm wondering if the source files in Project Chrono have 
since changed to no longer support these operators or if there's something 
wrong with how I built the project.

Best,
Daniel

-- 
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/projectchrono/2e8da663-45f5-416d-a1fd-a9e8eb2ff88dn%40googlegroups.com.

Reply via email to