[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#679990: ITP: clipper -- object oriented development kit for crystallographic computing

On Thu, 05. Jul 16:11, Baptiste Carvello wrote:
> I'm a little bit lost here, I did not even think that they use libtool.
I think what Fred meant is that they need to start thinking about versioning
their libs and libtool is a nice example here.
> That's also my opinion. At least, a static library can be shared with
> other packages which build-depend on us.
But then only the python interface would work. Other packages depending on the
c++ interface wouldn't work. I found this wiki entry[1] where I'm reading:

""Currently, the only generally accepted use of this feature in Debian is to add
non-standard library path (like /usr/lib/<package>) to libraries that are only
intended to be used by the executables or other libraries within the same source

So either with rpath nor static linking we can provide libs for objcryst-fox
with our package

> It's not that much debtree as it is Graphviz. I made a quick python
> script to parse the libtbx_config files and generate the graph. I
> attached the script and the result to the wiki page. Red boxes are
> python modules, green boxes are others (C++ or external). Black arrows
> are run-time dependancies, red are build-time, green are optional.
Great! But I don't see anything on the wiki page yet...

[1] http://wiki.debian.org/RpathIssue

Reply to: