From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 9 Oct 2002 12:23:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 9 Oct 2002 12:23:46 -0400 Received: from smtpzilla5.xs4all.nl ([194.109.127.141]:24587 "EHLO smtpzilla5.xs4all.nl") by vger.kernel.org with ESMTP id ; Wed, 9 Oct 2002 12:23:45 -0400 Date: Wed, 9 Oct 2002 18:29:03 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@serv To: "Randy.Dunlap" cc: Linus Torvalds , Brendan J Simon , linux-kernel , kbuild-devel Subject: Re: [kbuild-devel] Re: linux kernel conf 0.8 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Wed, 9 Oct 2002, Randy.Dunlap wrote: > So I think that you and Roman are close to agreement, when Roman > has the library backend ready. Of course someone needs to do a > "reference implementation" with it also, but it doesn't need to > ship with the kernel. We ship BK documentation, so shipping a small QT app can't be that problematic. :) Creating the library isn't that difficult (kbuild is currently my problem here) and I'll still have to write some API documentation for it and some glue code to load the library. bye, Roman