Re: [gpsd-dev] [PATCH]: Link Python extensions with libpython - attempt 3

[Greg Troxel]

I will read it in more detail and look at your earlier notes.  But some
comments/questions:

Does the build already use python-config?  From your patch, it seems
not.

Why isn't the build using pkg-config to find python?  It seems like that
is the norm these days, and it has the advantage of being cross
friendly, in that one has to (once) set a PKG_CONFIG_PATH (and
presumably you have to do that too when you build cross).

Are you actually building cross?  Or natively under cygwin?  Why does
this even come up as an issue?  (I'm not doubting that it does; but I'd
like to understand that.)

This patch looks like it will break the build under pkgsrc, which
doesn't provide python-config, but python2.7-config.  This is due to
longstanding issues with compatibility in python requiring installing
multiple versions at once (even before python3), and sound packaging
requires that packages depending on python be bound to the specific
version used at package build time.


I'm sympathetic to what you're trying to do.  But I don't see how what's
being added is adequately portable and addresses the real issue
squarely.

pgpTzcBbRS7fD.pgp
Description: PGP signature