[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyKDE] [PATCH] Compiling SIP with distutils
From:       "Phil Thompson" <phil () riverbankcomputing ! co ! uk>
Date:       2005-10-27 13:38:52
Message-ID: 48492.194.203.13.71.1130420332.squirrel () river-bank ! demon ! co ! uk
[Download RAW message or body]

> Phil Thompson <phil@riverbankcomputing.co.uk> wrote:
>
>> Is the swig_sources() method so called because it hooks into standard
>> wrapper support in distutils? Or were you just trying to hurt my
>> feelings?
>> :)
>
> Eheheh no, that's the hook point into distutils (which already supports
> SWIG). It's obviously the best place :)
>
>> You can get the name of the sip executable from the sipconfig module.
>
> Ah, which one exactly? _pkg_config["sip_bin"] + platform-dependent
> extension? Isn't _pkg_config private of the module (given the name)?

Instantiate the Configuration class and sip_bin becomes an attribute. You
shouldn't need a platform-dependent extension - unless that's a distutils
requirement.

>> Should this be added to sipconfig.py rather than being a separate
>> module?
>
> Yes, it's probably a better place. I believe the next step would be
> compiling SIP itself with distutils. After that, SIP will be totally
> distutils based, so your custom build engine could be moved into PyQt
> only.
> I reckon this could ease adoption of SIP as a general wrapping tool.

Maybe it should be kept separate then - so that it has a name that makes
the most sense in the long term.

>> Any chance of some documentation?
>
> Within sipref.txt? Sure, I can write something if you agree on getting
> this
> included.

Thanks,
Phil

_______________________________________________
PyKDE mailing list    PyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[prev in list] [next in list] [prev in thread] [next in thread]