Hi,
making this short because it has essentially been answered before on this
list. (I should drop this into a FAQ entry.)
See, for the last occurrence:
https://mail.python.org/archives/list/[email protected]/thread/FSNVCSQQECQKBF4XV7R7HODJEYGKMLRB/
Dennis Alo via lxml - The Python XML Toolkit schrieb am 31.10.26 um 09:37:
Could you kindly clarify:
Whether the official lxml 6.1.3 Windows CPython 3.14 x64 wheel
statically links GNU libiconv.
yes
Which exact libiconv source version, patches, and native-library
archives were used.
libiconv 1.19
https://github.com/lxml/libxml2-win-binaries/tree/bed89b4f0819fa3a7bf456d55780ee7a4ebb325e
https://github.com/winlibs/libiconv/tree/accac417318a3eef7402685a268cab8037e62ba1
Whether the corresponding build configuration, object files, or other
relinking materials are publicly available.
yes, see above.
What reproducible rebuilding or relinking procedure you recommend for
distributors seeking to satisfy LGPL 2.1 requirements.
Reproducible Windows builds are a bit tricky for 6.1.x. The lxml-6.1 branch
looks up the latest library release on github and downloads the libraries
with that version.
https://github.com/lxml/lxml/blob/62b002e08148049589494da1d58094a074a0201d/buildlibxml.py#L92-L111
I fixed that for lxml 7.0 to obey the "*_VERSION" environment variables
(and set them specifically for the versions used on Windows), but there's a
newer library release now than what was (and will be) used for the 6.1.x
releases, so I may have to work on that in case of a new 6.1.x release.
lxml 7.0 will use the latest library versions.
Stefan
_______________________________________________
lxml - The Python XML Toolkit mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3//lists/lxml.python.org
Member address: [email protected]
