On 2025-05-03 7:31 p.m., Daisuke Fujimura via Cygwin wrote:
The *.pc file name included in cairomm1.0 has changed, and gtkmm3.0
needs to adapt to this change.
I think we might have another problem, namely that the last update to
cairomm broke it.
gtkmm2.0 and pangomm1.4 couldn't be rebuilt (and probably gtkmm3.0 as
well), complaining that they couldn't find cairo-1.0.
This is from the website of cairomm:
https://www.cairographics.org/cairomm/
There are two series of cairomm releases, each with its own stable
API/ABI. Releases up to 1.14.z (z is any integer) belong to the
cairomm-1.0 ABI series. They are used by gtkmm-2.4 and gtkmm-3.0.
cairomm 1.16.0 and higher-numbered releases belong to the cairomm-1.16
ABI series. They are used by gtkmm-4.0.
So, right now, if you install the latest version of cairomm, you end up
with 1.18, which is used by gtkmm4.0 (I don't think we have gtk4 at all
in the repo, so it's not terribly useful). gtk2 and gtk3 use the
1.0-series, therefore would need 1.14.5, but installing "cairomm1.0"
forces you to use something incompatible.
Right now we have a package called "libcairomm1.0_1.16_1". Given the
above, that makes no sense and shouldn't exist. We should have two
separate cairomm package sets: cairomm1.0 (1.14.5) and cairomm1.16 (1.18).
--
pbl
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
