Skip to content

path to jellyfish includes #139

@rsharris

Description

@rsharris

I distribute a C++ package that links with the jellyfish library. I don't understand the proper way to access the .hpp files, as there seems to be an unusual extra layer in the path hierarchy.

After installing jellyfish, I find that the .h files are in ${HOME}/includes/jellyfish-2.2.10/jellyfish/*.hpp . For other packages, the paradigm is for installation to put them in ${HOME}/includes/some_package/*.hpp

If I add the usual -I${HOME}/includes to my compile command line, compilation (of MY package) fails at #include <jellyfish/mer_dna.hpp> because the path isn't right. I could make that <jellyfish-2.2.10 .jellyfish/mer_dna.hpp> and I assume that would work, but it seems like the wrong thing to do.

What I've been doing, after installation, is to make a symlink to hop past the jellyfish-2.2.10 level. This also seems like the wrong thing to do. Especially since anyone trying to build my package will also be expected to do that.

Nor do I really want to hardcode a jellyfish version number in my Makefile.

So my question is, what's the right way to do this?

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