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: Fri, 12 Jun 2020 15:44:22 +0100	[thread overview]
Message-ID: <bcf39324-9baf-39b0-8945-1789faa6f236@dronecode.org.uk> (raw)
In-Reply-To: <070a6a40-a1f4-c17e-3da6-3541174c5ec5@cornell.edu>

On 12/06/2020 00:23, Ken Brown via Cygwin-apps wrote:
> On 6/11/2020 5:39 PM, Jon Turney wrote:
[...]
>> --- shlibs.py~  2018-02-11 23:15:03.000000000 +0000
>> +++ shlibs.py   2020-06-11 22:28:07.901294700 +0100
>> @@ -62,7 +62,7 @@
>>       if platform.system() == 'Darwin':
>>           pattern = "([^\s]*lib*%s[^A-Za-z0-9_-][^\s\(\)]*)"
>>       elif platform.platform().startswith('CYGWIN'):
>> -        pattern = "([^\s]*cyg*%s[^A-Za-z0-9_][^\s\(\)]*)"
>> +        pattern = "([^\s]*cyg%s[-.0-9]*\.[^\s\(\)]*)"
>>       return re.compile(pattern % re.escape(library_name))
>>
>> But this all seems very fragile though, so I'm not sure if that's the 
>> right way to fix this.
>>
>> (This 'if cygwin' case is coming from gobject-introspection package in 
>> [1], it's not in upstream)
>>
>> https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/gobject-introspection.git;a=blob;f=1.46.0-cygwin.patch;h=a03271ea17e0d167eba7627ddf5d4303bbde9871;hb=4e3b8bd140db78ee35f29ee3d07ff3715416e259#l93 
> 
> Thanks, Jon!  Just as your mail came in, I was staring at the regex for 
> harfbuzz-gobject in shlibs.py, trying to understand why it wasn't 
> matched.  It never occurred to me that the cygharfbuzz-gobject-0.dll 
> line in the ldd output was being used to match the regex for harfbuzz 
> rather than the one for harfbuzz-gobject.  What a mess.

Yeah, I went around in circles on that a few times myself :)

  reply	other threads:[~2020-06-12 14:44 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 [this message]
2020-08-01 18:01                                     ` Ken Brown
2020-08-01 18:34                                       ` Jon Turney

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=bcf39324-9baf-39b0-8945-1789faa6f236@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).