On Apr 11, 2012, at 11:04 AM, Daniel Macks <dma...@netspace.org> wrote:
> Isn't the actual only difference between "framework" and "library" the > difference between using -F/-framework vs -L/-l flags when linking? And the > binary library inside .framework is really just a .dylib by a different > filenaming scheme. I can't envision any way that the linker flags or > filename/location could have any runtime effect at all, or that any > runtime-loading or configure-detection/makefile recipe couldn't just have its > flags changed to the normal-lib way. > dan Yes, it's just a matter of packaging. I'd bet though that wxcocoa assumes that python is always a framework on OS X and only looks there. It'll probably need patching. Now there is another difference between fink's and system python; the system's uses system tcltk which uses cocoa while fink's uses fink's tcltk which uses x11. I don't know if that's an issue. In any case, changing our python packages would require changing all packages that link to them. That's a lot more work than fixing one package. :) Daniel ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
