Hi Mariah, On Jan 26, 6:21 pm, Mariah <mariah.le...@gmail.com> wrote: > I guess I do not understand that "usual drawbacks" to > statically linking to which you refer. Can you expand, please?
First off all it wastes disk space; I'm trying to make a TOPCOM spkg and a naive compile/make/make install will generate 200MB of binaries. The more serious issue is that you can't upgrade the libraries any more after they were statically linked. Or, rather, if you do then whoever linked to the library does not get updated. > I still am confused about what is not working in Sage. > Are you talking about a program external to Sage not being > able to dynamically link with the Sage libraries? Yes, exactly. In particular, you can't create new spkgs that dynamically link with existing spkgs. Cheers, Volker -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
