Creating a Own Tool chain, some referenced packages are not included into the SDK archive

Creating a Own Tool chain, some referenced packages are not included into the SDK archive

[Hauser, Wolfgang (external)]

Hello, 

I tried to build my own tool chain, using the target task listed below.

The bitbake of the tool chain run w/o errors, but the referenced
packages will be installed partly only into the SDK archive.
(e.g. libqt-embeddedcore4-dev and libqt-embeddedphonon4-dev reside in
the SDK archive, the other packages are missing)

I use an private overlay, referencing org.openembedded.dev and using
DISTRO = "angstrom-2008.1" and MACHINE = "omap3evm" 
The meta-toolchain-xxx is derived from meta-toolchain-qte. 

What may going wrong here ?

Regards
Wolfgang Hauser

meta-toolchain-xxx.bb >>>
# xxx Qt Embedded toolchain
PR = "r3"
TOOLCHAIN_HOST_TASK = "task-xxx-toolchain-host"
TOOLCHAIN_TARGET_TASK = "task-xxx-toolchain-target"

require recipes/meta/meta-toolchain.bb
SDK_SUFFIX = "toolchain-xxx"
SDK_SUFFIX_angstrom = "toolchain-xxx-${ANGSTROM_QT_VERSION}"

QT_DIR_NAME = "qtopia"

do_populate_sdk_append() {
       script = "${SDK_OUTPUT}/${SDKPATH}/environment-setup"
       touch $script
       echo 'export OE_QMAKE_CC=${TARGET_SYS}-gcc' >> $script
       echo 'export OE_QMAKE_CXX=${TARGET_SYS}-g++' >> $script
       echo 'export OE_QMAKE_LINK=${TARGET_SYS}-g++' >> $script
       echo 'export
OE_QMAKE_LIBDIR_QT=${SDKPATH}/${TARGET_SYS}/${libdir}' >> $script
       echo 'export
OE_QMAKE_INCDIR_QT=${SDKPATH}/${TARGET_SYS}/${includedir}/${QT_DIR_NAME}
' >> $script
       echo 'export OE_QMAKE_MOC=${SDKPATH}/bin/moc4' >> $script
       echo 'export OE_QMAKE_UIC=${SDKPATH}/bin/uic4' >> $script
       echo 'export OE_QMAKE_UIC3=${SDKPATH}/bin/uic34' >> $script
       echo 'export OE_QMAKE_RCC=${SDKPATH}/bin/rcc4' >> $script
       echo 'export OE_QMAKE_QDBUSCPP2XML=${SDKPATH}/bin/qdbuscpp2xml4'
>> $script
       echo 'export OE_QMAKE_QDBUSXML2CPP=${SDKPATH}/bin/qdbusxml2cpp4'
>> $script
       echo 'export
OE_QMAKE_QT_CONFIG=${SDKPATH}/${TARGET_SYS}/${datadir}/${QT_DIR_NAME}/mk
specs/qconfig.pri' >> $script
       echo 'export
QMAKESPEC=${SDKPATH}/${TARGET_SYS}/${datadir}/${QT_DIR_NAME}/mkspecs/lin
ux-g++' >> $script

       # Repack SDK with new environment-setup
       cd ${SDK_OUTPUT}
       fakeroot tar cfj ${SDK_DEPLOY}/${TOOLCHAIN_OUTPUTNAME}.tar.bz2 .
}
<<<<<

task-xxx-toolchain-target.bb >>>>

DESCRIPTION = "Target packages for xxx Qt Embedded SDK"
LICENSE = "MIT"
ALLOW_EMPTY = "1"

PR = "r2"

PACKAGES = "${PN}"

DEPENDS = "task-sdk-bare"

RDEPENDS_${PN} += " \
        task-sdk-bare \
        alsa-lib-dev \
        libpng-dev \
        net-snmp-dev \
        ftplib-dev \
        libgles-omap3-dev \
        qt4-embedded-mkspecs \
        libqt-embeddedphonon4-dev \
        libqt-embedded3support4-dev \
        libqt-embeddedassistantclient4-dev \
        libqt-embeddedcore4-dev \
        libqt-embeddeddbus4-dev \
        libqt-embeddeddesignercomponents4-dev \
        libqt-embeddeddesigner4-dev \
        libqt-embeddeduitools4-dev \
        libqt-embeddedgui4-dev \
        libqt-embeddedhelp4-dev \
        libqt-embeddednetwork4-dev \
        libqt-embeddedsvg4-dev \
        libqt-embeddedtest4-dev \
        libqt-embeddedxml4-dev \
        libts-dev \
        "
