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
It should be possible to compile zig-cairo with or without support for optional Cairo surfaces. For example, in order to use XCB Surfaces, one has to link the XCB library. But since one might not be interested in using XCB surfaces, this feature should be optional.
Pycairo uses some compiler flags that define a few cairo.HAS constants to control whether these optional features are available or not. For example, this python script throws a runtime exception if Cairo was not compiled with PDF support.
In zig, maybe we could use @cDefine like it's done here?
It should be possible to compile zig-cairo with or without support for optional Cairo surfaces. For example, in order to use XCB Surfaces, one has to link the XCB library. But since one might not be interested in using XCB surfaces, this feature should be optional.
Pycairo uses some compiler flags that define a few cairo.HAS constants to control whether these optional features are available or not. For example, this python script throws a runtime exception if Cairo was not compiled with PDF support.
In zig, maybe we could use @cDefine like it's done here?
See also:
The text was updated successfully, but these errors were encountered: