After researching zydis bindings, zydis has a similar problem due to macro definitions that cause dll exported calling conventions to be interpreted as null by the macro, i.e. the calling convention is cleared. Seeing that the original author's approach was to modify the calling convention of the original header file using some undisclosed operation during the header file merging process, do I need to do the same when merging header files in hyperdbg?Or is there a reliable way to make sure that dll export function calling conventions are always reliable under Windows?Another possibility is that some configuration of clang overrides the macro definitions causing the calling conventions to be cleared?
After researching zydis bindings, zydis has a similar problem due to macro definitions that cause dll exported calling conventions to be interpreted as null by the macro, i.e. the calling convention is cleared. Seeing that the original author's approach was to modify the calling convention of the original header file using some undisclosed operation during the header file merging process, do I need to do the same when merging header files in hyperdbg?Or is there a reliable way to make sure that dll export function calling conventions are always reliable under Windows?Another possibility is that some configuration of clang overrides the macro definitions causing the calling conventions to be cleared?