linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	kbuild-devel <kbuild-devel@lists.sourceforge.net>,
	Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Subject: Re: [kbuild-devel] linux kernel conf 0.6
Date: Sun, 22 Sep 2002 17:24:12 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0209221648180.338-100000@serv> (raw)
In-Reply-To: <20020920071055.A1852@mars.ravnborg.org>

Hi,

On Fri, 20 Sep 2002, Sam Ravnborg wrote:

> I have been working on integrating lkc with kbuild.
> Here is the result.

Thanks, nice work. :)

> Rules.make
> - Added infrastructure to support host-ccprogs, in other words
>   support tools written (partly) in c++.

There are all compiled with gcc instead of g++, are you sure that will ok
with all supported gcc versions?

> scripts/lkc/Makefile*
> - As kbuild does not distingush between individual objects,
>   used for a given target, but (try to) build them all, I have
>   found a solution where I create one Makefile for each executable.
>   I could not see a clean way to integrate this in kbuild, and finally
>   decided that in this special case a number of Makefiles did not
>   hurt too much.

Here I thought about using "ifeq ($(MAKECMDGOALS),...)" to keep them in a
single file. Did you try something like this?

> flex/bison
> - Prepared for "_shipped" files.
>   Rename lex.zconf.c to lex.zconf.c_shipped etc. in the version
>   reday to go in the kernel.

This works quite well for users, but it's very annoying for the developer.
Kai, any chances to use md5sum for this at some point, e.g. with a helper
script like this:

set -e
src=$1
dst=$2
shift 2

test -f $dst && tail -1 $dst | sed 's,/\* \(.*\) \*/,\1,' | md5sum -c && touch $dst && exit 0
echo "$@"
"$@"
echo "/* $(md5sum $src) */" >> $dst

The only problem with this script is that it only supports a single input
and output file.

Something else I'd like to have for later is the ability to compile
$(sharedobjs) as a shared library and install it somewhere so it can be
used by external programs.

bye, Roman



  reply	other threads:[~2002-09-22 15:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-16 23:16 linux kernel conf 0.6 Roman Zippel
2002-09-20  5:10 ` [kbuild-devel] " Sam Ravnborg
2002-09-22 15:24   ` Roman Zippel [this message]
2002-09-22 22:36     ` Kai Germaschewski
2002-09-22 22:41       ` Jeff Garzik
2002-09-22 22:51         ` Kai Germaschewski
2002-09-22 22:53           ` Jeff Garzik
2002-09-22 23:03             ` Kai Germaschewski
2002-09-23  1:48               ` Jeff Garzik
2002-09-22 23:07           ` Roman Zippel
2002-09-22 23:19             ` Kai Germaschewski
2002-09-22 23:30               ` Roman Zippel
2002-09-23  1:50               ` Jeff Garzik
2002-09-23 19:59       ` Sam Ravnborg
2002-10-03 11:17       ` Roman Zippel

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=Pine.LNX.4.44.0209221648180.338-100000@serv \
    --to=zippel@linux-m68k.org \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /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;
as well as URLs for NNTP newsgroup(s).