Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Where does post-build script belong?
Date: Mon, 20 Feb 2012 20:41:31 +0000 (UTC)	[thread overview]
Message-ID: <jhub5r$smv$1@dough.gmane.org> (raw)

I'm trying to use a post-build script to fix up the init.d/S59snmpd
file, but I can't figure out what the post-build script path should
be.

It would be awfully nice if the help text for "path" config options
explained what directory the path is relative to. Alternatively, it
might be nice if there were some variables that could be used in
user-configured paths to anchor the path to specific points in the
build, output, or source tree.

Putting an absolute path in a config file doesn't really seem like a
workable option.

-- 
Grant Edwards               grant.b.edwards        Yow! Now, let's SEND OUT
                                  at               for QUICHE!!
                              gmail.com            

             reply	other threads:[~2012-02-20 20:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20 20:41 Grant Edwards [this message]
2012-02-20 21:00 ` [Buildroot] Where does post-build script belong? J.C. Woltz
2012-02-20 21:45   ` Grant Edwards
2012-02-21  8:44     ` Luca Ceresoli
2012-02-21 14:54       ` Grant Edwards
2012-02-28 20:38         ` Arnout Vandecappelle
2012-02-28 21:06           ` Grant Edwards
2012-02-28 21:29             ` Steve Calfee
2012-02-28 21:36               ` Grant Edwards
2012-02-28 22:06                 ` Steve Calfee
2012-02-28 22:18                   ` Grant Edwards
2012-03-16 21:30                     ` Peter Korsgaard
2012-02-28 22:19                   ` Arnout Vandecappelle
2012-02-29  7:41                     ` Thomas De Schampheleire
2012-03-16 21:32                       ` Peter Korsgaard
2012-02-28 22:18                 ` Arnout Vandecappelle

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='jhub5r$smv$1@dough.gmane.org' \
    --to=grant.b.edwards@gmail.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