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.

First Last Prev Next    This bug is not in your last search results.
Bug 1035 - Error compiling PySide-Tools with Python 2.7.2 32bit on Windows
: Error compiling PySide-Tools with Python 2.7.2 32bit on Windows
Status: RESOLVED DUPLICATE of bug 1052
Product: PySide
Classification: Unclassified
Component: pyside-tools
: 1.0.8
: All All
: P2 major
Assigned To: Lauro Moura
:
:
:
  Show dependency tree / graph
 
Reported: 2011-10-25 12:07 EEST by Roman Lacko
Modified: 2011-11-25 21:18 EET (History)
13 users (show)

See Also:

Attachments
fixed building for me (944 bytes, patch)
2011-11-15 17:39 EET, Vladimir Rutsky 		Details
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 Roman Lacko 2011-10-25 12:07:48 EEST 
I have problem building PySide Tools module with Python 2.7.2 32bit
(shiboken, apiextractor, genrunner and pyside was compiled without
errors),
CMake prints following message until I don't stop the cmake process with
ctrl+c:
-- Using default python:

Full log:
-- The C compiler identification is MSVC
-- The CXX compiler identification is MSVC
-- Check for CL compiler version
-- Check for CL compiler version - 1500
-- Check if this is a free VC compiler
-- Check if this is a free VC compiler - no
-- Check for working C compiler: c:/Program Files (x86)/Microsoft
Visual Studio 9.0/VC/bin/cl.exe
-- Check for working C compiler: c:/Program Files (x86)/Microsoft
Visual Studio 9.0/VC/bin/cl.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: c:/Program Files (x86)/Microsoft
Visual Studio 9.0/VC/bin/cl.exe
-- Check for working CXX compiler: c:/Program Files (x86)/Microsoft
Visual Studio 9.0/VC/bin/cl.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Found PythonInterp: c:/Python26/python.exe
-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - not found.
-- Looking for Q_WS_WIN
-- Looking for Q_WS_WIN - found
-- Looking for Q_WS_QWS
-- Looking for Q_WS_QWS - not found.
-- Looking for Q_WS_MAC
-- Looking for Q_WS_MAC - not found.
-- Found Qt-Version 4.7.4 (using c:/Qt/4.7.4/bin/qmake.exe)
-- Using default python:
-- Using default python:
-- Using default python:
-- Using default python:
-- Using default python:
-- Using default python:
-- Using default python:
-- Using default python:
-- Using default python:
-- Using default python:
-- Using default python:
-- Using default python:
-- Using default python:
-- Using default python:
-- Using default python:
-- Using default python:
-- Using default python:
^CTraceback (most recent call last):
 File "build.py", line 255, in <module>
   main()
 File "build.py", line 241, in main
   process_modules(options.build_module, options.download, modu
 File "build.py", line 74, in process_modules
   process_module(download, module, modules_dir, install_dir, q
 File "build.py", line 141, in process_module
   if run_process(*args) != 0:
 File "c:\Downloads\pyside-setuptools-1.0.8\utils.py", line 80,
   p.communicate()
 File "c:\Python26\lib\subprocess.py", line 688, in communicate
   self.wait()
 File "c:\Python26\lib\subprocess.py", line 883, in wait
   _subprocess.INFINITE)
KeyboardInterrupt

I'm not able to create windows packages until this error will be not resolved
Comment 1 david.w.watson 2011-10-25 15:47:41 EEST 
I am having the same problem installing on my MacOSX, through macports.
Comment 2 russell.p.palmer 2011-11-04 01:22:22 EET 
Hello,
I had exactly the same error trying to compile PySide-tools for python3.2.2 on
ArchLinux.

I have absolutely no python experience and am hoping to learn python and PySide
simultaneously so forgive me if my solution is a little naive...

I thought you would like to know that adding a --trace switch to the cmake
command resulted in some clues to the problem :

/usr/local/lib/cmake/PySide-1.0.8/PySideConfig.cmake(1):  if(NOT
PYTHON_BASENAME )
/usr/local/lib/cmake/PySide-1.0.8/PySideConfig.cmake(2):  message(STATUS Using
default python:  )
-- Using default python: 
/usr/local/lib/cmake/PySide-1.0.8/PySideConfig.cmake(3):  SET(PYTHON_BASENAME )
/usr/local/lib/cmake/PySide-1.0.8/PySideConfig.cmake(5): 
include(/usr/local/lib/cmake/PySide-1.0.8/PySideConfig${SHIBOKEN_PYTHON_SUFFIX}.cmake
)

I had a look at the file /usr/local/lib/cmake/PySide-1.0.8/PySideConfig.cmake
(I presume this path varies with different OSs?!), line 5.  Adding a line such
as:

message("Test : ${SHIBOKEN_PYTHON_SUFFIX}")

showed quite clearly that the problem lies in the fact that this variable has
not been set... so line 5 effectively includes itself ad infinitum.

I had a cursory look around for a likely file that it should be including,
found nothing so removed line 5 completely.

Running cmake then resulted in an error in the file <your build
dir>/pyside-tools/CMakeLists.txt on line 22.  This will only affect you if
you're using python3 as it is missing brackets round a print statement.

I added the brackets, ran cmake and all went swimmingly from there on in.

I believe that pyside-tools is now successfully installed and am off to do some
testing... hopefully this will help someone who knows a lot more than me to fix
the issue for future releases.  I presume the offending file
(/usr/local/lib/cmake/PySide-1.0.8/PySideConfig.cmake) was installed on my
system by the PySide install process, so would start my investigation there if
I had a clue how to go about doing that...!

Good luck to you all.
Comment 3 Vladimir Rutsky 2011-11-15 17:38:23 EET 
I can confirm this bug, IMO this bug should be prioritized as blocker.


I'm not familiar with CMake, but I managed to build latest PySide version using
attached patch against libpyside/PySideConfig.cmake.in.
Comment 4 Vladimir Rutsky 2011-11-15 17:39:32 EET 
Created attachment 447 [details]
fixed building for me
Comment 5 Paul Bonser 2011-11-17 19:03:59 EET 
(In reply to comment #3)
> I can confirm this bug, IMO this bug should be prioritized as blocker.
> 
> 
> I'm not familiar with CMake, but I managed to build latest PySide version using
> attached patch against libpyside/PySideConfig.cmake.in.

This patch seems to have generated a working PySide build for me as well.

Is a fix going to be merged in soon?
Comment 6 Hugo Parente Lima 2011-11-25 21:18:09 EET 

*** This bug has been marked as a duplicate of bug 1052 ***
First Last Prev Next    This bug is not in your last search results.