• George Kiagiadakis's avatar
    lib/wp: merge both WpRemote & WpRemotePipewire in WpCore · a63f2bb9
    George Kiagiadakis authored
    In practice we always create a remote and connect to pipewire.
    Any other scenario is invalid, therefore, it is not justified
    to be confused with so many classes for such small functionality.
    This simplifies a lot the modules code.
    Also, this commit exposes the pw_core and pw_remote objects
    out of WpCore. This is in practice useful when dealing with low-level
    pw and spa factories, which are used in the monitors. Let's not
    add API wrappers for everything... Bindings will never use this
    functionality anyway, since it depends on low level pipewire C API.
proxy.c 20.1 KB