[SailfishDevel] Fwd: Re: Include Python.h

khertan at khertan.net khertan at khertan.net
Tue Aug 6 10:14:07 UTC 2013

Hi Christopher,

Indeed i think the vm was the toolchain, and not an host of the toolchain :p

That's solve my problems and I'll be able to play now with PyOtherSide on sailfish.

Thanks a lot !
Benoît HERVIER - http://khertan.netLe 06/08/13 11:14 christopher.lamb at thurweb.ch a écrit :
Hi Benoit

B.t.w, zypper in to the MERSDK and adding packages to the toolchain  
via the SDK Control Center are NOT the same thing*.

I was also a bit confused on this, but as I see it, using zypper in  
the MERSDK makes stuff available to the underlaying operating system,  
but not necessarily to the toolchain.

To me it makes sense to isolate the 2, the OS may require different  
versions of the same package then those in the toolchain (which are  
intended to build stuff for a third party - in this case the Emulator)

Perhaps David can explain this better.


* having just added python-devel via the SDK Control Center, I also  
did a zypper se python-devel, which showed that package is not  
installed (for the OS), yet it is in the toolchain.

----- Weitergeleitete Nachricht von christopher.lamb at thurweb.ch -----
      Datum: Tue, 06 Aug 2013 11:03:35 +0200
        Von: christopher.lamb at thurweb.ch
    Betreff: Re: [SailfishDevel] Include Python.h
         An: "Benoît HERVIER" <khertan at khertan.net>
         Cc: devel at lists.sailfishos.org

Salut Benoit

Have you tried installing python-devel via the SDK Control Center in  
QtCreator. (The Sailfish Icon on the left side of QtCreator)

I have just done so, an now have a python.h file in the toolchain  
(before I had none).


Zitat von "Benoît HERVIER" <khertan at khertan.net>:

> Morning
> I'm currently facing a problem that i didn't understand :
> ./qpython.h:4:20: fatal error: Python.h: No such file or directory
> qpython.h
> ~~~~
> #ifndef _QPYTHON_H
> #define _QPYTHON_H
> #include "Python.h"
> ~~~~
> I ve installed via zypper python-devel in mersdk vm.
> I've even added hardcoded path in .pro:
> INCLUDEPATH += /usr/include/python2.7
> LIBS += -lpython2.7
> And python2.7 headers path are in the gcc cmd:
> Exécution_de(%build): /bin/sh -e /var/tmp/rpm-tmp.b27OWP
> g++ -c -m32 -pipe -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2  
> -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wformat  
> -Wformat-security -m32 -march=core2 -mssse3 -mtune=atom -mfpmath=sse  
> -fasynchronous-unwind-tables -fno-omit-frame-pointer -Wall -W  
> -DDEPLOYMENT_PATH="\""/usr/share/ownNotesForSailfish/"\""  
> -I/usr/share/qt5/mkspecs/linux-g++-32 -I. -I/usr/include/python2.7  
> -Isailfishapplication -I/usr/include/qt5 -I/usr/include/qt5/QtQuick  
> -I/usr/include/qt5/QtQml -I/usr/include/qt5/QtNetwork  
> -I/usr/include/qt5/QtGui -I/usr/include/qt5/QtCore -Imoc -o  
> obj/main.o main.cpp
> Python.h is available in /usr/include/python2.7 on mersdk vm.
> Such include is working in QtProject QtCreator on desktop ... so i  
> suppose that something i miss with the compilation on target ...
> Any advice ?
> Thx
> -- 
> Benoît HERVIER - http://khertan.net/
> _______________________________________________
> SailfishOS.org Devel mailing list

SailfishOS.org Devel mailing list

----- Ende der weitergeleiteten Nachricht -----

More information about the Devel mailing list