Hi!
On Sun, Sep 11, 2011 at 12:59 PM, Jakub Wilk wrote:
> That could be simplified to:
> PYTHON_VERSION = $(shell pyversions -dv)
Not really. Because I want to compile package for different versions
of Python installed on the system I am passing PYTHON variable to make
in each loop. So I have to
On 09/10/2011 11:18 PM, Mitar wrote:
> Hi!
>
> On Sat, Sep 10, 2011 at 10:59 PM, Christian Kastner wrote:
>> The reason for this is that your build environment affects the resulting
>> binary package in various ways, one of them being the generated
>> dependencies, which is why you are seeing str
* Mitar , 2011-09-11, 04:48:
There are other problems with cmake Python support:
http://bugs.debian.org/580503
I solved this by passing CMAKE_USE_PYTHON_VERSION parameter to cmake:
PYTHON_VERSION = $(shell $(PYTHON) -c 'import sys; print "%s.%s" %
sys.version_info[:2]')
That could be simplif
Hi!
On Sun, Sep 11, 2011 at 1:56 AM, Jakub Wilk wrote:
> There are other problems with cmake Python support:
> http://bugs.debian.org/580503
I solved this by passing CMAKE_USE_PYTHON_VERSION parameter to cmake:
PYTHON_VERSION = $(shell $(PYTHON) -c 'import sys; print "%s.%s" %
sys.version_info[
* Mitar , 2011-09-11, 01:37:
I also see that we link against libpython which should not be done,
according to Debian Python Policy 2.1. But this is what cmake's
FindPythonLibrary.cmake find. Is there some generic way to change this?
I don't think there's any sane way. If you don't mind a bit o
Hi!
I also see that we link against libpython which should not be done,
according to Debian Python Policy 2.1. But this is what cmake's
FindPythonLibrary.cmake find. Is there some generic way to change
this?
Mitar
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subje
On 09/10/2011 05:04 PM, Mitar wrote:
> What I have done is installed Python 2.7 from wheezy so that package
> would be build for Python in stable (2.6) and for 2.7 (unstable,
> Ubuntu).
Unfortunately, that is not how building for multiple distributions works.
You need to have a separate build env
Hi!
On Sat, Sep 10, 2011 at 11:18 PM, Mitar wrote:
> Strange. I am just working on that and it compiles OK on stable? What
> exactly is missing?
I see. libqt4-opengl-dev is recommended by libqt4-dev and I have it
installed. Will fix this.
Mitar
--
To UNSUBSCRIBE, email to debian-python-requ
Hi!
On Sat, Sep 10, 2011 at 10:59 PM, Christian Kastner wrote:
> The reason for this is that your build environment affects the resulting
> binary package in various ways, one of them being the generated
> dependencies, which is why you are seeing strange things below.
Sure. But then I cannot ha
Hi!
On Fri, Jul 22, 2011 at 11:43 PM, Christian Kastner wrote:
> debian/rules
>
> build:
> # Get the supported Python versions
> PYVERS = $(shell pyversions -r -v)
>
> set -e -x;\
> for py in $(PYVERS); do \
> PYTHON=python$$py make -C sourc
On 07/22/2011 09:57 AM, Mitar wrote:
> I now saw that my Orange package is build just for Python 2.6.
>
> http://orange.biolab.si/debian/dists/squeeze/main/source/
>
> How can I make it be build also for 2.7?
1. Get a list of requested Python versions with pyversions(1)
2. Perform build with
11 matches
Mail list logo
