From: Luca Boccassi <luca.boccassi@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] python3-pygobject: move python3-setuptools from RDEPENDS to DEPENDS
Date: Thu, 08 Aug 2019 12:48:22 +0100 [thread overview]
Message-ID: <09712a9113c606faf3b96e02cf3f009ef931507c.camel@gmail.com> (raw)
In-Reply-To: <20190805105232.16148-1-luca.boccassi@gmail.com>
> On 05/08/2019 11:52, luca.boccassi@gmail.com wrote:
> > inherit gnomebase distutils3-base gobject-introspection upstream-
> version-is-even
> >
> > -DEPENDS += "python3 glib-2.0"
> > +DEPENDS += "python3 python3-setuptools glib-2.0"
>
> If setuptools is a build dependency then surely you mean
> python3-setuptools-native. And if you need python3-setuptools-
> native,
> then just inherit setuptools3 instead of distutils3-base.
>
> Ross
Hi,
inheriting setuptools3 does not seem to work, the build fails:
2019-08-07T20:29:11.4006600Z [INFO] [10443] | /source/build-
project/tmp/work/aarch64-project-linux/python3-pygobject/3.28.3-
r0/recipe-sysroot-native/usr/bin/python3-native/python3: can't open
file 'setup.py': [Errno 2] No such file or directory
Using the -native suffix works, so sent a v2 doing that.
Thanks!
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-08-08 11:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 10:52 [PATCH] python3-pygobject: move python3-setuptools from RDEPENDS to DEPENDS luca.boccassi
2019-08-05 11:32 ` Ross Burton
2019-08-08 11:47 ` [PATCH v2] " luca.boccassi
2019-08-08 12:03 ` Alexander Kanavin
2019-08-08 13:57 ` Luca Boccassi
2019-08-08 11:48 ` Luca Boccassi [this message]
2019-08-08 13:58 ` [PATCH v3] " luca.boccassi
2019-08-08 14:03 ` Jacob Kroon
2019-08-08 14:37 ` Luca Boccassi
2019-08-08 14:02 ` [PATCH v4] python3-pygobject: remove python3-setuptools from RDEPENDS luca.boccassi
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=09712a9113c606faf3b96e02cf3f009ef931507c.camel@gmail.com \
--to=luca.boccassi@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