This release is a pre-release and may not be stable for production use.
Recipe for building and installing a static version of the lxml egg
This recipe automates the installation of the lxml python package and, additionally, builds it statically against dependent libraries like libxml2, libxlst.
Detailed Documentation
Supported options
The recipe supports the following options:
- egg
Set to the desired lxml egg, e.g. lxml or lxml==2.1.2
- libxslt-url, libxml2-url
The URL to download the source tarball of these libraries from. Currently defaults to:
http://dist.repoze.org/lemonade/dev/cmmi/libxslt-1.1.24.tar.gz http://dist.repoze.org/lemonade/dev/cmmi/libxml2-2.6.32.tar.gz
- build-libxslt, build-libxml2
Set to true if these should be build. Needed for a static build.
- static-build
true``or ``false
- xml2-loction
Needed if libxml2 is not built.
- xslt-loction
Needed if libxml2 is not built.
- xslt-config
Path to the xslt-config binary. Not needed if build-libxslt is set to true.
- xml2-config
Path to the xml2-config binary. Not needed if build-libxml2 is set to true.
- force
Set to true to force rebuilding libraries every time.
Example usage
We’ll start by creating a buildout that uses the recipe:
>>> xsltconfig = "foo"
>>> xml2config = "bar"
>>> write('buildout.cfg',
... """
... [buildout]
... parts = test1
... log-level = INFO
... index = http://dist.repoze.org/lemonade/dev/simple
...
... [test1]
... recipe = z3c.recipe.staticlxml
... xslt-config = %(xsltconfig)s
... xml2-config = %(xml2config)s
... """ % locals())
Running the buildout gives us:
>>> system(buildout) Installing test1. xslt-config: foo xml2-config: bar <BLANKLINE>
Contributors
Stefan Eletzhofer, Author
Change history
trunk
no changes yet
0.1 (2008-11-27)
Added iconv library, which enables fully static builds. This is actually a bug in lxml’s setup. [seletz]
Updated docs, removed junk code [seletz]
Added tweaks needed for Mac OS X [seletz]
Added basic build steps for liblxml2, libxslt and lxml. [seletz]
Created recipe with ZopeSkel [seletz].
Download
Metadata
Release files for z3c.recipe.staticlxml 0.1dev-r93403
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| z3c.recipe.staticlxml-0.1dev-r93403.tar.gz | 7.8 kB | Without provenance | Details for z3c.recipe.staticlxml-0.1dev-r93403.tar.gz |
Release files / z3c.recipe.staticlxml-0.1dev-r93403.tar.gz
| Download URL | z3c.recipe.staticlxml-0.1dev-r93403.tar.gz |
|---|---|
| Size | 7.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cbfa1eff9f406693ac25415f5a7ac459ebf13ef4e13c3320a634e39fe9db82c2
|
|
BLAKE2b-256 checksum How to use checksums |
05320767bd5e88f40cd95e087a2618d74f37f8d85aa950dc3d90d1935b7aa8e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for z3c.recipe.staticlxml 0.1dev-r93403
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.