[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [DotGNU]Mac OS X PInvoke question

From: Mario D . Santana
Subject: Re: [DotGNU]Mac OS X PInvoke question
Date: Tue, 9 Sep 2003 12:16:35 -0400


The main difference between OS X frameworks and "normal" dylibs is their location. Frameworks adhere to the Mac paradigm that every piece of software should be in its own little, independent package. So instead of having your different files spread out over the filesystem, you've got everything -- dylibs, headers, docs, etc -- in one subdirectory off .../Frameworks/ somewhere. Then you give the -framework argument to gcc and go to town.

For enlightenment, `ls -l /System/Library/Frameworks/AppKit.framework/Versions/Current/'

(There are also some subtle differences that play into OS X's whole two-level namespace thing, and an extra feature or two for fascist dependency enforcement, but they're fairly esoteric. `man ld' for details.)



On Tuesday, Sep 9, 2003, at 10:36 US/Eastern, Mark Easton wrote:

I've just been looking into getting PythonNet running on PNET 0.5.10
under Mac OSX and have a quick question that I'm hoping someone will

PythonNet relies on the Python shared library which is python22.dll on
Win32, on GNU/Linux and libpython2.2.dylib on Mac OSX.
I was just investigating the issue when I got told it's preferable to
use Mac OSX framework libraries than natural shared libraries.

Now I'm guessing that there ain't a virgin's chance in hell of these hi
falutin' framework libraries being usable from PNET's PInvoke (or anyone else's PInvoke for that matter) but if there's someone out there who has
been playing with PNET's PInvoke on Mac OSX (if indeed such a thing
works) or someone that knows their framework libraries from their elbow,
then please could you give me a shove in the right direction



Developers mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]