AFAIK ports are only being pre-built with the default variant.
GTK should be trivial to build though. On Jan 14, 2024 at 23:58 +0800, Valerio Messina via macports-dev <macports-dev@lists.macports.org>, wrote: > I'm not sure this is the right list to ask for pre-built macports. > > In case can you please direct me to the right one? > > thank you, > Valerio > > > On 12/5/23 10:47 PM, Valerio Messina via macports-dev wrote: > > hi, > > as a user of osxcross, I also use the good of macports. > > I read that is not your main target, but tolerate cross-built from other > > OS. I'm on Debian. > > > > I saw there are pre-built packages here: > > https://packages.macports.org/ > > and this is where the 'osxcross-macport' get the packages. > > > > Native macport client has support for variants with something like: > > $ port variants <pkg> # show package variants > > $ port install <pkg> +<var1> -<var2> # install variant1, not variant2 > > > > I saw on packages.macports.org there are only X11 packages, and seems > > native quartz variant are missing. > > So for example for gtk3-devel: > > https://ports.macports.org/port/gtk3-devel/details/ > > is available for X11 backend only as pre-built for foreign OS. > > > > Is there a reason for this? > > > > Having native quartz pre-built packages will help developer to target > > quartz instead of xquartz, without the need to (cross)build the GTK > > itself. This is so for other library with variants. > > > > As now the bash script 'osxcross-macport' do not support variants, but > > I'm sure can be easily upgraded if packages server will host quartz > > variants. > > > > thank you for explanation and work, > > > -- > Valerio
