From: Sascha Silbe <x-yo17@se-silbe.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gobject-introspection: relocate typelib repository for native builds
Date: Thu, 14 Jun 2018 18:13:57 +0200 [thread overview]
Message-ID: <toe4li5z6pm.fsf@twin.sascha.silbe.org> (raw)
In-Reply-To: <CANNYZj894Yin6tnTSW1Mw3YdcLkX9CdSBcs8kOo1iubi+LmHEA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
Alexander Kanavin <alex.kanavin@gmail.com> writes:
> 2018-06-08 22:27 GMT+03:00 Sascha Silbe <x-yo17@se-silbe.de>:
>> We have some Python modules that we are extracting some information from
>> and generating documentation for at build time; both times the modules
>> get imported. We don't need GLib to actually work; it only needs to be
>> importable. Fortunately no other typelib is used by the code.
>
> Thanks for explanation. The patch is fine then and can be added to
> oe-core - so that if later g-i needs to be fully supported on the
> native side, this part would be already sorted. For now though it's
> not 'officially' working.
Fair enough. Thanks for the review! Is there anything else I should do
for the patch to go in?
Sascha
--
Softwareentwicklung Sascha Silbe, Niederhofenstraße 5/1, 71229 Leonberg
https://se-silbe.de/
USt-IdNr.: DE281696641
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2018-06-14 16:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 16:18 [PATCH] gobject-introspection: relocate typelib repository for native builds Sascha Silbe
2018-06-08 17:13 ` Alexander Kanavin
2018-06-08 18:17 ` Sascha Silbe
2018-06-08 18:45 ` Alexander Kanavin
2018-06-08 19:27 ` Sascha Silbe
2018-06-09 10:11 ` Alexander Kanavin
2018-06-14 16:13 ` Sascha Silbe [this message]
2018-06-14 18:58 ` Alexander Kanavin
2018-06-14 19:51 ` Sascha Silbe
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=toe4li5z6pm.fsf@twin.sascha.silbe.org \
--to=x-yo17@se-silbe.de \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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