public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Help needed with gobject-introspection
Date: Sat, 1 Aug 2020 19:34:14 +0100	[thread overview]
Message-ID: <3967e4d9-1a8d-358a-b2be-4c23eb1bee1d@dronecode.org.uk> (raw)
In-Reply-To: <a151f89d-a4ed-7e56-6811-3162428420b8@cornell.edu>

On 01/08/2020 19:01, Ken Brown via Cygwin-apps wrote:
> 
> No one has suggested a better fix, so I think we should get your fix 
> into the distro.  It's not urgent, because harfbuzz still supports both 
> autotools and meson, but they're encouraging packagers to move toward 
> meson.

I think the real fix is for g-ir-scanner not to do this.

(To be clearer, I think the invoking build system has, in nearly all 
cases, an accurate idea of the mapping g-ir-scanner is trying to 
discover here (between libraries named in linker -l options and the 
actual shared library filename?), and it should just have options to let 
the build system give it that information, rather these going through 
these contortions to try to work it out)

But since that seems unlikely to happen anytime soon, so I guess this is 
the best we can do.

> How do you think we should proceed?  Are you interested in adopting 
> gobject-introspection?  Alternatively, one of us could do a 
> non-maintainer upload while we wait for a volunteer.

Please go ahead with an NMU, if you have the time for it.


      reply	other threads:[~2020-08-01 18:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 23:04 Ken Brown
2020-05-20 14:50 ` Ken Brown
2020-05-21 13:24   ` Jon Turney
2020-05-21 15:13     ` Ken Brown
2020-05-21 15:48       ` Jon Turney
2020-05-21 17:07         ` Ken Brown
2020-05-24 15:56           ` Jon Turney
2020-05-24 16:45             ` Ken Brown
2020-05-24 17:00               ` Ken Brown
2020-05-25 15:04                 ` Ken Brown
2020-05-29 15:56                   ` Jon Turney
2020-05-27 20:32             ` Ken Brown
2020-05-29 15:54               ` Jon Turney
2020-05-31 20:52                 ` Jon Turney
2020-05-31 23:58                   ` Ken Brown
2020-06-01 11:30                     ` Jon Turney
2020-06-02 14:26                       ` Jon Turney
2020-06-02 14:31                         ` Ken Brown
2020-06-02 21:28                           ` Jon Turney
2020-06-03 16:51                             ` Jon Turney
2020-06-03 18:30                               ` Ken Brown
2020-06-06 14:15                                 ` Ken Brown
2020-06-11 21:39                                   ` Jon Turney
2020-06-11 23:23                                     ` Ken Brown
2020-06-12 14:44                                       ` Jon Turney
2020-08-01 18:01                                     ` Ken Brown
2020-08-01 18:34                                       ` Jon Turney [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3967e4d9-1a8d-358a-b2be-4c23eb1bee1d@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).