[GNC-dev] Compiling Gnucash on MacOS - not for the faint of heart...

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

[GNC-dev] Compiling Gnucash on MacOS - not for the faint of heart...

chris graves
Okay, so I'm an obvious newb here, with the desire to help resolve a gnucash bug (https://bugs.gnucash.org/show_bug.cgi?id=794755 <https://bugs.gnucash.org/show_bug.cgi?id=794755>).

I'm following these build instructions: https://wiki.gnucash.org/wiki/MacOSX/Quartz <https://wiki.gnucash.org/wiki/MacOSX/Quartz>

The first issue was a file not found error when executing jhbuild.
Resolved this issue by changing the first line from:
#!/usr/bin/env python2
to
#!/usr/bin/env python2.7

even though entering python2 from the terminal worked just fine...

The second issue was jhbuild not being able to find the module: meta-gnucash-stable.
In perusing https://raw.githubusercontent.com/gnucash/gnucash-on-osx/master/modulesets/gnucash.modules <https://raw.githubusercontent.com/gnucash/gnucash-on-osx/master/modulesets/gnucash.modules>, it appears
the module name to use is: gnucash.  Setting it to this in ~/.jhbuildrc-custom got me past this issue.

The place I'm stuck at now is:
*** Checking out iso-codes *** [62/76]
curl --continue-at - -L http://pkg-isocodes.alioth.debian.org/downloads/iso-codes-3.67.tar.xz -o /Users/chris/gtk/source/pkgs/iso-codes-3.67.tar.xz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (6) Could not resolve host: pkg-isocodes.alioth.debian.org
*** Error during phase checkout of iso-codes: ########## Error running curl --continue-at - -L http://pkg-isocodes.alioth.debian.org/downloads/iso-codes-3.67.tar.xz -o /Users/chris/gtk/source/pkgs/iso-codes-3.67.tar.xz *** [62/76]

This page: https://wiki.debian.org/Alioth/PackagingProject <https://wiki.debian.org/Alioth/PackagingProject> indicates:
Alioth is deprecated, and you should not add any new projects

In particular the gforce component is broken in many surprising ways, and there is nobody around to fix it or work around its quirks. Please do not pester the remaining caretaker with requests.

So, I'm not quite sure how to proceed.

Also, just curious, what IDE's gnucash developers use on MacOS.  It appears that Xcode is not suitable.

Thanks,
Chris
_______________________________________________
gnucash-devel mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Reply | Threaded
Open this post in threaded view
|

Re: [GNC-dev] Compiling Gnucash on MacOS - not for the faint of heart...

John Ralls-2


> On Jul 1, 2018, at 7:39 PM, chris graves <[hidden email]> wrote:
>
> Okay, so I'm an obvious newb here, with the desire to help resolve a gnucash bug (https://bugs.gnucash.org/show_bug.cgi?id=794755 <https://bugs.gnucash.org/show_bug.cgi?id=794755>).
>
> I'm following these build instructions: https://wiki.gnucash.org/wiki/MacOSX/Quartz <https://wiki.gnucash.org/wiki/MacOSX/Quartz>
>
> The first issue was a file not found error when executing jhbuild.
> Resolved this issue by changing the first line from:
> #!/usr/bin/env python2
> to
> #!/usr/bin/env python2.7
>
> even though entering python2 from the terminal worked just fine...
>
> The second issue was jhbuild not being able to find the module: meta-gnucash-stable.
> In perusing https://raw.githubusercontent.com/gnucash/gnucash-on-osx/master/modulesets/gnucash.modules <https://raw.githubusercontent.com/gnucash/gnucash-on-osx/master/modulesets/gnucash.modules>, it appears
> the module name to use is: gnucash.  Setting it to this in ~/.jhbuildrc-custom got me past this issue.
>
> The place I'm stuck at now is:
> *** Checking out iso-codes *** [62/76]
> curl --continue-at - -L http://pkg-isocodes.alioth.debian.org/downloads/iso-codes-3.67.tar.xz -o /Users/chris/gtk/source/pkgs/iso-codes-3.67.tar.xz
>  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
>                                 Dload  Upload   Total   Spent    Left  Speed
>  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (6) Could not resolve host: pkg-isocodes.alioth.debian.org
> *** Error during phase checkout of iso-codes: ########## Error running curl --continue-at - -L http://pkg-isocodes.alioth.debian.org/downloads/iso-codes-3.67.tar.xz -o /Users/chris/gtk/source/pkgs/iso-codes-3.67.tar.xz *** [62/76]
>
> This page: https://wiki.debian.org/Alioth/PackagingProject <https://wiki.debian.org/Alioth/PackagingProject> indicates:
> Alioth is deprecated, and you should not add any new projects
>
> In particular the gforce component is broken in many surprising ways, and there is nobody around to fix it or work around its quirks. Please do not pester the remaining caretaker with requests.
>
> So, I'm not quite sure how to proceed.
>
> Also, just curious, what IDE's gnucash developers use on MacOS.  It appears that Xcode is not suitable.