<<<<

Re: Creating a Own Tool chain, some referenced packages are not included into the SDK archive

[Holger Freyther]

On 06/29/2010 10:04 PM, Hauser, Wolfgang (external) wrote:
> Hello, 

> I use an private overlay, referencing org.openembedded.dev and using
> DISTRO = "angstrom-2008.1" and MACHINE = "omap3evm" 
> The meta-toolchain-xxx is derived from meta-toolchain-qte. 

Hi,
to make it more easy for me. What is the difference between
meta-toolchain-xxxx and meta-toolchain-qte? Does meta-toolchain-qte work
properly?


The general advice I can give is to log at the opkg installation log and
see if the tasks were installed, and if it picked up the dependencies...

Re: Creating a Own Tool chain, some referenced packages are not included into the SDK archive

[Hauser, Wolfgang (external)]

Hello Holger Freyther,

here are the diffs for my changes:

diff of meta-toolchain-qte.bb <> meta-toolchain-xxx.bb
>>>>>>>> 
1c1
< # Qt Embedded toolchain
---
> # xxx Qt Embedded toolchain
3,4c3,4
< TOOLCHAIN_HOST_TASK = "task-qte-toolchain-host"
< TOOLCHAIN_TARGET_TASK = "task-qte-toolchain-target"
---
> TOOLCHAIN_HOST_TASK = "task-xxx-toolchain-host"
> TOOLCHAIN_TARGET_TASK = "task-xxx-toolchain-target"
6,8c6,8
< require meta-toolchain.bb
< SDK_SUFFIX = "toolchain-qte"
< SDK_SUFFIX_angstrom = "toolchain-qte-${ANGSTROM_QT_VERSION}"
---
> require recipes/meta/meta-toolchain.bb
> SDK_SUFFIX = "toolchain-xxx"
> SDK_SUFFIX_angstrom = "toolchain-xxx-${ANGSTROM_QT_VERSION}"
<<<<<<<<<

diff of task-qte-toolchain-host.bb <> task-xxx-toolchain-host.bb 
>>>>>>
1c1
< require task-sdk-host.bb
---
> require recipes/tasks/task-sdk-host.bb
<<<<<<

diff of task-qte-toolchain-target.bb <> task-xxx-toolchain-target.bb
>>>>>>>
< DESCRIPTION = "Target packages for Qt Embedded SDK"
---
> DESCRIPTION = "Target packages for xxx Qt Embedded SDK"
6a7,10
> PACKAGES = "${PN}"
> 
> DEPENDS = "task-sdk-bare"
> 
8a13,17
>         alsa-lib-dev \
>         libpng-dev \
>         net-snmp-dev \
>         ftplib-dev \
>         libgles-omap3-dev \
13d21
<         libqt-embeddedclucene4-dev \
22,24d29
<         libqt-embeddedscript4-dev \
<         libqt-embeddedscripttools4-dev \
<         libqt-embeddedsql4-dev \
27d31
<         libqt-embeddedwebkit4-dev \
29,31d32
<         libmysqlclient-dev \
<         sqlite-dev \
<         libsqlite-dev \
33d33
<         expat-dev \
<<<<<<<

The qte toolchain has created properly, my own do not.

The single packages are building properly.

Regards,
Wolfgang Hauser

-----Ursprüngliche Nachricht-----
Von: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] Im Auftrag von Holger Freyther
Gesendet: Dienstag, 29. Juni 2010 16:49
An: openembedded-devel@lists.openembedded.org
Betreff: Re: [oe] Creating a Own Tool chain, some referenced packages are not included into the SDK archive

On 06/29/2010 10:04 PM, Hauser, Wolfgang (external) wrote:
> Hello, 

> I use an private overlay, referencing org.openembedded.dev and using
> DISTRO = "angstrom-2008.1" and MACHINE = "omap3evm" 
> The meta-toolchain-xxx is derived from meta-toolchain-qte. 

Hi,
to make it more easy for me. What is the difference between
meta-toolchain-xxxx and meta-toolchain-qte? Does meta-toolchain-qte work
properly?


