Bug 457 – PYTHON_INCLUDE_DIR not set with older cmake

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 457 - PYTHON_INCLUDE_DIR not set with older cmake

Summary:

PYTHON_INCLUDE_DIR not set with older cmake

Status:	CLOSED FIXED

Product:	PySide
Classification:	Unclassified
Component:	Shiboken
Version:	HEAD
Platform:	Other Linux

Importance:	P3 critical
Assigned To:	Marcelo Lira

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-11-03 14:36 EET by Daniel Ashbrook
Modified:	2010-11-25 17:48 EET (History)
CC List:	8 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Daniel Ashbrook 2010-11-03 14:36:02 EET

I'm compiling the latest PySide for N900 using scratchbox. However, the Maemo
repositories have cmake version 2.6-patch 3, which (as far as I can make out)
has an older FindPythonLibs that doesn't set PYTHON_INCLUDE_DIR. This means
when compilation gets to PySide, it tries to use SHIBOKEN_PYTHON_INCLUDE_DIR,
which never got set, and compilation fails. The easy fix is to add
-DPYTHON_INCLUDE_DIR=/usr/include/python2.5 to the cmake command line, but this
probably shouldn't be required.

Comment 1 renato filho 2010-11-19 13:55:15 EET

changing importance to critical to get this fixed before the next release.

Comment 2 Marcelo Lira 2010-11-22 09:45:45 EET

Fixed in Shiboken/fb636656.

Comment 3 renato filho 2010-11-25 17:48:22 EET

released on 1.0.0~beta1