Hi Algis, Make sure you have python-dev and libpython2.6 installed.
I think this will solve your problem. BR On Fri, Oct 29, 2010 at 8:14 PM, Algis Kabaila <[email protected]> wrote: > Hi, > > I failed to find in my pyside binaries, downloaded from ubuntu repositories, > including updates of the binaries, the "pyside-uic" script. This prompted me > to try to switch to the PySide generated from the source. As a guide for > that I used your excellent documentation in ..wiki/Building_PySide_on_Linux. > > All my data is in a separate partition "/dat", so I made my sandbox > /dat/sandbox. It all went smoothly up to the header of *Building*, where I > decided to use the "build_all" script for building. I think that the first > two packages ("apiextractor" "generatorrunner") were successfully built. > However the process failed to build "shiboken" and consequently "pyside". I > think the main error was failure to find > > (missing: PYTHON_INCLUDE_DIRS), also reported as PYTHON_INCLUDE_DIR > (ADVANCED). I feel that both references are (or should be) to the same > environment variable. > > I decided to save time in the next trial and to reduce the list of packages > up to (but excluding) shiboken and called this modified script > "build_shiboken.sh". I list it here: > > ****************** > > #!/usr/bin/env bash > > #build_shiboken.sh > > alldirs=("shiboken" "pyside") > > if [ $# == 0 ] ; then > > dirs=("${alldi...@]}") > > else > > dirs=("$@") > > fi > > for d in "${di...@]}" ; do > > rm -rf "$d/build" > > mkdir -p "$d/build" > > (cd "$d/build" > > cmake .. && make -j4 && sudo make install || exit 1 > > ) # exit from "$d/build" > > done > > ****************** > > Of course, running it gives me the same errors as running the "build_all" > script (with the omission of [relatively] successful building of the first > two packages]. The listing of results is not huge, so I give it here in > full: > > =============== > > a...@supremo:/dat/sandbox$ ./build_shiboken.sh > > -- The C compiler identification is GNU > > -- The CXX compiler identification is GNU > > -- Check for working C compiler: /usr/bin/gcc > > -- Check for working C compiler: /usr/bin/gcc -- works > > -- Detecting C compiler ABI info > > -- Detecting C compiler ABI info - done > > -- Check for working CXX compiler: /usr/bin/c++ > > -- Check for working CXX compiler: /usr/bin/c++ -- works > > -- Detecting CXX compiler ABI info > > -- Detecting CXX compiler ABI info - done > > -- Looking for Q_WS_X11 > > -- Looking for Q_WS_X11 - found > > -- Looking for Q_WS_WIN > > -- Looking for Q_WS_WIN - not 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.0 (using /usr/bin/qmake) > > -- Could NOT find PythonLibs (missing: PYTHON_INCLUDE_DIRS) > > -- Found PythonInterp: /usr/bin/python2.6 > > -- Using protected hack! > > -- sphinx-build - found > > !! Some dependencies were not found, shiboken generator compilation > disabled! > > CMake Error: The following variables are used in this project, but they are > set to NOTFOUND. > > Please set them or make sure they are set and tested correctly in the CMake > files: > > PYTHON_INCLUDE_DIR (ADVANCED) > > used as include directory in directory /dat/sandbox/shiboken/libshiboken > > -- Configuring incomplete, errors occurred! > > -- The C compiler identification is GNU > > -- The CXX compiler identification is GNU > > -- Check for working C compiler: /usr/bin/gcc > > -- Check for working C compiler: /usr/bin/gcc -- works > > -- Detecting C compiler ABI info > > -- Detecting C compiler ABI info - done > > -- Check for working CXX compiler: /usr/bin/c++ > > -- Check for working CXX compiler: /usr/bin/c++ -- works > > -- Detecting CXX compiler ABI info > > -- Detecting CXX compiler ABI info - done > > CMake Error at CMakeLists.txt:9 (find_package): > > Could not find module FindShiboken.cmake or a configuration file for > > package Shiboken. > > Adjust CMAKE_MODULE_PATH to find FindShiboken.cmake or set Shiboken_DIR to > > the directory containing a CMake configuration file for Shiboken. The file > > will have one of the following names: > > ShibokenConfig.cmake > > shiboken-config.cmake > > -- Looking for Q_WS_X11 > > -- Looking for Q_WS_X11 - found > > -- Looking for Q_WS_WIN > > -- Looking for Q_WS_WIN - not 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.0 (using /usr/bin/qmake) > > -- Detected OS: x11 > > CMake Error at CMakeLists.txt:142 (message): > > Could not detect Python module installation directory. > > -- Configuring incomplete, errors occurred! > > a...@supremo:/dat/sandbox$ > > =============== > > I notice in ..wiki/Building_PySide_on_Linux that under the header of "Setup > these variable accordingly", line 6 alias runcmake='cmake .. ....' does not > appear in the script. Would it help if it did? Because of this omission, the > instruction to replace "cmake" with "runcmake" is not done either. In effect > IMHO the instructions for coding are not fully reflected in the script. I > surely do prefer using the script, particularly if the alternative is to > type long variables manually each time! > > I am totally lost what to do. All help will be appreciated! > > OldAl. > > -- > > Algis Kabaila > > http://akabaila.pcug.org.au/ > > _______________________________________________ > PySide mailing list > [email protected] > http://lists.openbossa.org/listinfo/pyside > > -- Renato Araujo Oliveira Filho Instituto Nokia de Tecnologia - INdT Mobile: +55 (81) 8704-2144 _______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
