Steve,
Steve M. Robbins wrote:
It turns out to be simpler than that. With a small tweak to boost's
Jamroot file, I'm now generating libraries without the toolset and
without the Boost version decorations. I will use this for the
upcoming Boost 1.35.0 Debian packages.
By all means, could you
On Thu, May 01, 2008 at 10:30:32AM -0400, David Abrahams wrote:
>
> on Thu Mar 13 2008, "Steve M. Robbins" wrote:
>
> > Actually, the only thing about Boost that causes grief to packagers is
> > that the toolset name (e.g. "gcc42") is embedded in the library
> > filename. I just wrote a respons
on Thu Mar 13 2008, "Steve M. Robbins" wrote:
> Actually, the only thing about Boost that causes grief to packagers is
> that the toolset name (e.g. "gcc42") is embedded in the library
> filename. I just wrote a response on Boost.Build outlining this in
> some detail [1]. Embedding the compile
on Sat Feb 23 2008, "Steve M. Robbins" wrote:
> Hi,
>
> I'm part of the Debian Boost packaging team, seeking some guidance on
> how to build and install Boost.Python so that it is usable with all
> Python versions shipped in Debian. Debian currently ships Python 2.4
> and 2.5.
>
> When reading
On Wed, Mar 12, 2008 at 09:11:25PM -0400, David Abrahams wrote:
>
> on Sat Feb 23 2008, "Steve M. Robbins" wrote:
[...]
> > This produces pairs of library files such as
> >
> > bin.v2/.../link-static/libboost_python-gcc42-1_34_1.a
> > bin.v2/.../link-static/python-2.5/libboost_pytho
On Wed, Feb 27, 2008 at 08:43:43AM -0500, Stefan Seefeld wrote:
> (I still don't see the problem: Source packages don't depend on binary
> packages, only binary packages do.
Source packages *do*, in fact, depend on binary packages. Each source
package describes exactly the packages required t
Le mardi 26 février 2008 à 22:04 -0600, Steve M. Robbins a écrit :
> The idea is to create a single -dev package that contains the
> following in /usr/lib:
>
> libboost_python-py24-gcc42-1_34_1.so
> libboost_python-py24-gcc42-1_34_1.a
>
> libboost_python-py25-gcc42-1_34_1.
Steve M. Robbins wrote:
On Tue, Feb 26, 2008 at 11:15:24PM -0500, Stefan Seefeld wrote:
Steve M. Robbins wrote:
Hi,
Thanks to Steve, Bernd, and Josselin for ideas.
On Sat, Feb 23, 2008 at 09:17:24PM -0800, Steve Langasek wrote:
Decorate only the shared library names with the python version
Hi,
On Tue, Feb 26, 2008 at 10:04:26PM -0600, Steve M. Robbins wrote:
>
> On Mon, Feb 25, 2008 at 01:15:31PM +0100, Josselin Mouette wrote:
> >
> > The solution is to keep the names decorated with both python versions,
> > but to maintain a farm of symbolic links pointing to the current python
>
On Tue, Feb 26, 2008 at 10:04:26PM -0600, Steve M. Robbins wrote:
> On Sat, Feb 23, 2008 at 09:17:24PM -0800, Steve Langasek wrote:
> > Decorate only the shared library names with the python versions, and retain
> > the current names for the .a files and .so symlinks - with two separate -dev
> > p
On Tue, Feb 26, 2008 at 11:15:24PM -0500, Stefan Seefeld wrote:
> Steve M. Robbins wrote:
> > Hi,
> >
> > Thanks to Steve, Bernd, and Josselin for ideas.
> >
> >
> > On Sat, Feb 23, 2008 at 09:17:24PM -0800, Steve Langasek wrote:
> >
> >> Decorate only the shared library names with the python v
Steve M. Robbins wrote:
Hi,
Thanks to Steve, Bernd, and Josselin for ideas.
On Sat, Feb 23, 2008 at 09:17:24PM -0800, Steve Langasek wrote:
Decorate only the shared library names with the python versions, and retain
the current names for the .a files and .so symlinks - with two separate -dev
Hi,
Thanks to Steve, Bernd, and Josselin for ideas.
On Sat, Feb 23, 2008 at 09:17:24PM -0800, Steve Langasek wrote:
> Decorate only the shared library names with the python versions, and retain
> the current names for the .a files and .so symlinks - with two separate -dev
> packages that confli
Hi,
Le samedi 23 février 2008 à 22:45 -0600, Steve M. Robbins a écrit :
> One idea is to use a user-config.jam file containing
>
> using python : 2.4 : /usr ;
> using python : 2.5 : /usr ;
>
> Then run jam twice
>
> bjam variant= ...
> bjam variant= ... python python=2.5
Hi,
I'd suggest to do
> 3. Put the libraries in different subdirectories, e.g.
>
> /usr/lib/python2.4/libboost_python-gcc42-1_34_1.a
> /usr/lib/python2.5/libboost_python-gcc42-1_34_1.a
and add a symlink to /usr/lib which points to the library version for
the current default python v
On Sat, Feb 23, 2008 at 10:45:18PM -0600, Steve M. Robbins wrote:
> The question, then, is how to distinguish them once installed?
> Should we:
[...]
> The drawback to all these approaches is that client code has to be
> adjusted to build on Debian.
Decorate only the shared library names wit
Hi,
I'm part of the Debian Boost packaging team, seeking some guidance on
how to build and install Boost.Python so that it is usable with all
Python versions shipped in Debian. Debian currently ships Python 2.4
and 2.5.
When reading the following, keep in mind that Boost.Python is not a
Python e
17 matches
Mail list logo
