Package Details: wkhtmltopdf-static 0.12.6.1_r3-1

Git Clone URL: https://aur.archlinux.org/wkhtmltopdf-static.git (read-only, click to copy)
Package Base: wkhtmltopdf-static
Description: Shell utility to convert HTML to PDF using Webkit and Qt (upstream static build)
Upstream URL: https://github.com/wkhtmltopdf/packaging
Licenses: GPL3
Conflicts: wkhtmltopdf
Provides: wkhtmltopdf
Submitter: foutrelis
Maintainer: koonix
Last Packager: koonix
Votes: 60
Popularity: 0.009663
First Submitted: 2010-02-06 14:46 (UTC)
Last Updated: 2023-05-22 12:59 (UTC)

Required by (27)

Sources (4)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

kageurufu commented on 2017-04-28 16:03 (UTC)

https://github.com/wkhtmltopdf/wkhtmltopdf/issues/3001 On my usage, the QSslSocket errors are output to stderr, and I'm still able to use "wkhtmltopdf - -" with pipes for input/output (Python subprocess) Can you provide more details?

Koterpillar commented on 2017-04-28 10:41 (UTC)

The QSslSocket error messages are printed to the standard output, not standard error, breaking use use of "-" for output file.

sanerb commented on 2017-04-28 05:57 (UTC)

anyone else getting similar errors to this since openssl was updated to 1.1.x? OSError: wkhtmltopdf reported an error: Loading pages (1/6) QSslSocket: cannot resolve CRYPTO_num_locks ] 10% QSslSocket: cannot resolve CRYPTO_set_id_callback QSslSocket: cannot resolve CRYPTO_set_locking_callback QSslSocket: cannot resolve sk_free QSslSocket: cannot resolve sk_num QSslSocket: cannot resolve sk_pop_free QSslSocket: cannot resolve sk_value QSslSocket: cannot resolve SSL_library_init QSslSocket: cannot resolve SSL_load_error_strings QSslSocket: cannot resolve SSLv3_client_method QSslSocket: cannot resolve SSLv23_client_method QSslSocket: cannot resolve SSLv3_server_method QSslSocket: cannot resolve SSLv23_server_method QSslSocket: cannot resolve X509_STORE_CTX_get_chain QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf QSslSocket: cannot resolve SSLeay QSslSocket: cannot call unresolved function CRYPTO_num_locks QSslSocket: cannot call unresolved function CRYPTO_set_id_callback QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback QSslSocket: cannot call unresolved function SSL_library_init QSslSocket: cannot call unresolved function SSLv23_client_method QSslSocket: cannot call unresolved function sk_num QSslSocket: cannot call unresolved function SSLv23_client_method0% QSslSocket: cannot call unresolved function SSL_library_init Counting pages (2/6) Resolving links (4/6) Loading headers and footers (5/6) Printing pages (6/6) Done Exit with code 1 due to network error: UnknownNetworkError QSslSocket: cannot call unresolved function CRYPTO_num_locks QSslSocket: cannot call unresolved function CRYPTO_set_id_callback QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback

kageurufu commented on 2016-11-22 15:39 (UTC)

ARM binaries are not provided by the upstream packager. This is a binary source package, You might check this wkhtmltopdf issue https://github.com/wkhtmltopdf/wkhtmltopdf/issues/1868 for information on cross-compiling for ARM

benoliver999 commented on 2016-11-22 15:01 (UTC)

Does anyone know how to compile this for ARM? Specifically armv7h

kageurufu commented on 2015-11-18 00:14 (UTC)

Specifically, its statically linked to a patched QT library with support for headless rendering. The community/wkhtmltopdf package requires a X server running.

phillid commented on 2015-11-17 23:30 (UTC)

It is statically linked for all the qt stuff. Compare `ldd /usr/bin/wkhtmltopdf` with the package in the repos and this package to see what has been statically linked.

Nowaker commented on 2015-11-17 23:04 (UTC)

Why does it require a dynamic library to work? "wkhtmltopdf-static" suggests it's static, not dynamic.

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »