In the config log we see:
configure:12277: checking whether to build static libraries
configure:12281: result: yes
configure:12419: checking for x86_64-overc-linux-pkg-config
configure:12452: result: no
configure:12462: checking for pkg-config
configure:12495: result: no
configure:12801: Using Farsight2 source release as package name
configure:12825: Using Unknown package origin as package origin
configure:12879: Using /usr/libexec/gst-install-plugins-helper as plugin install helper
configure:12953: checking for NICE
configure:13022: error: Need libnice >= 0.0.9
While it libnice that fails configure, it is the absence of pkg-config
several lines above that causes the failure, as libnice is in the sysroot.
For most build hosts, you'll have to remove the default binary that
lives in /usr/bin/pkg-config in order to see this failure.
Cc: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* Update do_compile_append where it was updating *.pc from ${S} and
removing staging dir folder. Now we have seperate build folder
where packages get build. We have to search pc in ${B} not in ${S}.
After updating the tmp dir path is removed from nice.pc file.
* Remove PNBLACKLIST for libnice and farsight2 recipes.
Signed-off-by: Noor Ahsan <noor_ahsan@mentor.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Fixed SRC_URI:
* ${PN} -> ${BPN}, use ${BP} if it was ${PN}-${PV}
* ${P} -> ${BP}
Otherwise we would meet do_fetch errors when we do the multilib, native
or nativesdk build.
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* This change is only aesthetic (unlike indentation in Python
tasks).
* Some recipes were using tabs.
* Some were using 8 spaces.
* Some were using mix or different number of spaces.
* Make them consistently use 4 spaces everywhere.
* Yocto styleguide advises to use tabs (but the only reason to keep
tabs is the need to update a lot of recipes). Lately this advice
was also merged into the styleguide on the OE wiki.
* Using 4 spaces in both types of tasks is better because it's less
error prone when someone is not sure if e.g.
do_generate_toolchain_file() is Python or shell task and also allows
to highlight every tab used in .bb, .inc, .bbappend, .bbclass as
potentially bad (shouldn't be used for indenting of multiline
variable assignments and cannot be used for Python tasks).
* Don't indent closing quote on multiline variables
we're quite inconsistent wheater it's first character on line
under opening quote or under first non-whitespace character in
previous line.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Acked-by: Koen Kooi <koen@dominion.thruhere.net>
