tigervnc and fltk
"Bruce Dubbs" ([email protected] via blfs-dev Mailing List) <[email protected]> Sat, 13 Jun 2026 21:48:03 -0500
| Newsgroups | gmane.linux.lfs.beyond.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format...
------------=_1781405292-1253-35572
Content-Language: en-US
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
I've been working on updating tigervnc today. Right now we have an instruction to
allow it to be built with fltk-1.4. However vncviewer does not work properly with
that version. I downgraded to fltk-1.3 and vncviewer works properly.
We have a couple of options. 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.
Looking at BLFS we have three packages that use fltk:
pinentry -- optional
This package does look for fltk-1.4 but according to configure fltk-1.3 is OK.
alsa-tools -- recommended for hdspconf and hdspmixer)
hdspconf is a gui app to control hw settings and internal routing for
RME Hammerfall DSP (HDSP) audio interfaces
hdspmixer is a gui app to control hw mixing for HDSP audio interfaces.
tigervnc - required
I looked at Arch and they have both fltk-1.4 and fltk-1.3 instructions. The
difference is that version 1.4 supports HighDPK displays and 1.3 does not.
For both alsa-tools and tigervnc Arch uses fltk-1.3. They do not mention fltk for
pinentry at all.
My feeling is that the need for tigervnc's vncviewer is the greatest for BLFS.
There may be other non-BLFS packages that really need fltk-1.4.
I want to get opinions on how to go on this. What do you think?
------------=_1781405292-1253-35572
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
------------=_1781405292-1253-35572--