On Fri, Mar 21, 2008 at 12:18:17PM -0500, Steve M. Robbins wrote:
I wrote about three weeks ago [1] that I'm trying to get Boost's
Python extension helper library building with multiple Python
versions. Several very helpful suggestions were made, for which I am
grateful.
I have been
On Mon, Mar 24, 2008 at 05:52:47PM +, Dominic Hargreaves wrote:
However, it looks to be like the shlibs file needs updating.
Yes, and thanks for the bug report. Upload is being prepared now.
-Steve
signature.asc
Description: Digital signature
On Fri, Mar 21, 2008 at 03:59:30PM -0400, Aaron M. Ucko wrote:
I do, however, see a couple of concrete issues with your script:
if [ $1 = -d ]; then
debug=-d
shift
fi
Shouldn't you fix that at build time à la $version?
You noticed a complication I was avoiding. There are
Steve M. Robbins [EMAIL PROTECTED] writes:
libraries, including the Boost.Python libraries. The only difference
in names is that the debug libraries have -d in them. So I was
avoiding two scripts by this parameterization.
Ah, thanks for clarifying; I had forgotten about the -dbg package,
Hello,
I wrote about three weeks ago [1] that I'm trying to get Boost's
Python extension helper library building with multiple Python
versions. Several very helpful suggestions were made, for which I am
grateful.
I have been plugging away, very slowly, ever since. I'm hoping to
upload it later
Steve M. Robbins [EMAIL PROTECTED] writes:
This allows extension builders to select either the default Python
version, or a specific version, without knowing the Boost
and GCC versions [2].
Yep; so far so good.
I'd like to ask about intended behaviour if a bad action is supplied.
Or if an
6 matches
Mail list logo
