[gtk-osx] Modernize jhbuild-gtk-osx-custom-example

[John Ralls <jralls src gnome org>]

commit 30031fbf2638eff51849fd5b55c49998aa2e4f98
Author: John Ralls <jralls ceridwen us>
Date:   Mon Apr 12 14:33:43 2021 -0700

    Modernize jhbuild-gtk-osx-custom-example

 jhbuildrc-gtk-osx-custom-example | 97 +++++++++++++---------------------------
 1 file changed, 30 insertions(+), 67 deletions(-)
---
diff --git a/jhbuildrc-gtk-osx-custom-example b/jhbuildrc-gtk-osx-custom-example
index cc722778..f0b73a19 100644
--- a/jhbuildrc-gtk-osx-custom-example
+++ b/jhbuildrc-gtk-osx-custom-example
@@ -4,27 +4,28 @@
 # things you can do to customize your build with python commands.
 
 # The URL for repositories can be overridden. This is how you'd set
-# your developer access to an SVN repo. It doesn't work, of course,
-# because gnome has migrated to git.
+# your developer access to a git repo.
 #
-# repos["svn.gnome.org"] = "svn+ssh://myusername svn gnome org/svn/"
+# repos["git.gnome.org"] = "git gitlab gnome org:GNOME"
 
-# You can set the default setup here.
+#  _gtk_osx_default_build designates a suffix that if set will load a
+#  second customization file after jhbuildrc-custom. For example,
+#    _gtk_osx_default_build = "fw-10.4"
+# would load the file .jhbuildrc-fw-10.4. This is a default that can
+# be overridded by setting the environment variable $JHB to a
+# different suffix.
 #
-# _gtk_osx_default_build = "fw-10.4"
-# 
-# or set things up with an environment variable: 
+# You can also read environment variables and decide what to do based
+# on their values:
 
-_jhb = os.environ.get("JHB")
-if _jhb is None:
+_target = os.environ.get("TARGET")
+if _target is None:
     # The default setup...
     # checkoutroot = os.path.expanduser("~/Source/gtk")
     # prefix = "/opt/gtk"
     pass
-# Do note, though, that jhbuildrc-gtk-osx also uses $JHB to find
-# another customization file that is loaded after this one. You can,
-# of course, define your own environment variables for passing in
-# parameters.
+#
+# 
 
 # The moduleset can be overridden.
 #
@@ -36,14 +37,18 @@ if _jhb is None:
 
 # You can skip modules.
 #
-# skip.append("libglade")
+# skip.append("python3")
 #
 #or put them back:
 #
-# if "libglade" in skip:
-#      skip.remove("libglade")
+# if "python3" in skip:
+#      skip.remove("python3")
 
-# Uncomment the following if you're running OSX 10.11 or later and SIP (see 
https://developer.apple.com/library/prerelease/mac/documentation/Security/Conceptual/System_Integrity_Protection_Guide/RuntimeProtections/RuntimeProtections.html)
+# See the jhbuild configuration file reference,
+# https://developer.gnome.org/jhbuild/stable/config-reference.html.en
+# for complete documentation of more ways to customize your build.
+
+# Uncomment the following if SIP (see 
https://developer.apple.com/library/prerelease/mac/documentation/Security/Conceptual/System_Integrity_Protection_Guide/RuntimeProtections/RuntimeProtections.html)
 # causes shell-script build failures. You'll also need to edit those
 # shell scripts to change the shebang from /bin/sh to $PREFIX/bin/bash.
 # Note that /usr/bin/env bash won't work, because it will also strip
@@ -74,22 +79,15 @@ if _jhb is None:
 # can run, in the form "10.X" or "native" (the default). It sets
 # MACOS_DEPLOYMENT_TARGET and the -macosx-version-min CFLAG.
 
-# From Xcode 7/MacOSX10.11.sdk on Apple has provided a new format
-# dylib stub that links with dylibs from earlier versions of MacOS and
-# has been tested to work back to 10.6 if MACOS_X_VERSION_MIN is set
-# appropriately. Earlier SDKs lack this feature and may or may not
-# actually work on MacOS X versions earlier than the SDK's; whether
-# they do depends on whether the SDK contains a newer "compatibility
-# version" library than the system on which you're attempting to run
-# and which is required by your application.
+# Unlike earlier SDKs, recent versions of Xcode have included SDKs
+# that can successfully compile programs that will run on earlier
+# versions of macOS, so it's reasonable to build for e.g. 10.13 while
+# running 11.2 and the Xcode 12.2 that ships with it.
 
 # Architecture is a list for backwards compatibility; it can contain
-# "i386" and/or "x86_64" and defaults to the machine's architecture if
+# "x86_64" and "arm64" and defaults to the machine's architecture if
 # left out. Passing both architectures will in theory build a
-# universal binary but this is untested. Since MacOS X 10.7 and later
-# run only on x86_64 systems it doesn't make sense to change this
-# unless you're targeting 10.6. 32-bit ("i386") programs run fine on
-# 64-bit systems.
+# universal binary but this is untested.
 
 # There are also some utility functions which you may find useful:
 #
@@ -112,41 +110,6 @@ if _jhb is None:
 setup_sdk()
 
 # Comment out the previous and uncomment this one to build for all
-# systems running SnowLeopard and later:
-# setup_sdk(target="10.6")
-
-# Modify the arguments passed to configure:
-#
-# module_autogenargs["libglade"] = "--enable-static"
-#
-# or simply  add to them:
-#
-# append_autogenargs("libglade", "--enable-static")
-# 
-# Note that in either case the args will be added *after* the args in
-# the module's autogenargs attribute.
-#
-# Tell Git to use a different module and branch (not tag!):
-#
-# branches["gtk-engines"] = ("gtk-css-engine", "bzr")
-#
-# Or just switch branches
-#
-# branches["gtk+"] = (None, "gtk-2-18")
-#
-# Tarballs take a whole URL for branches:
-#
-# branches["python"] = "http://www.python.org/ftp/python/2.6.4/Python-2.6.4.tar.bz2";
-#
-# Note that if the module has hash, md5sum, or size attributes and the
-# branch download doesn't match, jhbuild will error out. Open a shell,
-# untar the tarball yourself, quit the shell, and select "ignore
-# error". Don't try this with modules that need patches unless you're
-# sure that the updated version doesn't need them.
-#
-# Set an environment variable:
-#
-# os.environ["CC"] = "/usr/bin/gcc-4.0"
-
+# systems running Mojave and later:
+# setup_sdk(target="10.14")
 
-# And more...