> Il 17/01/2024 03:00 CET Joshua Root ha scritto:
> I agree that the UX surrounding the quartz/x11 choice is bad.
> Unfortunately it's harder to fix than you might hope, and gtk3 itself
> may be the easiest part of the puzzle. A number of other ports like
> glib2 and cairo are also involved,
On 17/1/2024 05:42, Valerio Messina via macports-dev wrote:
Using the pre-built gtk3 from macport (and osxcross), saved me the
library built time just for test of my apps, and the requirement to
access macOS on every run.
Then I discovered to start the app I had to install Xquartz on the real
sorry, I have never made a native port installation.
But given the syntax I found online:
$ port install + -
I expect a user can install every variant
If only default variant is pre-built what is shown by:
$ port variants gtk3
?
Native gtk3 building on macOS is trivial, I made that from
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
, 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
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
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
