On Mar 5, 2006, at 5:56 PM, Zachary Pincus wrote:
> Otherwise, Mac Python's bundle loading code should have a way to
> expose the global symbol loading mechanism (necessary for C++ RTTI
> with templates) to user code. There are two ways that I imagine
> this could be added:
>
> (1) Provide
Thanks again Bob for the feedback.
> MH_BUNDLE is not MH_DYLIB and neither are ELF. Everything you
> think you know about shared libraries isn't quite the same on Mac
> OS X. I suggest you read up on Mach-O, I don't really have time to
> answer all of your questions about it.
My admittedl
On Mar 5, 2006, at 4:16 PM, Zachary Pincus wrote:
> Thanks for the information, Bob. I appreciate your help.
>
>> Actually it's because Python extensions are bundles. Bundles are
>> NOT shared libraries and can not do what you want. Additionally,
>> Python on Mac OS X doesn't use dl to load its
Thanks for the information, Bob. I appreciate your help.
> Actually it's because Python extensions are bundles. Bundles are
> NOT shared libraries and can not do what you want. Additionally,
> Python on Mac OS X doesn't use dl to load its extensions, it uses
> lower-level means... so the R
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
has anybody tried to build the ICE Library for python under mac osx
10.4.5.
I have configured the env with:
declare -x DYLD_LIBRARY_PATH=":/share/Projekte/network/Ice-3.0.1/lib"
declare -x ICE_HOME="/share/Projekte/network/Ice-3.0.1"
declare -
On Mar 5, 2006, at 12:32 PM, Zachary Pincus wrote:
>>> [need to share symbols across dso boundaries snipped]
>>> Any help or suggestions or thoughts would be greatly appreciated,
>>
>> Don't do that?
>>
>> Python uses two-level namespaces on OSX, and for a purpose: to avoid
>> accidentally pickin
>> [need to share symbols across dso boundaries snipped]
>> Any help or suggestions or thoughts would be greatly appreciated,
>
> Don't do that?
>
> Python uses two-level namespaces on OSX, and for a purpose: to avoid
> accidentally picking up a symbol from another extension. IIRC You
> should
>
On Mar 5, 2006, at 5:52 AM, has wrote:
> Bob wrote:
>
>>> Just wondering what progress (if any) there's been on fixing the
>>> endian bugs in PyMac_GetOSType and PyMac_BuildOSType?
>>>
>>> https://sourceforge.net/tracker/?
>>> func=detail&atid=305470&aid=1218421&group_id=5470
>>
>> That's been
Am 2006-03-05 um 08:04 schrieb Brendan Simons:
> For interest's sake, here's the one I tried to do. (I'm not
> advocating it, but I put so much work into it ;)
>
> http://twototango.blogs.com/PythonLauncherBlech.tiff
How about some Jack-in-the-box python icon for the Launcher?
(i mean: snake wit
Bob wrote:
>>Just wondering what progress (if any) there's been on fixing the endian bugs
>>in PyMac_GetOSType and PyMac_BuildOSType?
>>
>>https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1218421&group_id=5470
>
>That's been fixed in the universal branch for some time now.
Cool. Mind
On 5-mrt-2006, at 8:46, Zachary Pincus wrote:
> Hi folks,
>
>
> Any help or suggestions or thoughts would be greatly appreciated,
Don't do that?
Python uses two-level namespaces on OSX, and for a purpose: to avoid
accidentally picking up a symbol from another extension. IIRC You should
build a
Hi folks,
I have a tricky issue with some python extension modules that need to
share symbols between themselves.
The setup: I am creating python modules to wrap a large template-
based C++ image processing library. The fundamental class that each
of these modules needs to be able to create,
12 matches
Mail list logo
