Skip to content

Meson support for Xvnc for xserver master branch with a patch - #2064

Draft
kohnish wants to merge 1 commit into
TigerVNC:masterfrom
kohnish:xvnc-meson
Draft

Meson support for Xvnc for xserver master branch with a patch#2064
kohnish wants to merge 1 commit into
TigerVNC:masterfrom
kohnish:xvnc-meson

Conversation

@kohnish

@kohnish kohnish commented Feb 9, 2026

Copy link
Copy Markdown

I've finished the work of #1729 and tested with the latest xserver master.
Their master branch is changeable, so the patch file is will be update on the best effort basis.

@CendioOssman CendioOssman left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the refresh of this PR. But I'm still sceptical to merge this whilst there is no release of the master branch and everything is a moving target.

Is there any distribution that uses the master branch?

We can have this PR as a draft for reference until then, though.

Comment on lines +15 to +21
dependency('zlib'),
dependency('pam'),
dependency('gnutls'),
dependency('nettle'),
dependency('hogweed'),
dependency('gmp'),
dependency('libjpeg'),

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As mentioned in the original PR, this is duplication we want to avoid. So we'd like some clever way of providing this information to Meson based on what's in our CMake files.

Comment on lines +27 to +28
'vncDRI3.c',
'vncDRI3Draw.c',

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aren't these conditional, like for autoconf?

Comment on lines +52 to +54
'../../../../common',
'../../../common',
'../../../vncconfig',

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably have a tigervnc_srcdir like we do for autoconf, to support different ways of building Xvnc.

srcs_xvnc,
include_directories : [inc, xvnc_inc],
dependencies: common_dep,
c_args: ['-DTIGERVNC', '-DNO_MODULE_EXTS'],

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are no longer used.

@CendioOssman
CendioOssman marked this pull request as draft February 10, 2026 08:57
@kohnish

kohnish commented Feb 10, 2026

Copy link
Copy Markdown
Author

Thanks for the refresh of this PR. But I'm still sceptical to merge this whilst there is no release of the master branch and everything is a moving target.

Is there any distribution that uses the master branch?

We can have this PR as a draft for reference until then, though.

Thanks for the reviews. I made a commit as a gentoo user for the benefit for myself. I feel like xvnc user is only myself.
I doubt any distributions support master branches in general officially.

Gentoo has this concept of live builds that just build master. It's quite useful to try the latest features/fixes of things, also beneficial on official version bump. Possibly Arch AUR supports something similar.

I'm happy to address the review remarks if you think it makes sense to merge it at all. Otherwise, I think closing is also fine.

@CendioOssman

Copy link
Copy Markdown
Member

Let's keep this PR in limbo as a draft until Xorg's main branch stabilises. They seem to be aiming for a release soon-ish, at which point we can merge it.

So feel free to have a look at my feedback and keep the branch up to date until the time comes to merge things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants