Ben Abbott wrote: > It is has been suggested that the SuiteSparse static libraries be > converted to dynamic libraries instead.
Why are they static? Are they shared libraries on other platforms? Who suggested the change? > > Rather than attempt to modify the makefiles directly, I'd like to > try to directly convert the static libraries to dynamic ones. > > My thought is to do something like > > # Extract the object files from the static library. > ar -x libamd.a > # Build the dynamic version of the library. > gcc -dynamiclib -arch_only `/usr/bin/arch` -o libamd.dylib *.o Change to libamd.0.dylib and you would also want to add -install_name $libdir/libamd.0.dylib. Please use a symlink so that the package can be splitoff correctly into -dev and -shlibs packages. Are the objects in the static archive built with any options? Specifically -fast or -mdynamic-no-pic? If so, this strategy will not work. > > I have no practical experience with building libraries, and thought > it a good idea to inquire here. > > Can anyone tell me what options are needed, desired, > recommended, etc? If they static library is fat, ar x will not work. If they are not fat, you do not need to add -arch_only. Peter -- Peter O'Gorman http://pogma.com ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Fink-devel mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.devel
