Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/zile: add Zile is Lossy Emacs editor
Date: Tue, 8 Apr 2014 18:16:53 +0200	[thread overview]
Message-ID: <20140408161653.GA3199@free.fr> (raw)
In-Reply-To: <87y4zg3yyj.fsf@linaro.org>

Alex, All,

On 2014-04-08 11:19 +0100, Alex Benn?e spake thusly:
> Yann E. MORIN <yann.morin.1998@free.fr> writes:
[--SNIP--]
> >> diff --git a/package/zile/zile.mk b/package/zile/zile.mk
> >> new file mode 100644
> >> index 0000000..024595c
> >> --- /dev/null
> >> +++ b/package/zile/zile.mk
> >> @@ -0,0 +1,13 @@
> >> +################################################################################
> >> +#
> >> +# Zile
> >> +#
> >> +################################################################################
> >> +
> >> +ZILE_VERSION = 2.4.11
> >> +ZILE_SITE = http://ftp.gnu.org/gnu/zile/
> >> +ZILE_LICENSE = GPLv1+
> >> +ZILE_LICENSE_FILES = COPYING
> >> +ZILE_CONF_OPT += --without-help2man
> >
> > In the previous patch, you added libgc, stating that it was a dependency
> > of Zile, but you forgot to add it here.
> 
> Ahh I thought it was enforced by the Config.in select but of course you
> need to ensure it's built as well. I'll fix that up.

THere are two types of dependencies:
  - build-time dependencies, and
  - run-time dependencies.

The run-time dependencies (eg. I need *that* program to be present) are
handled purely in the Config.in.

The build-time dependencies (eg. I need to link to *that* library) are
handled both in Config.in and the .mk.

The dependencies in Config.in will ensure that the package is present in
the target, while the dependencies in the .mk guarantee the build order.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2014-04-08 16:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 11:00 [Buildroot] [PATCH 0/2] Add lightweight Zile editor Alex Bennée
2014-04-07 11:00 ` [Buildroot] [PATCH 1/2] package/libgc: add Boehm-Demers-Weiser gc library Alex Bennée
2014-04-07 20:26   ` Yann E. MORIN
2014-04-08 10:20     ` Alex Bennée
2014-04-07 21:39   ` Thomas Petazzoni
2014-04-07 11:00 ` [Buildroot] [PATCH 2/2] package/zile: add Zile is Lossy Emacs editor Alex Bennée
2014-04-07 20:33   ` Yann E. MORIN
2014-04-08 10:19     ` Alex Bennée
2014-04-08 16:16       ` Yann E. MORIN [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=20140408161653.GA3199@free.fr \
    --to=yann.morin.1998@free.fr \
    --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