Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Oliver Niesner <oliver.niesner@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] understanding_cerowrt_buildsystem
Date: Thu, 20 Sep 2012 09:10:01 +0200	[thread overview]
Message-ID: <505AC149.2000905@googlemail.com> (raw)

Hi!

After a zillion tries i managed to build a cerowrt image for myself.
It's not really clear what happened when it fails, but sometimes 
building a package again does the trick.
Here is another question to understand  better:

When building a package (eg. selecting a new one in menuconfig) does the 
buildsystem take care of
dependencies in other "parts" of the system? Let's say i do a package 
which requires something new
must be build in the linux kernel, but in the build before the kernel is 
already succesfully compiled. Will the
buildsystem automatically detect that it is neccessary to build the 
kernel again, or do i have to do it
manually, eg. do a "make clean"? My guess is that i have to do it manually.

Thanks, for clearing things up

Oliver

             reply	other threads:[~2012-09-20  7:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20  7:10 Oliver Niesner [this message]
2012-09-20 10:41 ` Maciej Soltysiak
2012-09-20 13:05   ` Mark Constable
2012-09-21 15:35     ` Dave Taht
2012-09-21 17:04       ` Mark Constable
2012-09-21 21:08       ` Maciej Soltysiak
2012-09-21 21:22         ` Dave Taht
2012-09-21 22:16 ` Dave Taht
2012-09-22  2:32   ` Outback Dingo

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=505AC149.2000905@googlemail.com \
    --to=oliver.niesner@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.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