Archived issue #0032642
Coding - missing Standard_EXPORT in public interface of Standard_ErrorHandler
Description
Gmsh cannot be linked against the current development version of OCCT due to the `unresolved external symbol` error pointing to this file.
//! Registers this callback object in the current error handler (if found).
void RegisterCallback();
//! Unregisters this callback object from the error handler.
void UnregisterCallback();
//! Destructor
virtual ~Callback();
//! Registers this callback object in the current error handler (if found).
void RegisterCallback();
//! Unregisters this callback object from the error handler.
void UnregisterCallback();
//! Destructor
virtual ~Callback();
Public activity
5 archived notes
Participants are labeled by their role within this record.
Branch [archived branch] has been created by Author.
[revision removed]
Detailed log of new commits:
Author: Author
Date: Mon Oct 25 18:38:25 2021 +0300
0032642: Coding - missing Standard_EXPORT in public interface of Standard_ErrorHandler
Add missing Standard_EXPORT macro.
[revision removed]
Detailed log of new commits:
Author: Author
Date: Mon Oct 25 18:38:25 2021 +0300
0032642: Coding - missing Standard_EXPORT in public interface of Standard_ErrorHandler
Add missing Standard_EXPORT macro.
Standard_EXPORT should be added only in case when OCC_CONVERT_SIGNALS is defined while building OCCT.
Branch [archived branch] has been deleted by Author.
[revision removed]
[revision removed]
Kirill's message explains the root cause of the problem.
Dear Commenter 1,
Please close this ticket, it was created mistakenly.
Please close this ticket, it was created mistakenly.
Related records