[pyicu-dev] setup.py? Eggs?

[Andi Vajda]

On Wed, 30 Nov 2005, Jim Fulton wrote:

> Andi Vajda wrote:
>> 
> ...
>> The other kink is that there is a shared library being built that is not a 
>> python extension. The reason for it is that I couldn't find any other way 
>> for all the other python extensions in PyICU to share common code on the 
>> Mac. On Mac OS X, python extension are bundles and you cannot link a bundle 
>> with another bundle.
>> Another option was to make all extensions be just one, and that is the way 
>> I started the project, but the SWIG generated C++ code just became too 
>> large.
>
> Why does it matter how large the C++ code is?

Because it eventually takes gcc wayyyy to long to compile the file (10 
minutes) and it may even have choked.

> Is it feasible to statically link the common code into each
> extension?

This common code is define in common.cpp. There are few string conversion 
functions in there for which I'm pretty sure this would be possible.
There also is a C++ exception defined in there that I don't know if it is 
possible to duplicate since I don't know how exception catching would work 
across modules with the same exception statically defined in multiple places 
(I reach my meagre C++ knowledge quite fast).

Andi..