[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

gtk dependencies for Emdebian



gtk dependencies in Emdebian target for arm:

libatk1.0-0 (1.20.0-1em1) {arm}
libglib2.0-0 (2.12.11-3em1) {arm}
libpcre3 (7.3-2em1) {arm}
fontconfig (2.4.91-1em1) {arm}
libfontconfig1 (2.4.91-1em1) {arm}
libcairo2 (1.4.10-1em1) {arm}
libdatrie0 (0.1.2-2em1) {arm}
libthai0 (0.1.9-2em1) {arm}
libxrender1 (1:0.9.4-1em1) {arm}
libpng12-0 (1.2.15~beta5-3em1) {arm}
libxau6 (1:1.0.3-2em1) {arm}
libgcrypt11 (1.2.4-2em1) {arm}
libopencdk8 (0.5.13-2em1) {arm}
liblzo2-2 (2.02-3em1) {arm}
libtasn1-3 (0.3.10-1em1) {arm}
libgnutls13 (2.0.4-1em1) {arm}
libcomerr2 (1.40.2-1em1) {arm}
libkeyutils1 (1.2-4em1) {arm}
libjpeg62 (6b-14em1) {arm}
libtiff4 (3.8.2-7em1) {arm}
libxft2 (2.1.12-2em1) {arm}
libxcursor1 (1:1.1.9-1em1) {arm}
libpango1.0-0 (1.18.3-1em1) {arm}
libxfixes3 (1:4.0.3-2em1) {arm}
libxdamage1 (1:1.1.1-3em1) {arm}
libcupsys2 (1.3.4-1em1) {arm}
libxrandr2 (2:1.2.2-1em1) {arm}
libxcomposite1 (1:0.3.2-1em1) {arm}
libgpg-error0 (1.4-2em1) {arm}
libxinerama1 (1:1.0.2-1em1) {arm}
libxext6 (1:1.0.3-2em1) {arm}
libxi6 (2:1.1.3-1em1) {arm}
libfreetype6 (2.3.5-1em1) {arm}

These are only preliminary packages, first builds if you like. In
particular, some of the Build-Cross-Depends lines in debian/xcontrol are
likely to be incomplete. Patches welcome.

Now is the time to optimise the dependencies within these packages and
work out which can be dropped, which can have more things removed etc.

There may still be dependencies of these packages that are not yet built
 - I'll be checking that next. This is just the list produced by
'debtree' (a utility created by Frans Pop):
http://alioth.debian.org/~fjp/debtree/

(ITP 447158)

Debtree graphs: http://www.linux.codehelp.co.uk/emdebian/depends.html

The packages [0] and toolchains [1] search scripts on www.emdebian.org
have also been revised and should now be usable for unstable (remaining
issues include the inability to view package data from testing). The PHP
reads the Packages.gz data directly from the relevant repository each
time the page is loaded so data is *always* in sync with reprepro. With
a suitable configuration tweak in your favourite browser, you should be
able to simply click on the link in the search results and view the
contents of the packages using deb-gview.

Also new, a link to the crossbuilt bug reports in Debian [2] and a
parser for the 'planner' XML that identifies tasks that are not
allocated to someone already [3]. (The bug report has an update pending
in SVN, due to be refreshed tonight.)

[0] http://www.emdebian.org/packages/search.php
[1] http://www.emdebian.org/toolchains/search.php
[2] http://www.emdebian.org/bugs.php
[3] http://www.emdebian.org/emdebian/helpout.php

Next tasks are to get a functional X environment and configuration on
balloon3, build libgtk2.0-0 and libgpewidget1 before progressing to the
rest of the GPE packages.

As before, CDBS has proved to be the easiest build system to cross build
but most of the X libraries already implemented the autotools-dev
recommended cross-building support that is the subject of most of the
current 'crossbuilt' bug reports. All my GPE packages use CDBS and those
are the bulk of the GPE set so things are looking good.

Once that is done, an Emdebian/GPE sandbox script will be developed as
the main focus for emdebian-tools 0.7.0. (I've got a few checks to make
before releasing emdebian-tools 0.6.0 probably tomorrow.)

Out of 110 source packages now built, only about 40 have needed bug
reports for cross-build support, 5 of those are already fixed in Debian.
Things are a lot better with dpkg-cross 2.0.0.
;-)

The only remaining problematic package is 'mesa' - see # 451648 : mesa:
configures for the build, not the host - broken cross builds. If anyone
fancies fixing that one and adding a patch to the bug report . . . .

-- 


Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/


Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: