* [RFH] Wrong behaviour regarding SDK native and target paths
@ 2011-07-03 22:29 Otavio Salvador
2011-07-04 13:46 ` Richard Purdie
0 siblings, 1 reply; 2+ messages in thread
From: Otavio Salvador @ 2011-07-03 22:29 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
Hello,
I am looking for help to get our nativesdk working fine and I am quite
confused how does it can work after all.
I have looked at meta/recipes-qt/meta/meta-toolchain-qte.bb and it has:
QT_TOOLS_PREFIX = "${SDKPATHNATIVE}${bindir_nativesdk}"
Running it is expanded to:
QT_TOOLS_PREFIX="/usr/local/oecore-i686-i586/sysroots/i686-oesdk-linux/usr/bin"
It seems right but in fact it is wrong since Qt binaries are installed into:
(devel)~/hacking/el% tar tjf
tmp-eglibc-eglibc/deploy/sdk/oecore-i686-i586-toolchain-devel.tar.bz2|
grep 'bin/moc4'
./usr/local/oecore-i686-i686/sysroots/i686-oesdk-linux/usr/bin/moc4
so, the generated information for the script won't work.
I am quite confused by all this is suppose to work. Someone help me?
Cheers,
--
Otavio Salvador O.S. Systems
E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [RFH] Wrong behaviour regarding SDK native and target paths
2011-07-03 22:29 [RFH] Wrong behaviour regarding SDK native and target paths Otavio Salvador
@ 2011-07-04 13:46 ` Richard Purdie
0 siblings, 0 replies; 2+ messages in thread
From: Richard Purdie @ 2011-07-04 13:46 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On Sun, 2011-07-03 at 19:29 -0300, Otavio Salvador wrote:
> Hello,
>
> I am looking for help to get our nativesdk working fine and I am quite
> confused how does it can work after all.
>
> I have looked at meta/recipes-qt/meta/meta-toolchain-qte.bb and it has:
>
> QT_TOOLS_PREFIX = "${SDKPATHNATIVE}${bindir_nativesdk}"
>
> Running it is expanded to:
>
> QT_TOOLS_PREFIX="/usr/local/oecore-i686-i586/sysroots/i686-oesdk-linux/usr/bin"
>
> It seems right but in fact it is wrong since Qt binaries are installed into:
>
> (devel)~/hacking/el% tar tjf
> tmp-eglibc-eglibc/deploy/sdk/oecore-i686-i586-toolchain-devel.tar.bz2|
> grep 'bin/moc4'
> ./usr/local/oecore-i686-i686/sysroots/i686-oesdk-linux/usr/bin/moc4
>
> so, the generated information for the script won't work.
>
> I am quite confused by all this is suppose to work. Someone help me?
It looks like in OE-Core we have:
conf/bitbake.conf:SDKPATHNATIVE = "${SDKPATH}/sysroots/${SDK_SYS}"
conf/bitbake.conf:SDKPATH = "/usr/local/${SDK_NAME}"
conf/bitbake.conf:SDK_NAME = "oecore-${SDK_ARCH}-${TARGET_ARCH}"
and in meta-yocto:
conf/distro/poky.conf:SDKPATH = "/opt/${DISTRO}/${SDK_VERSION}"
I suspect having TARGET_ARCH in the PATH might be a bad idea and we need
to rethink the defaults in OE-Core. Using something more like the
meta-yocto default above might help your problem.
Cheers,
Richard
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-07-04 13:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-07-03 22:29 [RFH] Wrong behaviour regarding SDK native and target paths Otavio Salvador
2011-07-04 13:46 ` Richard Purdie
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox