SWIG problem -> solved

Hi,

the hinted problems of wrong version and threads where not
the cause. Linking 
on OSX is a very diverse subject and I did some trial and
error for a simple 
example. The final solution was -flat_namespace.

Cheers, Torsten

_______________________________________________
Pythonmac-SIG maillist  -  Pythonmac-SIGpython.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

On Sep 11, 2006, at 5:31 PM, Torsten Sadowski wrote:

> Hi,
>
> the hinted problems of wrong version and threads where
not the  
> cause. Linking
> on OSX is a very diverse subject and I did some trial
and error for  
> a simple
> example. The final solution was -flat_namespace.

Which may or may not be the right solution. -flat_namespace
is often  
an indication that you're doing something wrong .

The error-message in your original message seems to indicate
that  
you're linking the extension with python and the wrong one
at that.  
This causes two python libraries to be loaded, the one used
by the  
interpreter (which is correctly initialized) and one linked
by the  
extension (which isn't).

Are the python extension build using distutils? Distutils
should do  
the right thing automaticly.

Ronald

_______________________________________________
Pythonmac-SIG maillist  -  Pythonmac-SIGpython.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

On Sep 11, 2006, at 5:31 PM, Torsten Sadowski wrote:

> Hi,
>
> the hinted problems of wrong version and threads where
not the  
> cause. Linking
> on OSX is a very diverse subject and I did some trial
and error for  
> a simple
> example. The final solution was -flat_namespace.

Which may or may not be the right solution. -flat_namespace
is often  
an indication that you're doing something wrong .

The error-message in your original message seems to indicate
that  
you're linking the extension with python and the wrong one
at that.  
This causes two python libraries to be loaded, the one used
by the  
interpreter (which is correctly initialized) and one linked
by the  
extension (which isn't).

Are the python extension build using distutils? Distutils
should do  
the right thing automaticly.

Ronald

_______________________________________________
Pythonmac-SIG maillist  -  Pythonmac-SIGpython.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Am Dienstag, 12. September 2006 08:44 schrieben Sie:
> On Sep 11, 2006, at 5:31 PM, Torsten Sadowski wrote:
> > Hi,
snip
> > example. The final solution was -flat_namespace.
>
> Which may or may not be the right solution.
-flat_namespace is often
> an indication that you're doing something wrong .
>
> The error-message in your original message seems to
indicate that
> you're linking the extension with python and the wrong
one at that.
> This causes two python libraries to be loaded, the one
used by the
> interpreter (which is correctly initialized) and one
linked by the
> extension (which isn't).
>
> Are the python extension build using distutils?
Distutils should do
> the right thing automaticly.
>
> Ronald

Hello, 

unluckily the software I'm trying to port does not use
distutils but an 
automake system which means I have more or less to guess how
to make it work.

I built my simple example again with distutils just to see
what it does and it 
uses -undefined dynamic_lookup what of course depends on the
deployment 
target. With both solutions I can use the extension with all
installed 
pythons (Apple 2.3.5, Framework 2.4.1 and Fink 2.4.2).

Cheers, Torsten

_______________________________________________
Pythonmac-SIG maillist  -  Pythonmac-SIGpython.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Am Dienstag, 12. September 2006 08:44 schrieben Sie:
> On Sep 11, 2006, at 5:31 PM, Torsten Sadowski wrote:
> > Hi,
snip
> > example. The final solution was -flat_namespace.
>
> Which may or may not be the right solution.
-flat_namespace is often
> an indication that you're doing something wrong .
>
> The error-message in your original message seems to
indicate that
> you're linking the extension with python and the wrong
one at that.
> This causes two python libraries to be loaded, the one
used by the
> interpreter (which is correctly initialized) and one
linked by the
> extension (which isn't).
>
> Are the python extension build using distutils?
Distutils should do
> the right thing automaticly.
>
> Ronald

Hello, 

unluckily the software I'm trying to port does not use
distutils but an 
automake system which means I have more or less to guess how
to make it work.

I built my simple example again with distutils just to see
what it does and it 
uses -undefined dynamic_lookup what of course depends on the
deployment 
target. With both solutions I can use the extension with all
installed 
pythons (Apple 2.3.5, Framework 2.4.1 and Fink 2.4.2).

Cheers, Torsten

_______________________________________________
Pythonmac-SIG maillist  -  Pythonmac-SIGpython.org
http://mail.python.org/mailman/listinfo/pythonmac-sig