Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] dbus-triggerd: new package
Date: Wed, 26 Mar 2014 08:46:23 +0100	[thread overview]
Message-ID: <533285CF.6090700@mind.be> (raw)
In-Reply-To: <53327B4B.2010005@syscom.ch>

On 26/03/14 08:01, Arnaud R?billout wrote:
> Hi Arnout,
> 
>>  For the other dbus-* packages, the dbus dependencies are repeated (even
>> though they're automatic because of the depends on DBUS). So I would do
>> that here as well. And that means of course that there should also be a
>> comment in case of missing toolchain features. See dbus-cpp for an example.
> You're right, I forgot the comments, and the host-pkgconf dependency as well.
> I will do as you suggest for the DBUS dependencies.
> 
>>  Patch misses a description + Signed-off-by.
> Correct.
> 
>>  If you're anyway patching the Makefile, you can just as well make it:
>>
>> CFLAGS?=-Wall -O3
>> CFLAGS+=`$(PKG_CONFIG) --cflags dbus-1`
>> LDLIBS+=`$(PKG_CONFIG) --libs dbus-1`
>>
>>
>>
>>  Will you send this patch upstream?
> Yep. I will send a patch right now.
> 
> 
>>  This should be $(TARGET_CONFIGURE_OPTS) which includes all of the above
>> and more.
> OK. Actually, I've always been wondering it was OK to use
> TARGET_CONFIGURE_OPTS in a generic package, I never dared to do it.

 Yeah, it should be renamed, really.

 Regards,
 Arnout

> 
>>  Note BTW that the patch above refers to LDLIBS instead of LDFLAGS. Is
>> LDFLAGS used?
> Yep, LDFLAGS is used automatically by Make in this Makefile.
> 
> 
> 
> Thanks for your comments, I will send the patch upstream a wait a little
> for the author's comments on it.
> 
> 
> Regards
> 
> 
> -- 
> Arnaud R?billout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2014-03-26  7:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25  7:59 [Buildroot] [PATCH 0/1] dbus-triggerd, a helpful little daemon Arnaud Rébillout
2014-03-25  7:59 ` [Buildroot] [PATCH 1/1] dbus-triggerd: new package Arnaud Rébillout
2014-03-25 20:12   ` Arnout Vandecappelle
2014-03-26  7:01     ` Arnaud Rébillout
2014-03-26  7:46       ` Arnout Vandecappelle [this message]

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=533285CF.6090700@mind.be \
    --to=arnout@mind.be \
    --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