Hi, On 26.10.2018 22:30, Maciej Suminski wrote:
> What about libngspice.so.0 symlink? Which package ships that? Anyway, it > makes sense to request a particular version of the library in case the > API changes in the future. The .so.0 symlink is created from the SONAME field in the library. This is the correct way to reference a library by ABI. > You are correct. The library used to be linked with eeschema, but we > have faced problems that could be resolved only by reloading the > library. I am afraid it has to stay this way for the time being. The packaging tools look for hard dependencies between ELF objects. Anything else needs to be specified explicitly (which is totally allowed). Do the SPICE people know about the problems? Simon
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
