Including shared libraries in wheels
Phil Thompson
phil at riverbankcomputing.com
Tue Mar 7 12:04:31 GMT 2023
On 07/03/2023 10:58, Jean Abou Samra wrote:
> Le mardi 07 mars 2023 à 10:53 +0000, Phil Thompson a écrit :
>
>> On 07/03/2023 10:20, Jean Abou Samra wrote:
>>
>> > Hi,
>> >
>> > I'm trying to build wheels for python-poppler-qt5, which uses SIP and
>> > PyQt-builder. It's close to working, except that my wheels don't
>> > contain the `libpoppler.so` and `libpoppler-qt5.so` files, which they
>> > should in order to work on others' machines. (I'd like avoid
>> > statically linking these into the binding's generated shared library
>> > because it would force me to compile Poppler myself into a static
>> > library on various OSes, while I can get it as a shared library from
>> > Conda.)
>> >
>> > What would be the easiest way to make these libs end up in the wheels?
>>
>>
>> See 'wheel-includes' in...
>>
>> [https://www.riverbankcomputing.com/static/Docs/sip/pyproject_toml.html#tool-sip-project-section](https://www.riverbankcomputing.com/static/Docs/sip/pyproject_toml.html#tool-sip-project-section)
>
>
> Thanks for replying. I saw this parameter, but the paths are
> relative to the project directory, while in my case, the libraries
> are somewhere in the Conda environment.
Hmm, there's no reason why it shouldn't support absolute patterns. Fixed
in the next snapshot.
Phil
More information about the PyQt
mailing list