[ python-Bugs-1016626 ] distutils support for swig is under par
SourceForge.net
noreply at sourceforge.net
Fri Oct 15 20:07:06 CEST 2004
Bugs item #1016626, was opened at 2004-08-26 11:11
Message generated for change (Comment added) made by sjoerd
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1016626&group_id=5470
Category: Distutils
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Sjoerd Mullender (sjoerd)
Assigned to: Nobody/Anonymous (nobody)
Summary: distutils support for swig is under par
Initial Comment:
To my delight there is support for swig built into
distutils. However a few problems exist with the support.
- there is no way to specify any extra flags to the
swig command (I need -I/usr/include -DHAVE_LONG_LONG);
- swig generates two files, the XXX_wrap.c file which
is turned into a _XXX.so file, and a XXX.py file.
distutils only deals with the XXX_wrap.c file.
I have no suggested fix for these problems, but
problems they are.
(Python from CVS HEAD on Fedora Core 2).
----------------------------------------------------------------------
>Comment By: Sjoerd Mullender (sjoerd)
Date: 2004-10-15 20:07
Message:
Logged In: YES
user_id=43607
Hmm, you can't really call that "decent swig support" then,
can you?
If this "solution" were properly documented (in a place one
would notice when trying to create a setup.py to do swig!)
then it wouldn't be too much of a problem, but I wouldn't
know where that would be.
So, if my change doesn't cause any detrimental effects I'd
much rather see it fixed that way.
----------------------------------------------------------------------
Comment By: Thomas Heller (theller)
Date: 2004-10-15 17:34
Message:
Logged In: YES
user_id=11105
Haven't read the original problem (I don't use swig myself),
but if changing the order of the sub_commands list than it
can as well be done in the setup script by installing a
custom build command.
----------------------------------------------------------------------
Comment By: Sjoerd Mullender (sjoerd)
Date: 2004-10-15 16:37
Message:
Logged In: YES
user_id=43607
I just came up with a possible solution:
In command/build.py change the order of the
build.sub_commands list and put the entry for build_ext
before build_py.
The question is, does this cause a problem for anybody?
----------------------------------------------------------------------
Comment By: Sjoerd Mullender (sjoerd)
Date: 2004-10-15 16:27
Message:
Logged In: YES
user_id=43607
Part of the problem described here (the extra options that
need to be given to swig) is solved by [ 1046644 ] improving
distutils swig support (2). However, the other part is
still a problem.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1016626&group_id=5470
More information about the Python-bugs-list
mailing list