On 7 Oct 2020, at 14:16, Andreas Tille <andr...@fam-tille.de> wrote:
>
> On Wed, Oct 07, 2020 at 09:36:06AM +0000, John Marshall wrote:
>> --enable-plugins --with-plugin-dir='$(libdir)/htslib'
>> --with-plugin-path='/usr/local/lib/htslib:/usr/local/libexec/htslib:$(plugindir)'
>
> OK, that's in Git now
Great, thanks.
>> BTW it looks like htslib-s3-plugin.7.gz has ben placed in libhts3 basically
>> by default, although that is the right package for it.
>
> Sorry, I do not understand this sentence.
There are lines in libhts-dev.install (now libhts3.install -- thanks) for man5,
so I expected to see a line for man7 in some *.install file. But now I see
there are also *.manpages files which take care of this file. So never mind
then, my mistake.
>> How can I verify / test the correct setting?
>
> What exactly do you mean? Test my lastest changes I mentioned above or
> rather testing the package that is in unstable currently?
Sorry, this was a reply to your previous question but my mail client garbled
the exchange with its unintended rich text. You previously asked
Andreas> How can I verify / test the correct setting?
which I took to mean how do you verify that your plugin-dir and plugin-path
configure settings are effective, i.e., how does one verify what plugin
directories HTSlib is actually searching. And the answer is
By observing the -DPLUGINPATH=… setting that goes past in the log when plugin.c
is compiled; by running `strings` on libhts.so; or by seeing what directories
are scanned via e.g. `strace htsfile foo:bar 2>&1|grep O_DIRECTORY`.
(So no changes are needed. This is how you could check what plugin path
settings are burnt into the library if you wanted to.)
John