The general advice I can give is to log at the opkg installation log and
see if the tasks were installed, and if it picked up the dependencies...

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: Creating a Own Tool chain, some referenced packages are not included into the SDK archive

[Holger Freyther]

On 06/29/2010 11:20 PM, Hauser, Wolfgang (external) wrote:
> Hello Holger Freyther,
> 
> here are the diffs for my changes:
> 
> diff of meta-toolchain-qte.bb <> meta-toolchain-xxx.bb

sorry, this diff is not readable, please use a unified diff for the changes.

> 
> The qte toolchain has created properly, my own do not.

So you say bitbake meta-toolchain-qte is working?

Re: Creating a Own Tool chain, some referenced packages are not included into the SDK archive

[Hauser, Wolfgang (external)]

Hello Holger Freyther,

I have built a working qte toolchain at 2010/06/09. It is based on org.openembedded.dev at this time.

Regards
Wolfgang Hauser

-----Ursprüngliche Nachricht-----
Von: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] Im Auftrag von Holger Freyther
Gesendet: Donnerstag, 1. Juli 2010 14:51
An: openembedded-devel@lists.openembedded.org
Betreff: Re: [oe] Creating a Own Tool chain, some referenced packages are not included into the SDK archive

On 06/29/2010 11:20 PM, Hauser, Wolfgang (external) wrote:
> Hello Holger Freyther,
> 
> here are the diffs for my changes:
> 
> diff of meta-toolchain-qte.bb <> meta-toolchain-xxx.bb

sorry, this diff is not readable, please use a unified diff for the changes.

> 
> The qte toolchain has created properly, my own do not.

So you say bitbake meta-toolchain-qte is working?

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: Creating a Own Tool chain, some referenced packages are not included into the SDK archive

[Hauser, Wolfgang (external)]

Hello Holger Freyther,

I think, the working qte toolchain was built from stable_2009 branch.

Regards
Wolfgang Hauser
 
-----Ursprüngliche Nachricht-----
Von: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] Im Auftrag von Holger Freyther
Gesendet: Donnerstag, 1. Juli 2010 14:51
An: openembedded-devel@lists.openembedded.org
Betreff: Re: [oe] Creating a Own Tool chain, some referenced packages are not included into the SDK archive

On 06/29/2010 11:20 PM, Hauser, Wolfgang (external) wrote:
> Hello Holger Freyther,
> 
> here are the diffs for my changes:
> 
> diff of meta-toolchain-qte.bb <> meta-toolchain-xxx.bb

sorry, this diff is not readable, please use a unified diff for the changes.

> 
> The qte toolchain has created properly, my own do not.

So you say bitbake meta-toolchain-qte is working?

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: Creating a Own Tool chain, some referenced packages are not included into the SDK archive

[Hauser, Wolfgang (external)]

Hello, I have found the problems of creating the toolchain meta-toolchain-qte.bb (and my derived one) !

First problem:

There is a conflict in packages "cups" and "libpam-base-files" (same file "cups" in "/etc/pam.d" was deployed by the packages) this results in a bailing out while installing the packages.

My workaround was: local modified libpam-base-files w/o file "cups" in "libpam-base-files/pam.d"
(does libpam-base-files really have to install this file and some other package dependent ones ?)

Second problem:
meta-toolchain-qte.bb contains following line in do_populate_sdk_append():

  >script = "${SDK_OUTPUT}/${SDKPATH}/environment-setup"<

this have to be changed to:

  >script="${SDK_OUTPUT}/${SDKPATH}/environment-setup"<

because the code is used as shell commands and not as python code !

The issue above results in a call of "script" with arguments "=" and "${SDK_OUTPUT}/${SDKPATH}/environment-setup".
"script" opens a "bash -i" and wait for commands. Therefore the processing blocks until this shell exits.

Is there somebody out there having commit access who will fix that second problem in org.openembedded.dev ?

regards
Wolfgang Hauser

-----Ursprüngliche Nachricht-----
Von: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] Im Auftrag von Holger Freyther
Gesendet: Donnerstag, 1. Juli 2010 14:51
An: openembedded-devel@lists.openembedded.org
Betreff: Re: [oe] Creating a Own Tool chain, some referenced packages are not included into the SDK archive

On 06/29/2010 11:20 PM, Hauser, Wolfgang (external) wrote:
> Hello Holger Freyther,
> 
> here are the diffs for my changes:
> 
> diff of meta-toolchain-qte.bb <> meta-toolchain-xxx.bb

