You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I understand bx/platform.h is needed inside bgfx/c99/bgfx.h for the BX_PLATFORM_xxx macro which in turn is used to define BGFX_SYMBOL_EXPORT and BGFX_SYMBOL_IMPORT.
Both of those macros are used only if at least one of BGFX_SHARED_LIB_BUILD or BGFX_SHARED_LIB_USE is defined.
In case the bgfx API is exposed via another method (e.g. in a plugin system the bgfx_interface_vtbl_t pointer might have been provided to the plugin by the host), there is no need to depend on bx just for this header.
Is it possible to hide bx/platform.h in those cases?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
As far as I understand bx/platform.h is needed inside bgfx/c99/bgfx.h for the
BX_PLATFORM_xxx
macro which in turn is used to defineBGFX_SYMBOL_EXPORT
andBGFX_SYMBOL_IMPORT
.Both of those macros are used only if at least one of
BGFX_SHARED_LIB_BUILD
orBGFX_SHARED_LIB_USE
is defined.In case the bgfx API is exposed via another method (e.g. in a plugin system the
bgfx_interface_vtbl_t
pointer might have been provided to the plugin by the host), there is no need to depend on bx just for this header.Is it possible to hide bx/platform.h in those cases?
E.g.
It's not a big deal, but I thought of asking.
Beta Was this translation helpful? Give feedback.
All reactions