WaylandCS 1.0.0
dotnet add package WaylandCS --version 1.0.0
NuGet\Install-Package WaylandCS -Version 1.0.0
<PackageReference Include="WaylandCS" Version="1.0.0" />
<PackageVersion Include="WaylandCS" Version="1.0.0" />
<PackageReference Include="WaylandCS" />
paket add WaylandCS --version 1.0.0
#r "nuget: WaylandCS, 1.0.0"
#:package WaylandCS@1.0.0
#addin nuget:?package=WaylandCS&version=1.0.0
#tool nuget:?package=WaylandCS&version=1.0.0
WaylandCS
C# binding for Wayland using Net6.0 or above. Inspired by wayland-scanner in C language.
Goals
- support wayland extension protocols as many as possible
- easy to use, stable in production
Compatibility
.NET Version | Compatibility |
---|---|
.NET | (6.0 and above) ✔️ |
.NET Standard | ❌ |
.NET Framework | ❌ |
Getting started
Install WaylandCS nuget package.
dotnet add package WaylandCS
Grab wayland.xml
from freedesktop.org. Drop the file into your project.
Add the following to your .csproj
:
<ItemGroup>
<CompilerVisibleItemMetadata Include="AdditionalFiles" MetadataName="WaylandProtocol" />
<AdditionalFiles Include="wayland.xml" WaylandProtocol="client" />
</ItemGroup>
Quick Guide
using WaylandCS namespace
using WaylandCS;
Connection to a wayland display server can be established by calling:
WlDisplay.Connect(string);
Global objects can be retrieved by creating a registry object and listening for
Global
event
using wlDisplay = WlDisplay.Connect();
using wlRegistry = wlDisplay.GetRegistry();
wlRegistry.Global += (_, e) =>
{
Console.WriteLine($"{e.Name}:{e.Interface}:{e.Version}");
};
wlDisplay.Roundtrip();
Either a WlDisplay.Roundtrip()
or WlDisplay.Dispatch()
is required to
generate event invocations. In this case, Global
event will occur upon calling
Roundtrip()
.
As described in Wayland's official docs,
WlDisplay.Roundtrip()
dispatches all currently pending events. If no events
are pending, the function returns 0, otherwise it returns the number of pending
events that were processed. This internally calls Sync
and waits for the
server's callback before returning.
On the other hand, Dispatch
will block until there are events to process,
as such, it will never return 0. It is useful for setting up an event loop, like
in this example below.
while (someWlDisplayInstance.Dispatch() != -1)
{
// intentionally empty
}
Binding to global objects are done by using the data received from
GlobalEventArgs
, specifically Name
(a unique uint
given by the server
for this instance of global object), Interface
(the contract used), and
Version
and passing it as the arguments of WlRegistry.Bind()
.
As an example, assuming that the user wants to bind to a wl_output
wlRegistry.Global += (_, e) =>
{
if (e.Interface == WlInterface.WlOutput.Name)
{
// Passing a version is optional, it'll use the version specified in
// the protocol xml by default.
using var wlOutput = wlRegistry.Bind<WlOutput>(e.Name, e.Interface);
// do something about wlOutput here.
}
};
Learn more about Target Frameworks and .NET Standard.
-
.NETStandard 2.0
- Microsoft.Bcl.HashCode (>= 1.1.1)
- Microsoft.CodeAnalysis.CSharp (>= 4.2.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last Updated |
---|---|---|
1.0.0 | 86 | 7/29/2025 |