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
Big fan of cglm.
Want to try out making a project with the struct API. If you precompile cglm, you need to use call.h and the calls become glmc_XXX. But it doesn't seem, that this is possible with the struct api, as there exists no struct_call.h and no glmsc_XXX.
Is this an undesired feature? Is this a planned feature?
Can you reorganize the headers yourself to split them into a header and implementation, similar to how you can split single-header libraries?
The text was updated successfully, but these errors were encountered:
I didn't think about struct-call before actually. struct_call.h could be an option or we could provide a macro option like GLM_STRUCT_FORWARD_TO_CALL maybe, to forward all struct functions to call apis instead of inline api, default could be inline. But it would disable struct-inline entirely which may not be desired always. But it can be an option.
Big fan of cglm.
Want to try out making a project with the struct API. If you precompile cglm, you need to use call.h and the calls become glmc_XXX. But it doesn't seem, that this is possible with the struct api, as there exists no struct_call.h and no glmsc_XXX.
Is this an undesired feature? Is this a planned feature?
Can you reorganize the headers yourself to split them into a header and implementation, similar to how you can split single-header libraries?
The text was updated successfully, but these errors were encountered: