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
Many projects related to freedesktop.org and the graphics stacks have already migrated to Meson build system. If libedid was Meson too, it could easily be used as a sub-project from other projects, maybe to provide a static library. That would be an easy way to integrate libedid before it gets packaged in distributions. As static library, it also wouldn't need a stable API or ABI before being used, if compositors use a git snapshot of it. Meson wrap would make it very easy, but need a Meson build system in libedid.
This is not urgent until you want this actually used in compositor projects.
The text was updated successfully, but these errors were encountered:
Note that all the talk about Meson is based on the assumption that you have your own project.
If we go to edid-decode instead, I won't ask for Meson at all, since it's an existing project. However, if edid-decode upstream would be happy have a Meson build system, that's a different story.
Many projects related to freedesktop.org and the graphics stacks have already migrated to Meson build system. If libedid was Meson too, it could easily be used as a sub-project from other projects, maybe to provide a static library. That would be an easy way to integrate libedid before it gets packaged in distributions. As static library, it also wouldn't need a stable API or ABI before being used, if compositors use a git snapshot of it. Meson wrap would make it very easy, but need a Meson build system in libedid.
This is not urgent until you want this actually used in compositor projects.
The text was updated successfully, but these errors were encountered: