|
From: Per P. <per...@ma...> - 2007-01-25 22:47:05
|
On Jan 25, 2007, at 19:30, Mojca Miklavec wrote: > But there are more serious problems, like libraries. If I build > gnuplot with fink, the user who wants to use it need the same fink's > libraries installed to be able to use it. Isn't that expected? Fink's job is to track dependencies and handle them for _you_. > Simply adding "-static" > doesn't help since all the libraries on the system should be build > static and for both architectures I assume. Well, -static won't help but of course you can statically link any required library which can be built as a static library. As an example, in a binary release, static linking of readline (or using builtin) is a must. For libs provided as part of OS X, always shared libs or "frameworks", we should use them. Any other functionality which relies on non-standard libs[1] (from an OS X point of view) should be statically linked. In fixing up the release script, we might as well do our homework properly and decide what should come from the system and what should be linked in statically (and what must be left out). [1] D'oh! I just realized that the one and only non-standard *framework* required is AquaTerm.framework. Can't link statically from frameworks AFAIK. Maybe we should supply the AquaTerm package as a sub-package[2] of gnuplot to be automagically installed if necessary? [2] Come to think of it, we could do that for other libs as well, but then again, we don't want to mess up people's computers do we? ;-) Best, Per |