Last question first, bash and emacs. ISTR Mike Alexander uses vim and emacs.

Cmake *will* generate an Xcode project and I managed to get it to work once, but for the most after ~35 years of emacs I just don’t find that Xcode offers enough to make the time to switch.


As for iso-codes, they’ve had the unfortunate tendency to take down old revs when they put up new ones, which breaks things for people trying to build for the first time (everyone else has already got the download). It looks like their new home is https://salsa.debian.org/iso-codes-team/iso-codes <https://salsa.debian.org/iso-codes-team/iso-codes>, and being gitlab maybe the tarballs will stick around longer. It looks like the latest release is https://salsa.debian.org/iso-codes-team/iso-codes/uploads/ef8de8bc12e0512d26ed73436a477871/iso-codes-3.79.tar.xz <https://salsa.debian.org/iso-codes-team/iso-codes/uploads/ef8de8bc12e0512d26ed73436a477871/iso-codes-3.79.tar.xz>. I’ll fix up the module set sometime this week.

Regards,
John Ralls
_______________________________________________
gnucash-devel mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Reply | Threaded
Open this post in threaded view
|

Re: [GNC-dev] Compiling Gnucash on MacOS - not for the faint of heart...

Rob Gowin
On Sun, Jul 1, 2018, 11:25 PM John Ralls <[hidden email]> wrote:

>
>
> > On Jul 1, 2018, at 7:39 PM, chris graves <[hidden email]> wrote:
> >
> > Also, just curious, what IDE's gnucash developers use on MacOS.  It
> appears that Xcode is not suitable.
>
> Last question first, bash and emacs. ISTR Mike Alexander uses vim and
> emacs.
>
> Cmake *will* generate an Xcode project and I managed to get it to work
> once, but for the most after ~35 years of emacs I just don’t find that
> Xcode offers enough to make the time to switch.
>

