From owner-svn-ports-all@freebsd.org Wed Jun 13 18:57:16 2018 Return-Path: Delivered-To: svn-ports-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4FE7D1006EB6; Wed, 13 Jun 2018 18:57:16 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 09B3C740A9; Wed, 13 Jun 2018 18:57:16 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 0201017B49; Wed, 13 Jun 2018 18:57:15 +0000 (UTC) Date: Wed, 13 Jun 2018 18:57:15 +0000 From: Alexey Dokuchaev To: Yuri Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r472232 - in head/x11-toolkits/wxgtk31: . files Message-ID: <20180613185715.GA68070@FreeBSD.org> References: <201806120717.w5C7HA1e005551@repo.freebsd.org> <20180612113434.GA75210@FreeBSD.org> <20180613092827.GA41680@FreeBSD.org> <89f6cc7e-38d1-ac9e-9e82-41ab1ae514b7@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <89f6cc7e-38d1-ac9e-9e82-41ab1ae514b7@freebsd.org> User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 18:57:16 -0000 On Wed, Jun 13, 2018 at 10:42:49AM -0700, Yuri wrote: > On 06/13/18 02:28, Alexey Dokuchaev wrote: > >> If you just want to use wxWidgets for the port, you only need to set > >> USE_WX=3.1, and then use ${WX_CONFIG} and ${WXRC_CMD} to configure the > >> project. If some project hard-codes the config name executables, this > >> is a bug in that project. > > > > No, this is not the case, they use some API functions which are not > > available in 3.0, that's why I was not able to update it before 3.1 > > hit the tree. > > wxWidgets API changed in 3.1, so you need to say USE_WX=3.1 instead of > USE_WX=3.0. But, still, the only thing you do is to use USE_WX, > ${WX_CONFIG} and ${WXRC_CMD} in the ports that use wxWidgets. Well, OK, but WX_CONFIG and WXRC_CMD are not really part of the problem here (and even if they were, I surely know how to deal with it). > > I don't understand. How do you mean? Can I run wxWidgets ports without > > Gtk+ at all? > > The choice of Gtk2 vs. Gtk3 is abstracted away, such that users don't > need to know about it. This doesn't mean that Gtk itself can be > eliminated, you just don't need to worry about such details. Right, so I have to use some Gtk+. Now would you please make wxWidgets both Gtk+2/3 friendly? Flavor (preferred), an OPTION, or even a slave port would do for me as long as I can have Gtk+2 which is still supported by wxWidgets. Thanks, ./danfe