#21824: python26 framework broken ---------------------------------+------------------------------------------ Reporter: stromnov@… | Owner: blb@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.8.1 Resolution: invalid | Keywords: Port: python26 | ---------------------------------+------------------------------------------ Comment(by stromnov@…): When port is native MacOSX application that need explicit linkage with framework, we can link that application against fake framework, something like this (last lines in python_select sequence): {{{ PortGroup python25 ... set fwkdir ${workdir}/Frameworks/Python.framework cd ${workdir} mkdir -p ${fwkdir}/Versions ln -s ${prefix}/Library/Frameworks/Python.framework/Versions/2.5 ${fwkdir}/Versions/Current ln -s ${prefix}/Library/Frameworks/Python.framework/Versions/2.5/Headers ${fwkdir}/Headers ln -s ${prefix}/Library/Frameworks/Python.framework/Versions/2.5/Resources ${fwkdir}/Resources ln -s ${prefix}/Library/Frameworks/Python.framework/Versions/2.5/Python ${fwkdir}/Python ... CFLAGS+=-F${fwkdir} -framework Python ... }}} Every port, that installed as framework, can store (in registry?) some meta information for creating fake framework at build time. -- Ticket URL: <http://trac.macports.org/ticket/21824#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS