From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 2 03:36:33 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76E28106564A for ; Tue, 2 Dec 2008 03:36:33 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34]) by mx1.freebsd.org (Postfix) with ESMTP id 5E3A48FC18 for ; Tue, 2 Dec 2008 03:36:33 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id mB23aWIh082264 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Dec 2008 19:36:32 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id mB23aWYt082263; Mon, 1 Dec 2008 19:36:32 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA07474; Mon, 1 Dec 08 19:12:52 PST Date: Mon, 01 Dec 2008 19:16:22 -0800 From: perryh@pluto.rain.com To: laladelausanne@gmail.com Message-Id: <4934a886.x0zd2wiIrFlfIq2T%perryh@pluto.rain.com> References: <711D7381-D852-4B6B-991A-84BA6DEFB679@gmail.com> <49332E5C.9020303@freebsd.org> <200812011231.52262.fbsd.hackers@rachie.is-a-geek.net> In-Reply-To: <200812011231.52262.fbsd.hackers@rachie.is-a-geek.net> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: How to build kernel module spread on subdirectories? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2008 03:36:33 -0000 > As you discovered, includes are done before targets. You would > need seperate invocations of make, to generate the file and get > it included. Provided the module in question is contemplated for delivery as a port, rather than as part of the base -- so that having a build dependency on a port is tolerable -- perhaps it would be more easily built using devel/gmake?