Open CASCADE, the 3D modelling kernel
3D modeling & numerical simulation

Search the Forums
See All Topics
 

OCC 6.2 unresolved external symbol after rebuild

OCC 6.2 unresolved external symbol after rebuild
Sven Jungnickel 2007/07/24 08:28
Hi,

I have rebuild OCC 6.2 using the Visual Studio 2005 C++ Compiler. When linking the new export libraries to my application I get the following unresolved external symbol error messages:

Verknüpfen...
Bibliothek "Debug\vcpa.lib" und Objekt "Debug\vcpa.exp" werden erstellt.
SectionPlane.obj : error LNK2019: Verweis auf nicht aufgelöstes externes Symbol ""public: class Standard_Failure & __thiscall Standard_Failure::operator=(class Standard_Failure const &)" (??4Standard_Failure@@QAEAAV0@ABV0@@Z)" in Funktion ""public: class Standard_DomainError & __thiscall Standard_DomainError::operator=(class Standard_DomainError const &)" (??4Standard_DomainError@@QAEAAV0@ABV0@@Z)".
DataSet.obj : error LNK2001: Nicht aufgelöstes externes Symbol ""public: class Standard_Failure & __thiscall Standard_Failure::operator=(class Standard_Failure const &)" (??4Standard_Failure@@QAEAAV0@ABV0@@Z)".
Messpunkt.obj : error LNK2001: Nicht aufgelöstes externes Symbol ""public: class Standard_Failure & __thiscall Standard_Failure::operator=(class Standard_Failure const &)" (??4Standard_Failure@@QAEAAV0@ABV0@@Z)".
Debug\vcpa.exe : fatal error LNK1120: 1 nicht aufgelöste externe Verweise.

As I'm not using the class Standard-Failure directly it seems to me that some kind of implementation for the operator= is somewhere missing within OCC 6.2. Has anybody seen this problem before and hopefully has solved it?

Thanks, Sven
Patrik Mueller 2007/07/24 12:33
Hi Sven,

it could also be a problem with linker opimisation - try it without optimisation.

Apart from that:
have you linked all needed libs from OCC?

Greets,

Patrik
Sven Jungnickel 2007/07/24 15:38
Hi Patrik,

thanks for your answer. I think I should have linked all necessary libs from OCC. The application ran with OCC 6.1. I "simply" wanted to update the application to OCC 6.2. I also ran into some project conversion errors (missing "all" project within each *.sln file) using Visual Studio 2005, but could start the compiler.

I will try it without linker optimization sometime this week. In the meantime I switched back to OCC 6.1.

Regards,

Sven
 
 
Latest news
  • OCCT Applications
  • Open CASCADE Technology 6.8.0 is available for download!
  • New features to enhance the development process

  • © OPEN CASCADE 2000 - 2014  |  Search  |  Contacts   |  Site map