From: Tom <fivemiletom@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot and perforce.
Date: Sat, 22 Sep 2007 02:09:50 -0700 [thread overview]
Message-ID: <46F4DBDE.4010309@gmail.com> (raw)
In-Reply-To: <406A31B117F2734987636D6CCC93EE3CB05B69@ehost011-3.exch011.intermedia.net>
Leonid wrote:
>> + any config files your builroot uses which are easiest kept in a
>
>> sperate folder, [cfg].
>
>>
>
>
>
> What files do you mean? Pre-configured stuff for certain boards?
First, there is [br]/.config for the main buildroot configuration. This
might in turn reference two more files *.config, one for uclibc and one
for busybox, look in the main .config file.
>> [br]/target.../..._skeleton.)
>
>>
>
>
>
> So, ...skeleton plays a role of "static" files which will be simply
>
> copied into filesystem tree, right?
Right.
> Staging dir will hold toolchain itself (binaries/libraries) as far as I
>
> know. Normally people won't modify toolchain. I even don't want
>
> buildroot will create toolchain each and every time - is there an
>
> "official" way to disable toolchain creation?
There is the "use external toolchain" option.
next prev parent reply other threads:[~2007-09-22 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 7:22 [Buildroot] Buildroot and perforce Leonid
2007-09-22 9:09 ` Tom [this message]
2007-09-23 22:59 ` Adam Hawes
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=46F4DBDE.4010309@gmail.com \
--to=fivemiletom@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