-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[fltk] FLTK 1.3 is still needed as 1.4 is not fully backwards compatible #22769
Comments
Related, FLTK 1.3.10 was released at the same time as FLTK 1.4.0 and contains new functionality that TigerVNC wants. So it would be nice to get that new version packaged in to MSYS. |
As a temporary workaround, we've put this in place: TigerVNC/tigervnc@f06e574 |
According to upstream (https://www.fltk.org/roadmap.php) "...FLTK 1.3 is no longer in active development...FLTK 1.3.10 (released on Nov 16, 2024) is presumably the final release of branch 1.3.". We could add back a 1.3 version if really needed. How large are the incompatibilities? All our reverse deps built just fine with it. |
There would be file conflict if both fltk 1.3 and 1.4 is installed. I think the underlying issue should be fixed in tigervnc. |
We have not dug in to it. TigerVNC is a very advanced user of FLTK, and FLTK 1.4 has been in development for many years. So there are likely many things that need to be adjusted. As an example, we've got a report that the rendering pipeline is not compatible any more (linked above). To make things more complicated, we will likely need to support FLTK 1.3 for some time, as I would not assume 1.4 will be available in older Linux distributions. In short, FLTK 1.4 support in TigerVNC is not something anyone will have time to look at anytime soon. As a comparison, macOS homebrew now packages both 1.4 and 1.3: https://formulae.brew.sh/formula/fltk@1.3 I'm fairly sure this kind of overlap was also done for some time when 1.3 was released, which also wasn't fully backwards compatible with the previous version of FLTK. |
ok, thanks. Fedora is also thinking about it: https://bugzilla.redhat.com/show_bug.cgi?id=2253781 |
There are two way to go about it:
|
Conflicts are likely fine for us for the foreseeable future. We usually statically link stuff for distribution, so FLTK 1.3 just needs to be installed when building. |
Description / Steps to reproduce the issue
Expected behavior
TigerVNC builds
Actual behavior
TigerVNC fails to build (and if it would build, it would not behave correctly).
Verification
Windows Version
10.0.20348
MINGW environments affected
Are you willing to submit a PR?
No response
The text was updated successfully, but these errors were encountered: