In article ,
Louis Theran wrote:
>
>Is there a standard recipe for getting distutils to built universal .so
>files for modules that have C/C++ source?
You should check the archives of
http://mail.python.org/mailman/listinfo/pythonmac-sig
--
Aahz (a...@pythoncraft.com) <*> http
On 7/26/10 1:36 PM, Louis Theran wrote:
Is there a standard recipe for getting distutils to built
universal .so files for modules that have C/C++ source?
If your Python was built to be Universal, it will automatically use the same
architecture flags to build the extension modules Universal.
Joachim Dahl wrote:
> E.g., say I want to compile a project as:
>
> gcc -Ddef1 -c foo.c -o foo_def1.o
> gcc -Ddef2 -c foo.c -o foo_def2.o
> gcc foo_def1.o foo_def2.o -o myext_module.o
>
> How would I do that using distutils? It doesn't seem to be possible with
> the normal core.setup method, and d
On Wed, 07 Sep 2005 10:56:40 -0700, Joachim Dahl <[EMAIL PROTECTED]> wrote:
> I am trying to make a customized install script for an extension module
> using the distutils.ccompiler class.
>
> I want to embed an existing makefile for the C libraries into the Python
> setup script, but I am not su
Peter Hansen wrote:
>>How how can I install my .mo files from a distutil script into its
>>default location?
>>
>>sys.prefix + os.sep + 'share' + os.sep + 'locale'
>>
>>
>
>I can't answer the first question, but the latter should be written this
>way instead
>
>os.path.join(sys.prefix, '
Laszlo Zsolt Nagy wrote:
> How how can I install my .mo files from a distutil script into its
> default location?
>
> sys.prefix + os.sep + 'share' + os.sep + 'locale'
I can't answer the first question, but the latter should be written this
way instead
os.path.join(sys.prefix, 'share', 'lo
Le 16 Apr 2005 01:20:34 -0700, Qiangning Hong a écrit :
> To avoid namespace confliction with other Python packages, I want all
> my projects to be put into a specific namespace, e.g. 'hongqn' package,
> so that I can use "from hongqn.proj1 import module1", "from
> hongqn.proj2.subpack1 import modu
