BUG: xchm 1.13 defaults to Mac version of wxWidgets

[gui-dos (Guido Soranzio)]

When not providing any flag to configure, xchm builds using the Mac version of wxWidgets.

The dependency on wxgtk should be specific of a x11 variant.

[afb@…]

I cannot reproduce this. It seems to be using /opt/local/bin/wx-config and picks up wxGTK ?

[gui-dos (Guido Soranzio)]

Because wxGTK'wx-config conflicts with the one already provided by wxWidgets, I suggested that the xchm's x11 version should be provided as a variant, otherwise the activation phase fails and even the casual user is requested to de/ativate the tho versions.

[afb@…]

Ah, I see. Yes, this is a known shortcoming in MacPorts wxWidgets (only one at a time)

Feel free to borrow the ugly hackaround that I use in some of my own wxWidgets ports...

platform macosx {}
if { [variant_isset macosx] && ![variant_isset x11] } { default_variants +aqua }
if { [variant_isset puredarwin] } { default_variants +x11 }
if { [variant_isset freebsd] } { default_variants +x11 }

variant aqua requires macosx description "Use the wxMac port of wxWidgets" {

depends_lib-append	port:wxWidgets

}

variant x11 conflicts aqua description "Use the wxGTK port of wxWidgets" {

depends_lib-append	port:wxgtk

}

[markd@…]

Is X11 optional for xchm? I did not think so.

[(none)]

Milestone Port Bugs deleted

[mojca (Mojca Miklavec)]

I'm aware that this is an ancient ticket, but xchm 1.22 seems to work of with wxWidgets 2.9, at least for me. See #38375. Feel free to test in case that you are still interested in xchm. Once I commit the patches, I plan to close this ticket with "it's ok to depend on native wxWidgets". Now a better question would be: why is the port in x11?

[mojca (Mojca Miklavec)]

Fixed in r110276. The port now uses cocoa exclusively. There is wxgtk, but I don't see any reason to use it.