Checking for the last symbol is a valid solution but I wonder if checking for a version number would be easier to maintain. Perhaps using PKG_CHECK_MODULES as we do with other dependencies:
Thanks, committed in [b31c65]. The info was a bit outdated. PKG_CONFIG_PATH is prefered when doing a native compile as extends the search path with a local one. PKG_CONFIG_LIBDIR is prefered when cross-compiling as overrides the search path and ignores incompatible libraries.
Also suggested in [feature-requests:#78].
Checking for the last symbol is a valid solution but I wonder if checking for a version number would be easier to maintain. Perhaps using PKG_CHECK_MODULES as we do with other dependencies:
PKG_CHECK_MODULES([LIBSPECTRUM],[libspectrum >= 1.3.5], ...)That would need that libspectrum deploy a .pc file.
Related
Feature Requests:
#78Something like this?
Yep, something like that :-)
There isn't need to add a custom rule to build libspectrum.pc, though.
Is this right for updated Win32 build instructions?
Thanks, committed in [b31c65]. The info was a bit outdated. PKG_CONFIG_PATH is prefered when doing a native compile as extends the search path with a local one. PKG_CONFIG_LIBDIR is prefered when cross-compiling as overrides the search path and ignores incompatible libraries.
Related
Commit: [b31c65]
Thanks Sergio, looks good to me!