[BioLib-dev] Need to link another library gsl

Xin Shuai xshuai at umail.iu.edu
Mon Aug 3 14:36:32 UTC 2009


On Sun, Aug 02, 2009 at 10:36:27AM -0400, Xin Shuai wrote:
> Hi:   I'm still in the process of debugging and testing. I found that , in
> addition to Boost++ library, gsl library is also needed.
>    I tracked the location of gsl library and found it in
> /usr/local/lib/libgsl.dylib.

Hmmm. How much does it use? I have also the Scilib project, similar
to Biolib, which includes the GSL sources. I really dislike linking
against shared libraries for critical functionality. Prefer sources,
so it is one system and bugs can be tagged against one set of
versions. The only exception I am making now are Rlib and zlib.

>    Generally, any lib that is located in /usr/lib and /usr/local/lib
should
> be automatically found by CMake. But my program cannot find it. Thus I
have
> import error when I import libsequence library in Python. I guess the
reason
> is that CMake only recognize library with .so suffix (Unix) But not
library
> with .dylib(Mac). Since I met the similar situation at the beginning of
> project.

Finding is no problem, just takes a bit of hacking. I don't have OSX,
that complicates it for me. But we can find solutions if required.

>     Therefore, I think the solution is to add some hacking to let CMake
> recognize .dylib when Linking other library. How do you think of my
> thoughts? Can you give me some advice?

At this stage I favour including the source tree. Can you check what
functions libsequence really uses from the GSL?

Pj.



-- 
Xin Shuai (David)
PhD of Complex System in School of Informatics
Indiana University Bloomington
812-606-8019



More information about the BioLib-dev mailing list