sorry, this diff is not readable, please use a unified diff for the changes.

> 
> The qte toolchain has created properly, my own do not.

So you say bitbake meta-toolchain-qte is working?

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: Creating a Own Tool chain, some referenced packages are not included into the SDK archive

[Denys Dmytriyenko]

On Thu, Jul 08, 2010 at 05:22:38PM +0200, Hauser, Wolfgang (external) wrote:
> Hello, I have found the problems of creating the toolchain 
> meta-toolchain-qte.bb (and my derived one) !
> 
> Second problem:
> meta-toolchain-qte.bb contains following line in do_populate_sdk_append():
> 
>   >script = "${SDK_OUTPUT}/${SDKPATH}/environment-setup"<
> 
> this have to be changed to:
> 
>   >script="${SDK_OUTPUT}/${SDKPATH}/environment-setup"<
> 
> because the code is used as shell commands and not as python code !
> 
> The issue above results in a call of "script" with arguments "=" and 
> "${SDK_OUTPUT}/${SDKPATH}/environment-setup".
> "script" opens a "bash -i" and wait for commands. Therefore the processing 
> blocks until this shell exits.

Worked here for long time and environment-setup gets populated with 
corresponding lines...

-- 
Denys

Re: Creating a Own Tool chain, some referenced packages are not included into the SDK archive

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08-07-10 17:22, Hauser, Wolfgang (external) wrote:
> Hello, I have found the problems of creating the toolchain meta-toolchain-qte.bb (and my derived one) !
> 
> First problem:
> 
> There is a conflict in packages "cups" and "libpam-base-files" (same file "cups" in "/etc/pam.d" was deployed by the packages) this results in a bailing out while installing the packages.
> 
> My workaround was: local modified libpam-base-files w/o file "cups" in "libpam-base-files/pam.d"
> (does libpam-base-files really have to install this file and some other package dependent ones ?)

Fixed:
http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=81467a049f275dde815b000e25b704e9140c2440

> Second problem:
> meta-toolchain-qte.bb contains following line in do_populate_sdk_append():
> 
>   >script = "${SDK_OUTPUT}/${SDKPATH}/environment-setup"<
> 
> this have to be changed to:
> 
>   >script="${SDK_OUTPUT}/${SDKPATH}/environment-setup"<
> 
> because the code is used as shell commands and not as python code !
> 
> The issue above results in a call of "script" with arguments "=" and "${SDK_OUTPUT}/${SDKPATH}/environment-setup".
> "script" opens a "bash -i" and wait for commands. Therefore the processing blocks until this shell exits.

Fixed:
http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=479ea460e4fbacd00f26a8903427e674a3b7501f

> 
> Is there somebody out there having commit access who will fix that second problem in org.openembedded.dev ?

Sure :) Thanks for finding out these bugs!

> 
> regards
> Wolfgang Hauser
> 
> -----Ursprüngliche Nachricht-----
> Von: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] Im Auftrag von Holger Freyther
> Gesendet: Donnerstag, 1. Juli 2010 14:51
> An: openembedded-devel@lists.openembedded.org
> Betreff: Re: [oe] Creating a Own Tool chain, some referenced packages are not included into the SDK archive
> 
> On 06/29/2010 11:20 PM, Hauser, Wolfgang (external) wrote:
>> Hello Holger Freyther,
>>
>> here are the diffs for my changes:
>>
>> diff of meta-toolchain-qte.bb <> meta-toolchain-xxx.bb
> 
> sorry, this diff is not readable, please use a unified diff for the changes.
> 
>>
>> The qte toolchain has created properly, my own do not.
> 
> So you say bitbake meta-toolchain-qte is working?
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMNgbQMkyGM64RGpERAuenAJ4r9q5woSg6tZXCB9lPRAHgkGHpogCfZygX
9Ei0MyIj9zB/pNp+F9ik978=
=LLyA
-----END PGP SIGNATURE-----

Re: Creating a Own Tool chain, some referenced packages are not included into the SDK archive

[Hauser, Wolfgang (external)]

>Worked here for long time and environment-setup gets populated with 
>corresponding lines...

It may work if command "script" wasn't installed on a host system, while
variable "script" is set in meta-toolchain.bb in the right way, so it
was found by meta-toolchain-qte.bb too.

Regards
Wolfgang Hauser