The README_CMAKE.txt file (
https://github.com/Gnucash/gnucash/blob/maint/cmake/README_CMAKE.txt)
documents the details about how to use Xcode for GnuCash development (once
all of the dependencies are built.)

Rob
_______________________________________________
gnucash-devel mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Reply | Threaded
Open this post in threaded view
|

Re: [GNC-dev] Compiling Gnucash on MacOS - not for the faint of heart...

chris graves


> On Jul 1, 2018, at 8:39 PM, Rob Gowin <[hidden email]> wrote:
>
>
>
> On Sun, Jul 1, 2018, 11:25 PM John Ralls <[hidden email] <mailto:[hidden email]>> wrote:
>
>
> > On Jul 1, 2018, at 7:39 PM, chris graves <[hidden email] <mailto:[hidden email]>> wrote:
> >
> > Also, just curious, what IDE's gnucash developers use on MacOS.  It appears that Xcode is not suitable.
>
> Last question first, bash and emacs. ISTR Mike Alexander uses vim and emacs.
>
> Cmake *will* generate an Xcode project and I managed to get it to work once, but for the most after ~35 years of emacs I just don’t find that Xcode offers enough to make the time to switch.
>
> The README_CMAKE.txt file (https://github.com/Gnucash/gnucash/blob/maint/cmake/README_CMAKE.txt <https://github.com/Gnucash/gnucash/blob/maint/cmake/README_CMAKE.txt>) documents the details about how to use Xcode for GnuCash development (once all of the dependencies are built.)
>
> Rob
>
Thanks for the comments Rob.  Yeah I figured to just take the path of least resistance.  Long time vi user, so guess we'll stick with that.  Tried emacs once, but couldn't get my fingers to simultaneously press all the needed keys :-(

Made it a bit further in compiling gnucash.  I'm surprised that we are all not working from the same code base as far as the prereq's go.

To get pas the iso-codes issue, I manually downloaded iso-codes-3.67.tar.xz from:
https://ftp.osuosl.org/pub/blfs/conglomeration/iso-codes/ <https://ftp.osuosl.org/pub/blfs/conglomeration/iso-codes/>

Then ran across an error compiling guile, found a bug and manually applied a patch:
http://lists.gnu.org/archive/html/bug-guile/2016-06/msg00252.html <http://lists.gnu.org/archive/html/bug-guile/2016-06/msg00252.html>

Now I'm stuck compiling boost with this error:
*** Configuring boost *** [68/76]
./autogen.sh --prefix /Users/chris/gnucash-stable  
/bin/sh: ./autogen.sh: No such file or directory

Looking at https://raw.githubusercontent.com/gnucash/gnucash-on-osx/master/modulesets/gnucash.modules <https://raw.githubusercontent.com/gnucash/gnucash-on-osx/master/modulesets/gnucash.modules> I see:
<!--./b2 toolset=darwin address-model=32 cxxflags="$CPPFLAGS" cflags="$CPPFLAGS" linkflags="$LDFLAGS" dll-path=$PREFIX/lib -\-prefix=$PREFIX -\-build-dir=$PREFIX/../build/boost_1_56_0 install

After which one must run
for i in `ls $PREFIX/lib/libboost*.dylib`; do install_name_tool -id $i $i; done
for i in `ls $PREFIX/lib/libboost*.dylib`; do for j in `ls $PREFIX/lib/libboost*.dylib`; do install_name_tool -change `basename $i` $i $j; done; done
-->
  <autotools id="boost" supports-non-srcdir-builds="no" skip-install="True">
    <branch module="boost/boost_1_56_0.tar.bz2" repo="sourceforge"
            version="1.56.0"/>
    <after>
      <dep package="icu"/>
      <dep package="icu55"/>
    </after>
  </autotools>

I guessing one needs to run bootstrap.sh which may generate b2, but if so, not sure which args to provide bootstrap.sh



_______________________________________________
gnucash-devel mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Reply | Threaded
Open this post in threaded view
|

Re: [GNC-dev] Compiling Gnucash on MacOS - not for the faint of heart...

Rob Gowin
On Mon, Jul 2, 2018 at 7:22 PM, chris graves <[hidden email]> wrote:

>
>
> On Jul 1, 2018, at 8:39 PM, Rob Gowin <[hidden email]> wrote:
>
>
>
> On Sun, Jul 1, 2018, 11:25 PM John Ralls <[hidden email]> wrote:
>
>>
>>
>> > On Jul 1, 2018, at 7:39 PM, chris graves <[hidden email]> wrote:
>> >
>> > Also, just curious, what IDE's gnucash developers use on MacOS.  It
>> appears that Xcode is not suitable.
>>
>> Last question first, bash and emacs. ISTR Mike Alexander uses vim and
>> emacs.
>>
>> Cmake *will* generate an Xcode project and I managed to get it to work
>> once, but for the most after ~35 years of emacs I just don’t find that
>> Xcode offers enough to make the time to switch.
>>
>
> The README_CMAKE.txt file (https://github.com/Gnucash/
> gnucash/blob/maint/cmake/README_CMAKE.txt) documents the details about
> how to use Xcode for GnuCash development (once all of the dependencies are
> built.)
>
> Rob
>
> Thanks for the comments Rob.  Yeah I figured to just take the path of
> least resistance.  Long time vi user, so guess we'll stick with that.
> Tried emacs once, but couldn't get my fingers to simultaneously press all
> the needed keys :-(
>
>
If you're going to stick with vi, why were you asking about IDEs? :-)

<!--./b2 toolset=darwin address-model=32 cxxflags="$CPPFLAGS"
cflags="$CPPFLAGS" linkflags="$LDFLAGS" dll-path=$PREFIX/lib
-\-prefix=$PREFIX -\-build-dir=$PREFIX/../build/boost_1_56_0 install

>
> After which one must run
> for i in `ls $PREFIX/lib/libboost*.dylib`; do install_name_tool -id $i $i; done
> for i in `ls $PREFIX/lib/libboost*.dylib`; do for j in `ls $PREFIX/lib/libboost*.dylib`; do install_name_tool -change `basename $i` $i $j; done; done
> -->
>   <autotools id="boost" supports-non-srcdir-builds="no" skip-install="True">
>     <branch module="boost/boost_1_56_0.tar.bz2" repo="sourceforge"
>    version="1.56.0"/>
>     <after>
>       <dep package="icu"/>
>       <dep package="icu55"/>
>     </after>
>   </autotools>
>
>
> I guessing one needs to run bootstrap.sh which may generate b2, but if so,
> not sure which args to provide bootstrap.sh
>

No arguments needed,  as per  https://wiki.gnucash.org/wiki/MacOSX/Quartz

-- Rob
_______________________________________________
gnucash-devel mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Reply | Threaded
Open this post in threaded view
|

Re: [GNC-dev] Compiling Gnucash on MacOS - not for the faint of heart...

chris graves


> On Jul 2, 2018, at 5:38 PM, Rob Gowin <[hidden email]> wrote:
>
>
>
> On Mon, Jul 2, 2018 at 7:22 PM, chris graves <[hidden email] <mailto:[hidden email]>> wrote:
>
>
>> On Jul 1, 2018, at 8:39 PM, Rob Gowin <[hidden email] <mailto:[hidden email]>> wrote:
>>
>>
>>
>> On Sun, Jul 1, 2018, 11:25 PM John Ralls <[hidden email] <mailto:[hidden email]>> wrote:
>>
>>
>> > On Jul 1, 2018, at 7:39 PM, chris graves <[hidden email] <mailto:[hidden email]>> wrote:
>> >
>> > Also, just curious, what IDE's gnucash developers use on MacOS.  It appears that Xcode is not suitable.
>>
>> Last question first, bash and emacs. ISTR Mike Alexander uses vim and emacs.
>>
>> Cmake *will* generate an Xcode project and I managed to get it to work once, but for the most after ~35 years of emacs I just don’t find that Xcode offers enough to make the time to switch.
>>
>> The README_CMAKE.txt file (https://github.com/Gnucash/gnucash/blob/maint/cmake/README_CMAKE.txt <https://github.com/Gnucash/gnucash/blob/maint/cmake/README_CMAKE.txt>) documents the details about how to use Xcode for GnuCash development (once all of the dependencies are built.)
>>
>> Rob
>>
> Thanks for the comments Rob.  Yeah I figured to just take the path of least resistance.  Long time vi user, so guess we'll stick with that.  Tried emacs once, but couldn't get my fingers to simultaneously press all the needed keys :-(
>
>
> If you're going to stick with vi, why were you asking about IDEs? :-)

If someone came out and said XYX is the most awesome tool for hacking gnucash, I'd be up for it, but since no one has...
As they say, do as the natives do!

>
> <!--./b2 toolset=darwin address-model=32 cxxflags="$CPPFLAGS" cflags="$CPPFLAGS" linkflags="$LDFLAGS" dll-path=$PREFIX/lib -\-prefix=$PREFIX -\-build-dir=$PREFIX/../build/boost_1_56_0 install
>
> After which one must run
> for i in `ls $PREFIX/lib/libboost*.dylib`; do install_name_tool -id $i $i; done
> for i in `ls $PREFIX/lib/libboost*.dylib`; do for j in `ls $PREFIX/lib/libboost*.dylib`; do install_name_tool -change `basename $i` $i $j; done; done
> -->
>   <autotools id="boost" supports-non-srcdir-builds="no" skip-install="True">
>     <branch module="boost/boost_1_56_0.tar.bz2" repo="sourceforge"
>    version="1.56.0"/>
>     <after>
>       <dep package="icu"/>
>       <dep package="icu55"/>
>     </after>
>   </autotools>
>
> I guessing one needs to run bootstrap.sh which may generate b2, but if so, not sure which args to provide bootstrap.sh
>
> No arguments needed,  as per  https://wiki.gnucash.org/wiki/MacOSX/Quartz <https://wiki.gnucash.org/wiki/MacOSX/Quartz>
I know, it's always RTFM -- thanks.
>
> -- Rob
>

_______________________________________________
gnucash-devel mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Reply | Threaded
Open this post in threaded view
|

Re: [GNC-dev] Compiling Gnucash on MacOS - not for the faint of heart...

Mike Alexander
In reply to this post by John Ralls-2
> On Jul 1, 2018, at 11:23 PM, John Ralls <[hidden email]> wrote:
>
> Last question first, bash and emacs. ISTR Mike Alexander uses vim and emacs.

Sorry for the delay, I’m a bit behind on EMail

My GnuCash environment is probably unique, or at least was until recently.  I’ve been too busy to update things for the current release so for the last few weeks I’ve been using the prebuilt binaries.  I hope to get back to my previous setup soon, however.  This means running the X-Window version on MacOS instead of the native Quartz version.  GTK3 is better than GTK2, but even with it I find the support for Quartz deficient in many ways.  For example there is almost no support for any accessibility features such as Voice Over.  Since I’m partly blind I depend on this and find apps that don’t suport it difficult to use.

I use a combination of MacPorts, BBEdit, and XCode to work on GnuCash.  I use MacPorts to install the dependencies.  This works fine if you’re using the X-Window version since that’s what MacPorts does for a living.  I’m not sure MacPorts has a quartz build for everything GnuCash needs for a dependency but it probably would be possible to add any that are missing.  It’s hard to have MacPorts build both X-Window and Quartz versions of things on the same machine so you really need to pick one or the other.

I use BBEdit to look at and edit the source and to do the builds.  I used to use XEmacs (never vi)  a lot back when I worked on Unix and Windows systems, but since XEmacs is essentially dead now and BBEdit is a very good replacement I use it.  I do the builds in a BBEdit worksheet.  If any of you have been around Macs long enough to remember MPW, a BBEdit worksheet is much like an MPW worksheet.  It’s an editable text window with a shell attached so you can execute shell commands and have the output appear in the window.   This is somewhat of an acquired taste, but I like it for some things.

I also have an XCode project (which is in git) but it is not used for building (the build script is /usr/bin/true).  It is useful for debugging since XCode provides a quite reasonable GUI for lldb.  I’ve got most of the source files in the project (although it’s probably not up to date right now) so XCode can find them.  I point the binary at the copy I build in BBEdit.  Then I can use XCode to debug GnuCash.  This works surprisingly well.

When I just  want to run GnuCash I invoked it from the terminal using a bash script I’ve put in ~/bin/gnucash.

This is admittedly an odd setup, but it works for me.

         Mike
 
_______________________________________________
gnucash-devel mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Reply | Threaded
Open this post in threaded view
|

Re: [GNC-dev] Compiling Gnucash on MacOS - not for the faint of heart...

John Ralls-2


> On Jul 16, 2018, at 10:21 PM, Mike Alexander <[hidden email]> wrote:
>
>> On Jul 1, 2018, at 11:23 PM, John Ralls <[hidden email]> wrote:
>>
>> Last question first, bash and emacs. ISTR Mike Alexander uses vim and emacs.
>
> Sorry for the delay, I’m a bit behind on EMail
>
> My GnuCash environment is probably unique, or at least was until recently.  I’ve been too busy to update things for the current release so for the last few weeks I’ve been using the prebuilt binaries.  I hope to get back to my previous setup soon, however.  This means running the X-Window version on MacOS instead of the native Quartz version.  GTK3 is better than GTK2, but even with it I find the support for Quartz deficient in many ways.  For example there is almost no support for any accessibility features such as Voice Over.  Since I’m partly blind I depend on this and find apps that don’t suport it difficult to use.
>
> I use a combination of MacPorts, BBEdit, and XCode to work on GnuCash.  I use MacPorts to install the dependencies.  This works fine if you’re using the X-Window version since that’s what MacPorts does for a living.  I’m not sure MacPorts has a quartz build for everything GnuCash needs for a dependency but it probably would be possible to add any that are missing.  It’s hard to have MacPorts build both X-Window and Quartz versions of things on the same machine so you really need to pick one or the other.
>
> I use BBEdit to look at and edit the source and to do the builds.  I used to use XEmacs (never vi)  a lot back when I worked on Unix and Windows systems, but since XEmacs is essentially dead now and BBEdit is a very good replacement I use it.  I do the builds in a BBEdit worksheet.  If any of you have been around Macs long enough to remember MPW, a BBEdit worksheet is much like an MPW worksheet.  It’s an editable text window with a shell attached so you can execute shell commands and have the output appear in the window.   This is somewhat of an acquired taste, but I like it for some things.
>
> I also have an XCode project (which is in git) but it is not used for building (the build script is /usr/bin/true).  It is useful for debugging since XCode provides a quite reasonable GUI for lldb.  I’ve got most of the source files in the project (although it’s probably not up to date right now) so XCode can find them.  I point the binary at the copy I build in BBEdit.  Then I can use XCode to debug GnuCash.  This works surprisingly well.
>
> When I just  want to run GnuCash I invoked it from the terminal using a bash script I’ve put in ~/bin/gnucash.
>
> This is admittedly an odd setup, but it works for me.

Mike,

I think that the only GnuCash dependencies that care about the windowing backend (i.e. quartz vs. X11) are cairo, pango, gtk, and webkitgtk, all of which I’m pretty sure MacPorts supports building with quartz. That doesn’t do anything for your a11y needs, of course. That requires someone to integrate atk with the Mac a11y apis.

Since we’ve moved to cmake it’s possible to have cmake create an xcodeproject for you. Have you tried that? It might be easier than hand-maintaining your own.

Regards,
John Ralls

_______________________________________________
gnucash-devel mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Reply | Threaded
Open this post in threaded view
|

Re: [GNC-dev] Compiling Gnucash on MacOS - not for the faint of heart...

Geert Janssens-4
In addition I think the xcode project in git is out of date. When I moved the source directories around I saw a lot of source file references in the xcode project, but I didn't update those. So they still point at the old locations.

Geert

John Ralls <[hidden email]> schreef op 17 juli 2018 17:07:30 CEST:

>
>
>> On Jul 16, 2018, at 10:21 PM, Mike Alexander <[hidden email]> wrote:
>>
>>> On Jul 1, 2018, at 11:23 PM, John Ralls <[hidden email]> wrote:
>>>
>>> Last question first, bash and emacs. ISTR Mike Alexander uses vim
>and emacs.
>>
>> Sorry for the delay, I’m a bit behind on EMail
>>
>> My GnuCash environment is probably unique, or at least was until
>recently.  I’ve been too busy to update things for the current release
>so for the last few weeks I’ve been using the prebuilt binaries.  I
>hope to get back to my previous setup soon, however.  This means
>running the X-Window version on MacOS instead of the native Quartz
>version.  GTK3 is better than GTK2, but even with it I find the support
>for Quartz deficient in many ways.  For example there is almost no
>support for any accessibility features such as Voice Over.  Since I’m
>partly blind I depend on this and find apps that don’t suport it
>difficult to use.
>>
>> I use a combination of MacPorts, BBEdit, and XCode to work on
>GnuCash.  I use MacPorts to install the dependencies.  This works fine
>if you’re using the X-Window version since that’s what MacPorts does
>for a living.  I’m not sure MacPorts has a quartz build for everything
>GnuCash needs for a dependency but it probably would be possible to add
>any that are missing.  It’s hard to have MacPorts build both X-Window
>and Quartz versions of things on the same machine so you really need to
>pick one or the other.
>>
>> I use BBEdit to look at and edit the source and to do the builds.  I
>used to use XEmacs (never vi)  a lot back when I worked on Unix and
>Windows systems, but since XEmacs is essentially dead now and BBEdit is
>a very good replacement I use it.  I do the builds in a BBEdit
>worksheet.  If any of you have been around Macs long enough to remember
>MPW, a BBEdit worksheet is much like an MPW worksheet.  It’s an
>editable text window with a shell attached so you can execute shell
>commands and have the output appear in the window.   This is somewhat
>of an acquired taste, but I like it for some things.
>>
>> I also have an XCode project (which is in git) but it is not used for
>building (the build script is /usr/bin/true).  It is useful for
>debugging since XCode provides a quite reasonable GUI for lldb.  I’ve
>got most of the source files in the project (although it’s probably not
>up to date right now) so XCode can find them.  I point the binary at
>the copy I build in BBEdit.  Then I can use XCode to debug GnuCash.
>This works surprisingly well.
>>
>> When I just  want to run GnuCash I invoked it from the terminal using
>a bash script I’ve put in ~/bin/gnucash.
>>
>> This is admittedly an odd setup, but it works for me.
>
>Mike,
>
>I think that the only GnuCash dependencies that care about the
>windowing backend (i.e. quartz vs. X11) are cairo, pango, gtk, and
>webkitgtk, all of which I’m pretty sure MacPorts supports building with
>quartz. That doesn’t do anything for your a11y needs, of course. That
>requires someone to integrate atk with the Mac a11y apis.
>
>Since we’ve moved to cmake it’s possible to have cmake create an
>xcodeproject for you. Have you tried that? It might be easier than
>hand-maintaining your own.
>
>Regards,
>John Ralls
>
>_______________________________________________
>gnucash-devel mailing list
>[hidden email]
>https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Sent from my smartphone. Please excuse my brevity.
_______________________________________________
gnucash-devel mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel