Building gnucash in native Quartz for macOS Mojave...?

Carlo Tambuatco oraclmaster at gmail.com
Sun Oct 28 09:03:10 UTC 2018



> On Oct 28, 2018, at 4:47 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
> 
> 
> 
> On Oct 27, 2018, at 19:46, Carlo Tambuatco wrote:
> 
>> I’ve got gnucash installed at the moment, but it’s the x11 build not the native quartz build.
>> 
>> I’ve been thinking about following the instructions detailed here:
>> 
>> https://wiki.gnucash.org/wiki/MacOSX/MacPortsDetail
>> 
>> for building the native quartz version of gnucash. 
>> 
>> The instructions say that I also need to install x11-free versions of dbus and cairo. Basically the 
>> instructions say if I don’t have x11-free versions of these ports, I should alter my variants.conf 
>> file to include:
>> +no_static
>> +no_x11
>> -x11
>> +quartz
>> 
>> Then install gnucash and its dependencies including x11-free versions of dbus and cairo. 
>> 
>> But then I was thinking when I migrate over to Mojave, and I have to reinstall everything anyway, I 
>> 
>> could alter my variants.conf file then follow the migration steps on macports.org and then x11-free 
>> 
>> versions of gnucash dependencies will be installed as well as gnucash being build for native quartz…
>> 
>> right? Theoretically?
>> 
>> Basically, I’m asking if altering the variants.conf file as outlined in the instructions then migrating 
>> 
>> over to Mojave per the steps on macports.org will result in a native quartz build of gnucash without 
>> 
>> breaking anything I’ve got installed. 
>> 
>> Heck, I’ll even include a full list of my installed ports just to ask if following these 
>> 
>> steps will break anything that you might know of… (it’s a bit long)
>> 
>> I see a lot of ‘arch=x86_64’ in that list, so those ports should not cause problems in Mojave, right?
>> 
>> Thanks in advance.
>> 
>> <myports.txt.zip>
>> 
>> 
> 
> 
> If you want to switch from X11 to Quartz, you should uninstall and reinstall ports, so doing so at migration time is ideal.
> 
> There are many occurrences of the string "+x11" in your myports.txt. You will not want those when switching to Quartz. Maybe editing myports.txt to remove all those "+x11"s before running it through the restoration process is sufficient.
> 
> 
> 

Okay, I thought so… 

So any ports of mine with archs=‘x86_64’ or archs=‘noarch’ won’t cause any problems on Mojave?

Did you see any other possible problematic ports in the list?

Thanks



More information about the macports-users mailing list