El diumenge, 25 d’agost del 2024, a les 13:23:19 (CEST), Neal Gompa va 
escriure:
> On Sun, Aug 25, 2024 at 7:20 AM Neal Gompa <ngomp...@gmail.com> wrote:
> 
> >
> >
> > On Sun, Aug 11, 2024 at 7:04 PM Albert Astals Cid <aa...@kde.org> wrote:
> > 
> > >
> > >
> > > How hard would be for mingw64-boost/mingw32-boost to include
> > > BoostConfig.cmake?
> > >
> > >
> > >
> > > boost-devel does but it's on the wrong "sysroot".
> > >
> > >
> >
> >
> >
> > It shouldn't be hard, currently we're deleting the files instead of
> > keeping them. I'm not sure if the files are usable, but if you're
> > willing to test a build, I can attempt to restore them and provide a
> > test build for you to try?
> >
> >
> 
> 
> For reference, it looks like it was disabled ten years ago with this
> message:
 
> * Fri Feb 10 2012 Erik van Pienbroek <epien...@fedoraproject.org> -
> 1.48.0-3
 - Don't provide the cmake files any more as they are broken and
> cmake itself already provides its own boost detection mechanism.
> Should fix detection of boost by mingw32-qpid-cpp. RHBZ #597020, RHBZ
> #789399
 
> Those bugs are:
> 
> * https://bugzilla.redhat.com/597020
> * https://bugzilla.redhat.com/789399
> 
> If CMake has its own way to detect Boost that works for this, is there
> a reason you're not using it?

Because cmake says you is deprecating its FindBoost.

"Port projects to upstream Boost's BoostConfig.cmake package configuration 
file"

https://cmake.org/cmake/help/latest/module/FindBoost.html

Chers,
  Albert

> 
> 
> 
> -- 
> 真実はいつも一つ!/ Always, there's only one truth!




-- 
_______________________________________________
mingw mailing list -- mingw@lists.fedoraproject.org
To unsubscribe send an email to mingw-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/mingw@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to