Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] New Package: latencytop
Date: Wed, 18 Apr 2012 00:13:09 +0200	[thread overview]
Message-ID: <201204180013.10481.arnout@mind.be> (raw)
In-Reply-To: <1334680135-30458-1-git-send-email-qais.yousef@imgtec.com>

On Tuesday 17 April 2012 18:28:55 Qais Yousef wrote:
> +--- latencytop-0.5/Makefile.old        2012-04-17 16:22:25.896083743 +0100
> ++++ latencytop-0.5/Makefile    2012-04-17 16:23:01.318057605 +0100
> +@@ -4,11 +4,11 @@
> + DESTDIR =
> + SBINDIR = /usr/sbin
> + XCFLAGS = -W  -g `pkg-config --cflags glib-2.0` -D_FORTIFY_SOURCE=2 -Wno-sign-compare
> +-LDF = -Wl,--as-needed `pkg-config --libs glib-2.0`   -lncursesw 
> ++LDF = -Wl,--as-needed `pkg-config --libs glib-2.0`   -lncurses 
> + 
> + OBJS= latencytop.o text_display.o translate.o fsync.o
> + 
> +-ifdef HAS_GTK_GUI
> ++ifneq ($(HAS_GTK_GUI),0)

 I think this one is unneeded as well if you use HAS_GTK_GUI= (without 
the 0).  So:

> +       $(TARGET_CONFIGURE_OPTS) $(MAKE) -C $(@D) HAS_GTK_GUI=0

would become

	$(TARGET_CONFIGURE_OPTS) $(MAKE) -C $(@D) HAS_GTK_GUI=

 Regards,
 Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
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:[~2012-04-17 22:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 16:28 [Buildroot] [PATCH v3] New Package: latencytop Qais Yousef
2012-04-17 22:13 ` Arnout Vandecappelle [this message]
2012-04-18 11:08   ` Qais Yousef

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=201204180013.10481.arnout@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