Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Custom automake arguments
Date: Thu, 27 Oct 2011 00:10:11 +0200	[thread overview]
Message-ID: <201110270010.12137.arnout@mind.be> (raw)
In-Reply-To: <CANdC7UEcaK0AkPfL_Rr_f=DwXbT9=ikhn3H9a+NyLA1CEtubfQ@mail.gmail.com>

On Tuesday, October 25, 2011 15:15:42 Allan Nielsen wrote:
> Hi
> 
> Is it possible to parse custom package specifick arguments to automake
> (run'ed through autorecong)
> 
> I have tried this, but it does not seem to work:
> foo-configure: override AUTOMAKE:=$(HOST_DIR)/usr/bin/automake
> $(FOO_AUTOMAKE_FLAGS)
> 
> Best Regards
> Allan W. Nielsen

 I'm not entirely sure what you mean.  However, if you just want to specify 
arguments to autoreconf:  autoreconf is called as

$(AUTORECONF) $($(PKG)_AUTORECONF_OPT)

 so set FOO_AUTORECONF_OPT before calling AUTOTARGETS to override the default 
(which is empty).

 However, if you want to run automake instead of autoreconf, that's not really 
supported.  You could hack away using overrides, but probably it's much 
cleaner to do something like:

define FOO_AUTOMAKE_HOOK
   $(HOST_DIR)/usr/bin/automake $(FOO_AUTOMAKE_FLAGS)
endef
FOO_PRE_CONFIGURE_HOOKS += FOO_AUTOMAKE_HOOK
FOO_DEPENDENCIES += host-automake


 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:  31BB CF53 8660 6F88 345D  54CC A836 5879 20D7 CF43

      reply	other threads:[~2011-10-26 22:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25 13:15 [Buildroot] Custom automake arguments Allan Nielsen
2011-10-26 22:10 ` 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=201110270010.12137.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