Re: [Buildroot] pkg-meson.mk: support for the host python packages

From: Peter Seiderer via buildroot <buildroot@buildroot.org>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: James Hilliard <james.hilliard1@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] pkg-meson.mk: support for the host python packages
Date: Mon, 22 Apr 2024 15:11:55 +0200	[thread overview]
Message-ID: <20240422151155.28acd5df@gmx.net> (raw)
In-Reply-To: <CAGm1_kudsdPfm+++_ZTXz2D23ezUJSxGaKaGpxC_ac45eK8sgQ@mail.gmail.com>

On Mon, 22 Apr 2024 14:29:42 +0200, Yegor Yefremov <yegorslists@googlemail.com> wrote:

> On Mon, Apr 22, 2024 at 2:28 PM Yegor Yefremov
> <yegorslists@googlemail.com> wrote:
> >
> > On Mon, Apr 22, 2024 at 2:19 PM Peter Seiderer <ps.report@gmx.net> wrote:  
> > >
> > > On Mon, 22 Apr 2024 12:46:04 +0200, Yegor Yefremov <yegorslists@googlemail.com> wrote:
> > >  
> > > > libglib2 2.80.0 requires host-python-packaging to build the library [1].
> > > >
> > > > What is the best way to tell meson/ninja where to look for our host
> > > > python packages?
> > > >
> > > > [1] https://gitlab.gnome.org/GNOME/glib/-/commit/fc6f06127cff9fe3e464b5be8c92ea08a679b620  
> > >
> > > diff --git a/package/libglib2/libglib2.mk b/package/libglib2/libglib2.mk
> > > index c06ded2a5b..819282910a 100644
> > > --- a/package/libglib2/libglib2.mk
> > > +++ b/package/libglib2/libglib2.mk
> > > @@ -34,9 +34,11 @@ HOST_LIBGLIB2_CONF_OPTS = \
> > >
> > >  LIBGLIB2_DEPENDENCIES = \
> > >         host-pkgconf host-libglib2 \
> > > +       host-python3 host-python-packaging \
> > >         libffi pcre2 zlib $(TARGET_NLS_DEPENDENCIES)
> > >
> > >  HOST_LIBGLIB2_DEPENDENCIES = \
> > > +       host-python3 host-python-packaging \
> > >         host-gettext \
> > >         host-libffi \
> > >         host-pcre2 \  
> >
> > This just builds the package but meson won't look in
> > host/lib/python3.11/site-packages/ for regex.  

Sorry, works for me (and additional removed the local python311-packaging on the
build system, but works otherwise too):

	$ rm -rf build/host-libglib2-2.80.0 && rm -rf build/libglib2-2.80.0 && strace -fo out.log make libglib2

	$ grep packaging build/libglib2-2.80.0/build/meson-logs/meson-log.txt 
	Program python3 (packaging) found: YES (<my_local_build_path>/host/bin/python3) modules: packaging

	$ grep packaging out.log
	[...]
	21929 newfstatat(AT_FDCWD, "<my_local_build_path>/host/lib/python3.11/site-packages/packaging/__init__.py", {st_mode=S_IFREG|0644, st_size=496, ...}, 0) = 0
	21929 newfstatat(AT_FDCWD, "<my_local_build_path>/host/lib/python3.11/site-packages/packaging/__init__.py", {st_mode=S_IFREG|0644, st_size=496, ...}, 0) = 0
	21929 openat(AT_FDCWD, "<my_local_build_path>/host/lib/python3.11/site-packages/packaging/__pycache__/__init__.cpython-311.pyc", O_RDONLY|O_CLOEXEC) = 3

Regards,
Peter

> 
> s/regex/package
> 
> >
> > Should one just add a PYTHONPATH pointing to
> > host/lib/python3.11/site-packages before invoking meson/ninja as we do
> > with PYTHONNOUSERSITE?
> >
> > Yegor  

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot