From: Jens Lucius <jenslucius@freenet.de>
To: yocto@yoctoproject.org
Subject: Building python module after compiling in one recipe
Date: Thu, 10 Apr 2014 23:40:42 +0200 [thread overview]
Message-ID: <53470FDA.6010703@freenet.de> (raw)
In-Reply-To: <533B0C8F.9050004@freenet.de>
Hi
I am trying to bitbake pjproject including the python module. I manged
to write a working .bb recipe for the latest pjproject, which compiles
and installes correctly. But I also want to build the python module.
The documentation of pjproject says about building the python module:
1. Build the PJSIP libraries first with the usual "./configure && make
dep && make" commands.
2. Go to pjsip-apps/src/python directory.
3. Run *'sudo python ./setup.py install'* or just *'sudo make'*
So I guess with the working recipe I got part 1. I tried to do stepts 2
and 3 by adding the following:
do_compile_append() {
export BUILD_SYS
export HOST_SYS
export STAGING_INCDIR
export STAGING_LIBDIR
cd ${S}/pjsip-apps/src/python
oe_runmake
}
which starts the building process but then terminates with:
| cc1: warning: include location "/usr/include/python2.7" is unsafe for
cross-compilation [-Wpoison-system-directories]
| In file included from _pjsua.c:20:0:
| _pjsua.h:25:20: fatal error: Python.h: No such file or directory
So I guess it is trying to use the host python for building the module
(which is obviously not correct).
So can I build them both in one recipe and how? And if built correctly
how to install the modules?
Thanks for your help.
prev parent reply other threads:[~2014-04-10 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 18:59 Is Python Tkinter available for Yocto Jens Lucius
2014-04-04 14:34 ` Jens Lucius
2014-04-04 14:42 ` Gary Thomas
2014-04-04 15:36 ` Jens Lucius
2014-04-04 16:35 ` Paul Barker
2014-04-10 21:40 ` Jens Lucius [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53470FDA.6010703@freenet.de \
--to=jenslucius@freenet.de \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.