Re: tigervnc and fltk

This is a multi-part message in MIME format...

------------=_1781414098-1253-35602
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, 2026-06-13 at 21:48 -0500, Bruce Dubbs wrote:
> I've been working on updating tigervnc today.=C2=A0 Right now we have an
> instruction to=20
> allow it to be built with fltk-1.4.=C2=A0 However vncviewer does not work
> properly with=20
> that version.=C2=A0 I downgraded to fltk-1.3 and vncviewer works properly.
>=20
> We have a couple of options.=C2=A0 We can leave fltk at version 1.4 and
> tell users to
> build gnome-connections to access a vnc or we can downgrade fltk to
> version 1.3.11.
>=20
> Looking at BLFS we have three packages that use fltk:
>=20
> pinentry=C2=A0=C2=A0 -- optional
> =C2=A0=C2=A0=C2=A0 This package does look for fltk-1.4 but according to c=
onfigure
> fltk-1.3 is OK.
>=20
> alsa-tools -- recommended for hdspconf and hdspmixer)
> =C2=A0=C2=A0=C2=A0 hdspconf is a gui app to control hw settings and inter=
nal routing
> for
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 RME Hammerfall DSP (HDSP) audio interfaces
> =C2=A0=C2=A0=C2=A0 hdspmixer is a gui app to control hw mixing for HDSP a=
udio
> interfaces.
>=20
> tigervnc - required
>=20
> I looked at Arch and they have both fltk-1.4 and fltk-1.3
> instructions.=C2=A0 The=20
> difference is that version 1.4 supports HighDPK displays and 1.3 does
> not.
>=20
> For both alsa-tools and tigervnc Arch uses fltk-1.3.=C2=A0 They do not
> mention fltk for=20
> pinentry at all.
>=20
> My feeling is that the need for tigervnc's vncviewer is the greatest
> for BLFS.
>=20
> There may be other non-BLFS packages that really need fltk-1.4.
>=20
> I want to get opinions on how to go on this.=C2=A0 What do you think?

I'm somewhat amazed that we discover just now that the move to fltk-
1.4.x broke vncviewer; the move occurred in January 2025!

A more recent change is the move to nettle-4.x. There are instructions
to adapt to it. I added those instructions, but couldn't test at the
time (then I forgot about it, sorry...). So isn't the problem with
nettle rather?

For the main question, I have no strong feelings...

Pierre

------------=_1781414098-1253-35602
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page
------------=_1781414098-1253-35602--