Closed #257.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/257#event-1305239481___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Thanks but no thanks, a helper that's practically as long as our entire
configure.ac seems like a huge overkill with the relatively few external
dependencies we have.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://
The RPM+UUID patch in issue #269 illustrates another, more subtle usage feature
of RPM_CHECK_LIB.
There are two uuid.h files on a linux system: one from ossp-uuid, the other
from ext4.
Using --with-uuid=system (rather than --with-uuid=external) finds the correct
uuid.h.
Think about the hack-o
Here is a moderately complex real world example of how to use: detecting ZSTD
either externally or internally.
In configure.ac:
```
dnl # Facebook Zstd
RPM_CHECK_LIB(
[Facebook Zstd], [zstd],
[zstd], [ZSTD_versionNumber], [zstd.h],
[no,external:internal:none], [zstd:lib:lib],
[
The RPM_CHECK_LIB macro: add to acinclude.m4.
[rpm_check_lib.m4.gz](https://github.com/rpm-software-management/rpm/files/1156106/rpm_check_lib.m4.gz)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-sof
Projects that use autoconf are expected to detect build prerequisites and
libraries.
This usually leads to a set of ad hoc de facto m4 macros that deal with various
details like API and path incompatibilities, much of which is platform and os
and distro dependent.
Various standard tools (like
