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 21:45:41 +0000 (UTC)	[thread overview]
Message-ID: <jhueu4$u5p$1@dough.gmane.org> (raw)
In-Reply-To: CAC78GpcJ8nZ0QrZ01a0sDgVxV7kN12ShRi27Cv8sGLg4-TKXgQ@mail.gmail.com

On 2012-02-20, J.C. Woltz <jwoltz@gmail.com> wrote:
> On Mon, Feb 20, 2012 at 3:41 PM, Grant Edwards
><grant.b.edwards@gmail.com> wrote:
>>
>> 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.
>
> The post-build script can be where you want it :) When you define the
> post build script to run, it is relative to the buildroot main
> directory

That's the bit of info I was looking for.  I'd been trying to figure
that out via trial-and-error for a while, but I'd been editing the
defautl config file without ever regenerating the .config file in the
output directory -- so it was all "error" and no "trial".

> Personally, I keep my post-build is a directory structure like:
> board/manufacture/model/post-build.sh

I prefer to modify the buildroot source tree as little as possible (it
makes upgrading to a new version easier).  So I keep everything
outside it that I can.  I've put what used to be my
package/customize/source directory in "../customfiles", my post-build
script in "../postbuild.sh", and my output directory is "../output".

>> 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.
>
> Agreed
>
> Somewhere I saw some slides that had a recommended way to do this. It
> also had a minimal post-build script to run. It is on the mailing
> list somewhere.

I think somebody posted a pointer to a week or so back when I was
asking about a change to the customize.mk file.

-- 
Grant Edwards               grant.b.edwards        Yow! I'm having a RELIGIOUS
                                  at               EXPERIENCE ... and I don't
                              gmail.com            take any DRUGS

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

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20 20:41 [Buildroot] Where does post-build script belong? Grant Edwards
2012-02-20 21:00 ` J.C. Woltz
2012-02-20 21:45   ` Grant Edwards [this message]
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='jhueu4$u5p$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