From: Justin Mark <oilehus@yahoo.com>
To: buildroot@busybox.net
Subject: [Buildroot] DConf
Date: Sat, 4 Dec 2010 16:09:00 -0800 (PST) [thread overview]
Message-ID: <953244.140.qm@web111110.mail.gq1.yahoo.com> (raw)
In-Reply-To: <20101203113536.38481498@surf>
OK, I will work on adding dconf into buildroot, but before doing that, I need to add libgee into buildroot first.
I can build libgee with buildroot in my workspace, how should I submit the patch for review? post the patch here or directly do it from git? Can someone give me some details since I don't know much about git?
thanks,
Justin
--- On Fri, 12/3/10, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Subject: Re: [Buildroot] DConf
> To: buildroot at busybox.net
> Date: Friday, December 3, 2010, 2:35 AM
> On Thu, 2 Dec 2010 21:39:01 -0800
> (PST)
> Justin Mark <oilehus@yahoo.com>
> wrote:
>
> > Any plan to add DConf (http://live.gnome.org/dconf) in buildroot?
>
> I am not aware of any effort to package DConf in Buildroot
> at the
> moment. Looking at the configure.ac, the number of
> dependencies seems
> to be limited, so adding this package shouldn't be very
> difficult.
>
> I of course encourage you to submit a patch to add this
> package into
> Buildroot. See
> http://buildroot.org/downloads/buildroot.html#autotools-tutorial
> for
> details on how to add an autotools-based package.
>
> Regards,
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2010-12-05 0:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 5:39 [Buildroot] DConf Justin Mark
2010-12-03 10:35 ` Thomas Petazzoni
2010-12-05 0:09 ` Justin Mark [this message]
2010-12-05 0:38 ` Lionel Landwerlin
2010-12-05 0:50 ` Justin Mark
2010-12-05 8:03 ` Thomas Petazzoni
2010-12-05 8:17 ` [Buildroot] How to contribute to Buildroot with Git Thomas Petazzoni
2010-12-05 8:23 ` Paul Jones
2010-12-05 14:26 ` Heiko Zuerker
2010-12-05 14:41 ` Thomas Petazzoni
2010-12-05 14:54 ` Heiko Zuerker
2010-12-05 21:23 ` 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=953244.140.qm@web111110.mail.gq1.yahoo.com \
--to=oilehus@yahoo.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