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 On Wed, 11 Apr 2012 10:43:46 -0400, Jack Howarth <howa...@bromo.med.uc.edu> wrote: Daniel and Daniel, > While creating test packaging for a wxcocoa923-py package for use > with relax-py, I discovered that the cocoa build of wxPython 9.2.3.1 > issues an error message, when running its demos, that access to the > screen requires a framework build of python for the cocoa support. > Since MacPorts already builds their pythons as frameworks, I'll > continue testing there to make sure that the resulting wxPython > with cocoa support is fully functional. If it is, we really might > want to consider switching our python packages over to framework > builds as well in order to be able to use the upcoming cocoa support > in such packages as wxPython. > Jack > > -- Daniel Macks dma...@netspace.org ------------------------------------------------------------------------------ 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
