From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] How does an offline build work?
Date: Wed, 04 Jun 2008 23:10:26 +0200 [thread overview]
Message-ID: <87iqwoq531.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <326f33790806041344p65f55e31i3e9a507ef1176a72@mail.gmail.com> (Arun Reddy's message of "Wed\, 4 Jun 2008 13\:44\:56 -0700")
>>>>> "Arun" == Arun Reddy <reddyac@gmail.com> writes:
Hi,
Arun> I was curious as to how an offline build works. When I first
Arun> starting using Buildroot, I downloaded a snapshot for that
Arun> day. As I used that same snapshot for about a month, I would
Arun> run into different Buildroot issues, which came up whenever new
Arun> changes were implemented. I assumed that whenever I typed
Arun> "make" Buildroot is automatically being updated with those
Arun> changes which could be affecting certain things.
Buildroot itself never gets updated by running make.
Arun> I am now using Subversion access so I can update the source
Arun> tree whenever I want, but if I were to go back to using the
Arun> Buildroot snapshot image, will doing an offline build "make
Arun> source" allow me to do a build without Buildroot being updated?
Arun> Or is it just a way for all the files, packages, etc, to be
Arun> downloaded first so that I can continue the build in a place
Arun> where I do not have network access?
make source downloads the tarballs (E.G. source code) of all the
enabled packages into the download directory (dl by default). It is
indeed meant for offline use, E.G. you connect to the internet and run
make source, and once it is completed you will have all the needed
tarballs in your download directory and you can do the build without
network access.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-06-04 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 20:44 [Buildroot] How does an offline build work? Arun Reddy
2008-06-04 21:10 ` Peter Korsgaard [this message]
2008-06-04 21:26 ` Bernhard Fischer
2008-06-04 22:26 ` Arun Reddy
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=87iqwoq531.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.