archive mirror
 help / color / mirror / Atom feed
From: David Dillow <>
Subject: [BK PATCH 0/3] Teach kbuild to pull files from BK repository
Date: 04 Dec 2003 22:32:01 -0500	[thread overview]
Message-ID: <> (raw)

I finally got tired of having to run "bk -r get" before doing a build, so I
taught the kbuild system to get the needed files for me. I did most of the
work before Sam added the KBUILD_OUTPUT option, so this doesn't work when
you're building to a different directory. It could probably be added with
a few tweaks to scripts/getfiles, but I'm lazy, and don't use KBUILD_OUTPUT
myself. If that scratches your itch, then feel free to take this code and
run with it. Same goes for CVS or subversion -- it should not be very
difficult to get those working as well.

This isn't really meant for inclusion, just something that makes my life
easier. Maybe it will make your's easier too. Though, I'll have to do many,
many builds in order to make up for the lost time.... :)

Anyways, the patches follow, or BK users (the intended audience) can do a

	bk pull

This will update the following files:

 Makefile                            |   89 +++++++++++--
 drivers/scsi/aic7xxx/Makefile       |    2 
 scripts/              |   13 +
 scripts/Makefile.clean              |    6 
 scripts/Makefile.repo               |  124 ++++++++++++++++++
 scripts/depkconfig                  |   58 ++++++++
 scripts/getfiles                    |  245 ++++++++++++++++++++++++++++++++++++
 scripts/kconfig/Makefile            |   30 ++--
 scripts/kconfig/lex.zconf.c_shipped |  114 +++++++++++++++-
 scripts/kconfig/listkconfigs.c      |   22 +++
 scripts/kconfig/lkc.h               |    2 
 scripts/kconfig/zconf.l             |   29 +++-
 12 files changed, 697 insertions(+), 37 deletions(-)

through these ChangeSets:

<> (03/12/04 1.1507)
   Make the build process a bit less verbose and a bit cleaner during a build
   from a "cleaned" repository.

<> (03/12/04 1.1506)
   Teach the kbuild system how to retrieve the Kconfig files from
   the repository. This involves modifying the kconfig lexer/parser
   to give us a list of sourced Kconfig files so that we can tell
   make about the dependencies. Then is just a matter of makeing sure
   that make will extract those files before they are needed in the
   build process.

<> (03/12/03 1.1505)
   Teach the kbuild system how to pull needed files from the repository.
   With this, you can copy your config into a clean repository, type
   make, and it will build the kernel, retrieving any needed files that
   have not yet been checked out.
   We cannot use make's default implicit rules to do this, as we do
   not list the dependencies for each file in the Makefiles, nor do we
   want to. Therefore, we use the getfiles script to parse error
   messages from a gcc -E run to determine which files are missing.
   This does not handle Kconfig files yet, only the source files.

             reply	other threads:[~2003-12-05  3:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-05  3:32 David Dillow [this message]
2003-12-08  3:06 ` [BK PATCH 0/3] Teach kbuild to pull files from BK repository Ricky Beam
2003-12-08 15:12   ` David Dillow

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:

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

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).