From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kmu-office.ch (mail.kmu-office.ch [178.209.48.109]) by mail.openembedded.org (Postfix) with ESMTP id F1D62787B0 for ; Tue, 12 Dec 2017 07:53:51 +0000 (UTC) Received: from webmail.kmu-office.ch (unknown [178.209.48.103]) by mail.kmu-office.ch (Postfix) with ESMTPSA id AC54B5C1878; Tue, 12 Dec 2017 08:47:52 +0100 (CET) MIME-Version: 1.0 Date: Tue, 12 Dec 2017 08:48:58 +0100 From: Stefan Agner To: Otavio Salvador , "Burton, Ross" In-Reply-To: References: <20171211135720.38714-1-stefan@agner.ch> <1b5588ed9cdad157c4129eb45d2a0fe0@agner.ch> <1513006338.9676.5.camel@gmail.com> <1513006625.9676.9.camel@gmail.com> Message-ID: X-Sender: stefan@agner.ch User-Agent: Roundcube Webmail/1.2.5 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=agner.ch; s=dkim; t=1513064872; bh=r3sJFNmy/lKTDzg0z8iZ9NNufWG5p/uAd4LjfWIhDYA=; h=MIME-Version:Content-Type:Content-Transfer-Encoding:Date:From:To:Cc:Subject:In-Reply-To:References:Message-ID; b=GnKOTOO5YmhmpDlXBkvXPkYXC5T+i4tHhRPNScDXX5WsY3W6fdwzwNKHTKXi+N/oo88pR0jdcibZdp8QenQV/M1Ud0pl2zZfQdxBF14uC/VvUlJtFQz+Ei4BPvmdycJlt0wG7lku+z+NCba8bK/2Y9u13nTW++p5p4wiU1BJJrQ= Cc: Stefan Agner , Otavio Salvador , OE-core Subject: Re: [PATCH] waf.bbclass: explicitly pass libdir X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Dec 2017 07:53:52 -0000 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On 2017-12-11 18:15, Otavio Salvador wrote: > On Mon, Dec 11, 2017 at 3:09 PM, Burton, Ross wrote: >> On 11 December 2017 at 15:37, Joshua Watt wrote: >>> >>> Vanilla waf only supports --prefix, --libdir, and --bindir. Anything else >>> is a result of loading the gnu_dirs tool, which not all projects are >>> required to do. >>> >>> >>> Sorry, hit send too soo: waf (at least version 2.0) also errors out on >>> unknown options. I think the three I listed are the only ones we can do >>> generically. There might be some way to easily adding the rest if you know >>> waf is loading gnu_dirs >> >> >> One option would be for waf.bbclass to check if WAF_USES_GNU_DIRS is set >> (defaulting to 0) and pass the full set of path options automatically. > > Possible. But passing the standard ones solve 99% of the issues. > I am with Otavio here. Also, adding the standard ones and adding the additional GNU_DIRS would best be done in two independent patches anyway. For now I'd rather prefer to only add the standard ones. -- Stefan