8000 Optional GLFW termination on library side if client code initializes it. · Issue #2687 · glfw/glfw · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Optional GLFW termination on library side if client code initializes it. #2687
Open
@abhi-k9

Description

@abhi-k9

Hi,

I have a library that uses GLFW to setup the context for OpenGL offscreen rendering. At the moment, I initialize and terminate the it around my API calls.

However, the client code could also be depending on GLFW and needs it to remain in a initialized state after completion of my API functions, i.e. my library should not terminate GLFW if the client code initialized GLFW for its own purposes.

I was thinking of checking if it was already initialized upon entry to my API and if so not terminate, but #2036 mentions this is not possible as of now, and attempts to add reference counting have been hanging for a long time #2070.

Are there any workarounds for this use case?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0