svn commit: r472232 - in head/x11-toolkits/wxgtk31: . files

[Alexey Dokuchaev]

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