Re: [ITP] python-scikit-build-core

On 23/03/2026 21:42, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 23/03/2026 20:08, Jon Turney wrote:
>> On 19/03/2026 14:43, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>>> On 15/03/2026 15:56, Hamish McIntyre-Bhatty wrote:
>>>> Hi all,
>>>>
>>>> scikit-build-core (https://pypi.org/project/scikit-build-core/) is a 
>>>> dependency of pybind11, which is itself a dependency of recent 
>>>> versions of python-imaging (a package I already maintain), and as 
>>>> such I'd like to package it for Cygwin.
>>>>
>>>> I haven't yet created a cygport file for this package, but will do 
>>>> shortly.
>>>>
>>>> scikit-build-core is in Debian: https://packages.debian.org/trixie/ 
>>>> python3-scikit-build-core
>>>>
>>>> This, together with pybind11, will enable me to release the current 
>>>> version of python-imaging for Python 3.12 as stable, and start 
>>>> working on wxPython for Python 3.12.
>>>>
>>>> Best,
>>>> Hamish
>>>>
>>> I have now created a cygport file for this package, and it is 
>>> available at: https://gitlab.com/hamishmb/cygwin-python-scikit-build- 
>>> core
>>
>> Thanks.
>>  This looks fine.
> Cheers!
>>
>>> PATCH_URI=""
>>
>> You don't need to keep this around if it's empty.
> Good to know, I shall remove it.
>>
>>> CMAKE_PREFIX_PATH=$CMAKE_PREFIX_PATH:${I}/usr/lib/python${v}/site- 
>>> packages/pybind11/share/cmake/pybind11/ cmake ..
>>
>> This makes me kind of wonder if pybind shouldn't be installing these 
>> files into /usr/share/cmake/ (or similar), where cmake can find them 
>> by default? 

(To be clear, I don't consider that a blocker, but it does save having 
to repeat this voodoo in anything that uses pybind11)

> Yeah I have no idea why it isn't to be honest. Shall I ask if I can 
> somehow configure this?

Yes, that might be helpful.

A brief look at the Fedora packaging [1] looks like it's working around 
this issue also...

[1] https://src.fedoraproject.org/rpms/pybind11/blob/rawhide/f/pybind11.spec