On Thu, Feb 9, 2023 at 10:09 PM Ferry Toth <[email protected]> wrote: > > Op 25-01-2023 om 09:17 schreef Bartosz Golaszewski: > > From: Bartosz Golaszewski <[email protected]> > > > > It seems that automake's AM_PATH_PYTHON() macro no longer sets the > > $PYTHON variable. This means the python bindings build for libgpiod has > > been broken for some time. As we know which version we're using - > > I have in my conf file: > # Build python bindings for libgpiod > PACKAGECONFIG:append:pn-libgpiod = " python3" > > and it work ok on Kirkstone which builds automake-native 1.16.5. > Which version is causing you trouble?
It builds on kirkstone but doesn't build on master (not sure which subsequent branch first failed) without that change. I can see the automake version didn't change but for libgpiod v2 we moved away from automake python support in favor of setup.py so I don't want to spend too much time on it unnecessarily. I just noticed that AM_PATH_PYTHON() no longer sets the PYTHON variable for some reason. AFAIK python support in autotools is quite wonky anyway so good riddance for libgpiod v2. Bart
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#101011): https://lists.openembedded.org/g/openembedded-devel/message/101011 Mute This Topic: https://lists.openembedded.org/mt/96517158/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
