From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: Help needed with gobject-introspection
Date: Wed, 3 Jun 2020 14:30:19 -0400 [thread overview]
Message-ID: <0876122c-1c1e-54e0-1a18-0c3774e71641@cornell.edu> (raw)
In-Reply-To: <5fb4bf89-58a5-88cb-c2cb-29cfef65ffc1@dronecode.org.uk>
On 6/3/2020 12:51 PM, Jon Turney wrote:
> On 02/06/2020 22:28, Jon Turney wrote:
>> On 02/06/2020 15:31, Ken Brown via Cygwin-apps wrote:
>>> On 6/2/2020 10:26 AM, Jon Turney wrote:
>>>> On 01/06/2020 12:30, Jon Turney wrote:
>>>>> On 01/06/2020 00:58, Ken Brown via Cygwin-apps wrote:
>>>>>>
>>>>>> I'll see what I can figure out, but as I said, it doesn't look to me like
>>>>>> a meson issue.
>>>>>
>>>>> This looks like the problem that my second patch was supposed to fix, so I
>>>>> guess I've messed up somewhere.
>>>>>
>>>>> (gtkdoc-scangobj builds and runs a executable linked with the gio shared
>>>>> library. meson needs to set PATH appropriately so that shared library can
>>>>> be loaded)
>>>>
>>>> Hmmm.. I can't reproduce this.
>>>>
>>>> Using my meson 0.54.2-2 package, I managed to build glib (from the 2.64.3
>>>> tag in the glib repository) configured with -Dgtk_doc=true.
>>>
>>> Did you run 'ninja install'? The problem doesn't show up until you do that.
>>
>> Sigh, yes, you're right. It gets built during 'all', and succeeds, and then
>> gets built again during 'install', in a slightly different way, which fails.
> Added another patch to that PR which should fix gtkdoc documentation which is
> built at install-time.
>
> Uploaded a meson 0.54.2-3 test package.
That fixes it! Thanks.
Ken
next prev parent reply other threads:[~2020-06-03 18:30 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 [this message]
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
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=0876122c-1c1e-54e0-1a18-0c3774e71641@cornell.edu \
--to=kbrown@cornell.edu \
--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).