Skip to content

Skipping lib2bit.a and using only lib2bit.so? [Documentation issue mostly I think] #7

@rubyFeedback

Description

@rubyFeedback

Hey there,

Right now when doing "make" and "make install" we instlal both
lib2bit.a and lib2bit.so. I am not sure I will need the lib2bit.a
though. Would there be a possibility to add a flag to the
Makefile, e. g. to skip building the .a file or remove it?

It's not a big issue - I can manually remove the .a file or
do so via scripts (e. g. ruby compiling lib2bit for me,
and then at post-installation remove the lib2bit.a file).

Rationale: Personally I try to use .so files when possible,
unless it is a statically compiled program. I have had
some issues with .a files before, in particular "relocation
errors" due to -fPIC, such as in bzip2.a or similar files. But
as said, it's no big deal, I can remove it just fine after
make install.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions