I agree with Rainer all around. Apple uses frameworks, but most non-OSX-native projects do not & they generally work just fine when ported without frameworks to OSX. Qt and Python are two of the few exceptions of which I know that can do framework installs; I'm sure there are others. That said, I don't think you (generically) are require to install a framework-based library to use Aqua or Cocoa or whatever -- you just have to link correctly to get access to those OSX-internals. That's what we do in GNU Radio-land, and it seems to work just fine. I might be missing a few subtle details of the actual execution, but I think the over-arching concept is valid. - MLD
On Tue, 31 Aug 2010 18:07 +0200, "Rainer Müller" <[email protected]> wrote: > The only reason we ever switched to frameworks with python25 was to get > pythonw running. Otherwise that was only causing lots of troubles with > the paths as dependents were not using the correct way to determine > installation directories. > > Frameworks ought to be _relocatable_ and that is one of the main purpose > of them. But we are not able to provide this with MacPorts. So it's not > a reason to stick to a framework just because we are on a Mac. _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
