From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] zopfli-1.0.3_1 doesn't include shared libraries
Date: Thu, 21 Jan 2021 18:52:38 +0100 [thread overview]
Message-ID: <20210121175238.12POKExXby4IHj6dk72ORJIsYDaPuC3Uzi8Xwkwkl7I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23986@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
Closed issue by mrnoname1000 on void-packages repository
https://github.com/void-linux/void-packages/issues/23986
Description:
Zopfli builds shared and static libraries, but the build script doesn't install them. FYI, Zopfli's included makefile doesn't link the binaries with the shared libraries, but its cmake script does (if building the libraries, with -DZOPFLI_BUILD_SHARED=ON).
The below build script builds and installs everything, but I wasn't able to figure out the best way to package the necessary files separately in a -devel package.
```bash
# Template file for 'zopfli'
pkgname=zopfli
version=1.0.3
revision=2
wrksrc="${pkgname}-${pkgname}-${version}"
build_style=cmake
configure_args=-DZOPFLI_BUILD_SHARED=ON
short_desc="Very good, but slow, deflate or zlib compression"
maintainer="Leah Neukirchen <leah@vuxu.org>"
license="Apache-2.0"
homepage="https://github.com/google/zopfli"
distfiles="https://github.com/google/${pkgname}/archive/${pkgname}-${version}.tar.gz"
checksum=e955a7739f71af37ef3349c4fa141c648e8775bceb2195be07e86f8e638814bd
post_install() {
vlicense COPYING LICENSE
}
```
parent reply other threads:[~2021-01-21 17:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23986@inbox.vuxu.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210121175238.12POKExXby4IHj6dk72ORJIsYDaPuC3Uzi8Xwkwkl7I@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).