A common practice is the static and dynamic versions of the library with the same name?

I downloaded the library (NAG c libraries), and both static and dynamic versions of the library have the same name (libnagc_nag). In the beginning, I had problems because I tried to link the static version in OS X and it uses a dynamic library by default, so I changed the file name to distinguish them (libnagc_nag_s.a and libnagc_nag_d.dylib for OS X and libnagc_nag_d.so on Linux). my question is: do they give the same name as normal practice? Even so, are there any problems or flaws in changing their names this way?

+3
source share
2 answers

Yes, this agreement has

 libNAME.a

and

 libNAME.so.VERS 

.a, . ? , .

-lnagc_nag_d LDFLAGS Makefile , .

+2

( )...

+3

All Articles