# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4
# This PortGroup is to be used with all projects that depend on wxWidgets
# (including some that need wxPython).
# After the PortSystem 1.0 line, put:
# PortGroup wxWidgets 1.0
# Then, assuming that the port needs wxWidgets 3.0, use
# wxWidgets.use wxWidgets-3.0
# to specify the version/variant of wxWidgets.
# Valid options for wxWidgets.use are as follows:
# You should generally use this one unless there are valid reasons for
# This is almost the same as 'wxWidgets-3.0' except that a separate
# instance of wxWidgets was made available for cases when wxPython
# releases lag behind the wxWidgets releases.
# You should only use this option for ports that need both wxPython
# (usually py27-wxpython) as well as require linking of C++ code against
# wxWidgets via the usual ./configure && make. Using 'wxPython-3.0'
# avoids any version mismatches between wxPython and wxWidgets.
# * 'wxWidgets-2.8' or 'wxGTK-2.8'
# For projects that are still not fully compatible with wxWidgets 3.0
# (even though we strongly encourage you to try to make the package work
# with wxWidgets 3.0 instead).
# 'wxWidgets-2.8' requires Carbon and can only be compiled as 32-bit app
# against MacOSX10.6.sdk or earlier. It gives a native look and feel and
# might be preferred to wxGTK on systems where it works.
# 'wxGTK-2.8' should work on modern systems as well, but depends on X11.
# Mainly for testing purposes. wxGTK 3.0 currently uses GTK 3 (and could
# be compiled against quartz if desired). Many programs make assumptions
# that GTK != Mac, some programs work with wxGTK, but not with wxOSX.
# This could help you write proper patches and submit them upstream.
# * 'wxWidgets-3.0-cxx11'
# A workaround to make software written in C++11 work on macOS < 10.9.
# This is just wxWidgets 3.0 compiled against libc++ even where libstdc++
# https://trac.macports.org/wiki/LibcxxOnOlderSystems
# At the moment still mainly for development purposes, for testing ports
# for compatibility with wxWidgets 3.1/3.2.
# It uses wxWidgets 3.1 at the moment, but will switch to wxWidgets 3.2
# after the first release of version 3.2 becomes available.
# If you already want to provide a special variant for your port with
# 'wxWidgtes-3.2', you might only need a revbump after the switch to 3.2
# You should note an important aspect of 'wxWidgets.use' though: