Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Laird <daniel.j.laird@nxp.com>
To: buildroot@busybox.net
Subject: [Buildroot]  Howto mainline patches I have posted?
Date: Tue, 1 Jul 2008 10:46:28 -0700 (PDT)	[thread overview]
Message-ID: <18221527.post@talk.nabble.com> (raw)


Hi

I have posted some patches and raised BUG reports but have had no feedback
and i was wondering how i might get these changes mainlined?
These changes are all designed to get GTK building with DirectFB support if
DirectFB is enabled and XORG is not.  I think this would benefit many
embedded buildroot users.
I am currently working on getting WebKit on GTK running with a patch they
have in their bug tracking system that removes the dependancy on ICU and
this I am sure will benefit all cross compilers out there 
For now I have lots of local changes and I just want to get them mainlined
for others to benefit / improve.

The changes are:
Summary 0003614: libxslt uses old build system and does not post edit the
xslt-config script like libxml2/freetype 
Description libxslt is built using old build system. Move to autotargets
system and make sure config script is post edited correctly.
Also add option to support conditional crypto support (based upon libgcrypt
being selected) 

Summary 0003604: libxml2 config script (xml2-config) is not edited in the
same way as freetype-config 
Description libxml2 produces a config script like freetype. Called
xml2-config. It requires that the same SED be done so that cross compilation
works. 

Summary 0003594: ATK does not always require X support to be compiled
 Description ATK does not always require X support to be enabled (DirectFB
only for instance) 

Summary 0003584: Cairo does not build directfb if directfb support required
(dependencies missing) 
Description Cairo supports being built for DirectFB. However it is not
dependent on DirectFB so DirectFB may not actually be build yet 

Summary 0003574: pango.mk redefines PKG_CONFIG_* for no reason 
Description pango.mk currently redefines PKG_CONFIG_PATH/SYSROOT. This is
not necessary as specified in configure enviroment. In my case I have added
usr/local/lib/pkgconfig as well and without this fix I need to edit multiple
makefiles not just package/Makefile.in. 

Summary 0003564: libgtk.mk redefines PKG_CONFIG_PATH, not necessary 
Description libgtk.mk currently redefines PKG_CONFIG_PATH. This is not
necessary as specified in configure enviroment. In my case I have added
usr/local/lib/pkgconfig as well and without this fix I need to edit multiple
makefiles not just package/Makefile.in. 

Summary 0003554: Make libgtk2 visible with DirectFB and not just XORG 
Description libgtk2 is currently dependent on XORG being selected in some
form or another. You may only have DirectFB is which case gtk is currently
not selectable. 

Hope this helps
Daniel Laird
-- 
View this message in context: http://www.nabble.com/Howto-mainline-patches-I-have-posted--tp18221527p18221527.html
Sent from the BuildRoot mailing list archive at Nabble.com.

             reply	other threads:[~2008-07-01 17:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 17:46 Daniel Laird [this message]
2008-07-01 19:13 ` [Buildroot] Howto mainline patches I have posted? Peter Korsgaard

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=18221527.post@talk.nabble.com \
    --to=daniel.j.laird@nxp.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox