How about patching the paths, s.t. it can nicely included by default with e.g. "bamtools/api/Reader.h" and no include paths need to be provided manually?
It would be as simple as adding this patching to the prepare():
sed -i "s/api\//bamtools\/api\//g" $(find $scrdir -name "*.h" -o -name "*.h")
mkdir -p src/$pkgname
[ ! -e src/$pkgname/api ] && ln -s $(realpath src/api) src/$pkgname/api
Search Criteria
Package Details: bamtools 2.4.1-1
| Git Clone URL: | https://aur.archlinux.org/bamtools.git (read-only) |
|---|---|
| Package Base: | bamtools |
| Description: | C++ API & command-line toolkit for working with BAM data |
| Upstream URL: | https://github.com/pezmaster31/bamtools |
| Licenses: | |
| Submitter: | stratust |
| Maintainer: | alexpe87 |
| Last Packager: | wookietreiber |
| Votes: | 3 |
| Popularity: | 0.000000 |
| First Submitted: | 2012-01-16 06:11 |
| Last Updated: | 2016-12-09 10:24 |
Dependencies (3)
- gcc-libs (gcc-libs-multilib-x32, gcc-libs-git, gcc-libs-multilib-git)
- zlib (zlib-asm, libz, zlib-git, zlib-static)
- cmake (cmake-git) (make)
@confusedfla: this package installs /usr/include/bamtools/api/BamReader.h - the problem is, that you need to
#include <bamtools/api/BamReader.h>
i.e. whith angle brackets, not double quotes. Double quotes should be used only for headers *within* your project, see https://stackoverflow.com/questions/21593/what-is-the-difference-between-include-filename-and-include-filename