Re: [Boost-build] How to deal with debug-python?

From: Boris Gubenko (Boris.Gubenko_at_[hidden])
Date: 2007-03-22 12:18:39

David Abrahams wrote:
> [...]                Should the suffix be a feature?

I think, it is a good idea. On HP-UX, the suffix is a function of
python version: starting with Python 2.5, python uses .so suffix
while pre-2.5 versions use .sl suffix.

I've submitted a patch for python.jam which, for HP-UX, determines
the suffix based on python version. If the suffix was a feature, no
run-time selection would be necessary. The patch has not been applied
and now, after python.jam was almost completely revamped, this patch
is irrelevant.

Since I'm using Python 2.5 for boost testing on HP-UX, this is not an
issue for me. It can be an issue for HP customers using python version
prior to 2.5. Making suffix a feature would solve this problem.

Thanks,
  Boris

----- Original Message ----- 
From: "David Abrahams" <dave_at_[hidden]>
To: <boost-build_at_[hidden]>
Sent: Thursday, March 22, 2007 11:47 AM
Subject: [Boost-build] How to deal with debug-python?

>
> I've recently discovered that ubuntu has a python-dbg package that,
> unlike every other *nix installation, helpfully follows the Windows
> convention of requiring the "_d" suffix on extension modules
> (https://wiki.ubuntu.com/PyDbgBuilds).
>
> There doesn't seem to be any way to probe for that, so we need a way
> to allow the user to specify a suffix that will be added to extension
> module names for a particular installation of python (assuming that
> multiple pythons can be configured).  I'm not sure about the correct
> way to handle this.  Should the suffix be a feature?
>
> -- 
> Dave Abrahams
> Boost Consulting
> www.boost-consulting.com
>
> _______________________________________________
> Unsubscribe & other changes: 
> http://lists.boost.org/mailman/listinfo.cgi/boost-build
>
>