-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installs static libs instead of shared libs, for example lib/libncbi-vdb.a.2.11.0 #36
Comments
What problems does to cause? |
For example, here
all libs are static. There is no need to install same static library under different file names. |
Hi @yurivict - I would point out that your interpretation of the utility of the static links does not seem to take into account application linking at build time, which in some cases that we use will include a library's version, e.g. In our build system, we treat library names and versions separately from the static or shared nature of the package. So while you say there is no need because you assume the only use of symlinks is for the runtime link editor, we use them during the build. Which begs the question, what problem is it creating for you? |
It doesn't cause any particular problems so far except it looks broken to anybody used to look at shared library names. For example:
-- symbolic links are used for shared libraries, also in conjunction with shared library SONAMEs. |
Yes.
We'll take it into consideration. Thank you for your feedback. |
Version 2.11.0 installs static libs instead of shared libs:
This issue is similar to issue ncbi/ngs#33 in the
ngs
project.OS: FreeBSD 12.2
The text was updated successfully, but these errors were encountered: