On 1/14/2021 1:41 AM, Marco Atzeri via Cygwin-apps wrote:
On 14.01.2021 03:53, Ken Brown via Cygwin-apps wrote:
On 1/10/2021 8:36 AM, Lemures Lemniscati via Cygwin-apps wrote:
On Sun, 10 Jan 2021 12:46:43 +0100, Marco Atzeri via Cygwin-apps
On 10.01.2021 01:07, Lemures Lemniscati via Cygwin-apps wrote:
Building on my system I found that gobject-introspection will need
a rebuild for python3.



Although I'm not sure...
We might need to rebuild gobject-introspection, as Marco said,
and python*-mako also.

I am uploading python*mako as test
I will also try to rebuild gobject-introspection

I've just pushed an update for python 3.8 to the playground branch at

https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/gobject-introspection.git

That should be a good starting point for you.
I can do a non-maintainer upload of gobject-introspection, rebuilt for python3, to see if that helps.  I'm in the process of testing the build on Scallywag at the moment.  I'm using python37 because of the mako requirement.

I'd prefer to upgrade gobject-introspection to a more recent release rather than just rebuilding the current release.  But, unfortunately, a more recent gobject-introspection would require a more recent glib2.0. I'm not sure it's a good idea to update glib2.0 without updating all of GNOME.  I tried to start a discussion about this last May, but it didn't get very far:

I will try the current version as first.
A further upgrade seems to need a major patch effort.

I played with gobject-introspection-1.64.1 last summer and updated the patches. If you're curious, you can find what I did in the 1.64 branch at the same source repo that I cited above. But in order to build it, I had to build and install an updated glib2.0, since it required glib2.0 >= 2.58.0. (I also used pip to install python-markdown, which was a new build requirement.)

Maybe I'll take a little time right now to push my glib2.0 work in case someone braver than I am wants to pick this up. I'm afraid to do it for the reason Achim gave in his recent email in this thread.

Ken

Reply via email to