Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751324AbVIRHuM (ORCPT ); Sun, 18 Sep 2005 03:50:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751325AbVIRHuM (ORCPT ); Sun, 18 Sep 2005 03:50:12 -0400 Received: from mx2.palmsource.com ([12.7.175.14]:54240 "EHLO mx2.palmsource.com") by vger.kernel.org with ESMTP id S1751324AbVIRHuL convert rfc822-to-8bit (ORCPT ); Sun, 18 Sep 2005 03:50:11 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT Subject: RE: Why don't we separate menuconfig from the kernel? Date: Sun, 18 Sep 2005 00:50:10 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Why don't we separate menuconfig from the kernel? Thread-Index: AcW8IrdMOtmdoj4VQDyUXoHVL1rL1wAApuiA From: "Martin Fouts" To: "Sam Ravnborg" Cc: , "Krzysztof Halasa" , Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 668 Lines: 18 > I'm a bit confused. > Do you want to take a copy of kbuild or kconfig? > > kbuild is much more intiminate than kconfig althougth the > latter has a few kernel only issues too. Kconfig is nice without kbuild, but if you want to automate it in a makefile, you'll want the bits of kbuild from the top level makefile that do that. So I guess my personal answer is I want kconfig with just enough kbuild to make it nice. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/