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] Suggestion for config menu help for path values
Date: Wed, 23 Jun 2010 13:53:05 +0000 (UTC)	[thread overview]
Message-ID: <hvt3k1$167$1@dough.gmane.org> (raw)
In-Reply-To: 20100623090429.539f3c0f@surf

On 2010-06-23, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

>> Right now I'm trying to figure out the CWD when the post-build script
>> is called, and I'll submit a help patch when I figure out the answer.
>
> All Buildroot Makefiles are interpreted from the top Buildroot source
> directory, as we only use Makefile inclusion and not recursive make.
> So, in general, relative paths are interpreted relatively to the top
> Buildroot source directory.

I had initially assumed that scripts belonged in the "scripts"
directory.  That didn't work.  Then I tried the top of the source
directory.  That didn't work either.  I finally figured out that the
script path wasn't interpreted relative to a fixed point, but it was
left up to the shell to find using the normal PATH mechanism (so it
had to be ./filename rather than filename).

I'll submit a patch to the docs.

> Don't hesitate to point us those inconsistencies, and either submit a
> patch to fix them or ask us to do so :-)

I will.

-- 
Grant Edwards               grant.b.edwards        Yow! It's a lot of fun
                                  at               being alive ... I wonder if
                              gmail.com            my bed is made?!?

      reply	other threads:[~2010-06-23 13:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22 21:10 [Buildroot] Suggestion for config menu help for path values Grant Edwards
2010-06-22 21:31 ` Grant Edwards
2010-06-23  7:04 ` Thomas Petazzoni
2010-06-23 13:53   ` Grant Edwards [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='hvt3k1$167$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