DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 59PC7WFT3461472
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 931573857B84
MIME-Version: 1.0
Date: Sat, 25 Oct 2025 21:06:25 +0900
Message-ID: <CAA3frXRCBQqGsafyWDFqRaYRGWbe5Lva-PPs7DsdO_ztJFUGww@mail.gmail.com>
Subject: CMake 3.31.3 no longer detects Boost 1.66 due to Config mode
 preference
To: cygwin AT cygwin DOT com
From: Daisuke Fujimura via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Daisuke Fujimura <booleanlabel AT gmail DOT com>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit

When using the current Cygwin CMake package (3.31.3), CMake fails to
detect an installed Boost 1.66 installation.
This issue appears to be caused by an upstream change introduced
around CMake 3.30, where find_package(Boost) now prefers Config mode
over the legacy Module mode (FindBoost.cmake).

Since Boost 1.66 does not provide a BoostConfig.cmake, CMake 3.31.3
assumes that Boost is not installed, even though the libraries are
actually present.

As far as I understand, this is an expected upstream behavior rather
than a Cygwin packaging bug. However, for users still depending on
older Boost versions, it may cause unexpected detection failures.

Upgrading Boost to version 1.70 or later (which provides
BoostConfig.cmake) is therefore recommended.

I’m aware that the Boost package currently has no active maintainer,
but I wanted to document this behavior in case others encounter the
same issue.

-- 
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