Re: [GNC-dev] Compiling Gnucash on MacOS - not for the faint of heart...
> On Jul 1, 2018, at 11:23 PM, John Ralls 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 gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] gnucash 3.2 build failure
Graham Menhennitt, Your GUESS concerning the output and build directories being the same and causing the error was exactly correct. I assume you are very smart; but, there is nothing like experience in addition. Thank you very much for taking the time to help me. David > > > On Jul 15, 2018, at 3:05 PM, Carol & David Weiner > .net> wrote: > > > > Trying to build gnucash 3.2 from a tar file on a Debian Stretch > > system. CMAKE and MAKE run to completion just fine. If I look at > > /build_directory/lib/gnucash/ I see a number of libraries including > > libgncmod-app-utils.so. If I run 'sudo make install' it fails > > because > > libgncmod-app-utils.so is not found. Sure enough this library is > > no > > longer in /build_directory/lib/gnucash/ after the make install > > command > > completes. The error occurs at line 42 of the cmake_install.cmake > > file > > in libgnucash/app-utils/. Any suggestions? > > That?s seriously strange. make install shouldn?t be removing > anything. Try starting over and then run > make install VERBOSE=1 > and examine the output to see what?s becoming of it. > > Regards, > John Ralls > > > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] gnucash 3.2 build failure
Please remember to copy the list on all replies. It looks like Graham Menhennitt might be on the right track. What did you set CMAKE_INSTALL_PREFIX to in your cmake invocation? Regards, John Ralls > On Jul 16, 2018, at 12:13 PM, Carol & David Weiner > wrote: > > John, > > Thanks for your response. I agree with you that this is 'seriously > strange'; but, that is what I usually think when I don't yet understand > why something is happening. > > As you suggested, I deleted everything, including the expanded tar > file, and reran the build up to 'sudo make install VERBOSE=1'. I got > about 2k lines of output that looked very normal, except for the last > few lines which I have included below: > > -- Installing: > /home/david/gnc_build/share/locale/mai/LC_MESSAGES/gnucash.mo > -- Installing: > /home/david/gnc_build/share/locale/mni/LC_MESSAGES/gnucash.mo > -- Up-to-date: /home/david/gnc_build/share/locale/mni@bengali/LC_MESSAG > ES/gnucash.mo > -- Installing: > /home/david/gnc_build/share/gnucash/scm/gnucash/unittest-support.scm > CMake Error at libgnucash/app-utils/cmake_install.cmake:42 (file): > file INSTALL cannot find > "/home/david/gnc_build/lib/gnucash/libgncmod-app-utils.so". > Call Stack (most recent call first): > libgnucash/cmake_install.cmake:37 (include) > cmake_install.cmake:83 (include) > > > Makefile:61: recipe for target 'install' failed > make: *** [install] Error 1 > > This is the only place where the library libgncmod-app-utils.so is > mentioned in the output. I still have no idea where the problem is! > But, I am willing to try almost anything to track the problem down. > > David > > > On Sun, 2018-07-15 at 19:36 -0700, John Ralls wrote: >>> On Jul 15, 2018, at 3:05 PM, Carol & David Weiner >> .net> wrote: >>> >>> Trying to build gnucash 3.2 from a tar file on a Debian Stretch >>> system. CMAKE and MAKE run to completion just fine. If I look at >>> /build_directory/lib/gnucash/ I see a number of libraries including >>> libgncmod-app-utils.so. If I run 'sudo make install' it fails >>> because >>> libgncmod-app-utils.so is not found. Sure enough this library is >>> no >>> longer in /build_directory/lib/gnucash/ after the make install >>> command >>> completes. The error occurs at line 42 of the cmake_install.cmake >>> file >>> in libgnucash/app-utils/. Any suggestions? >> >> That’s seriously strange. make install shouldn’t be removing >> anything. Try starting over and then run >> make install VERBOSE=1 >> and examine the output to see what’s becoming of it. >> >> Regards, >> John Ralls >> >> ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Problems with python 3 and the gnucash python bindings.
> On Jul 16, 2018, at 10:09 AM, Derek Atkins wrote: > > John Ralls writes: > >>> When it moves to C++ you can just use std::string. :) >> >> An enum would be safer, faster, smaller, more intuitive, and wouldn’t >> break swig. > > Funny... 15+ years ago it WAS an Enum, but changed to a string because > we wanted to enable searching on plug-in modules. OK, and enums are immune to run-time changes implied by a plugin module, but there are better ways than strings to tag types. Glib provides Gquarks for just this purpose and even provides a function to get one on a GObject's type name: g_type_qname(G_OBJECT_TYPE()). C++ obviously has a different type model and we'll need to rework/replace QofID, QofContainer, and QofQuery to match it so changing them now to use quarks instead of strings would be wasted effort. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Problems with python 3 and the gnucash python bindings.
John Ralls writes: >> When it moves to C++ you can just use std::string. :) > > An enum would be safer, faster, smaller, more intuitive, and wouldn’t > break swig. Funny... 15+ years ago it WAS an Enum, but changed to a string because we wanted to enable searching on plug-in modules. > Regards, > John Ralls -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH warl...@mit.eduPGP key available ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] GnuCash 3.x Release Tour
Hi Adrien, Sure, after you commited a new tour. ;-) Regards Frank Am 11.07.2018 um 04:09 schrieb Adrien Monteleone: > I see right near the top there is still the “GnuCash 2.6 release tour”. > Perhaps an update there to 3.0 would be in order. > > Regards, > Adrien > >> On Jul 10, 2018, at 8:45 PM, Wm wrote: >> >> On 29/06/2018 08:43, Geert Janssens wrote: >>> Op donderdag 28 juni 2018 22:11:49 CEST schreef Dennis West: I'm sure you like to get feedback from someone with absolutely no problems at all. I was using 2.6.21 on my primary computer and testing 3.1/3.2 on my standby testbed (both on Win 10.1803). I finally decided to take the plunge and upgraded my primary computer form 2.6.21 to 3.2. The experience was flawless and now my testbed pc is eagerly awaiting vs 4.0. >> >> But approximately a decade away for v4 so maybe get some new kit before 2030 >> for your testbed :) >> >>> That's nice to hear :) >> >> Aside: is there a reason why version changes aren't on (or easily found >> from) the front page of gnucash.org? they used to be there. >> >> -- >> Wm >> >> ___ >> gnucash-devel mailing list >> gnucash-devel@gnucash.org >> https://lists.gnucash.org/mailman/listinfo/gnucash-devel >> > > > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > pEpkey.asc Description: application/pgp-keys ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] GnuCash 3.2 Released
I see right near the top there is still the “GnuCash 2.6 release tour”. Perhaps an update there to 3.0 would be in order. Regards, Adrien > On Jul 10, 2018, at 8:45 PM, Wm wrote: > > On 29/06/2018 08:43, Geert Janssens wrote: >> Op donderdag 28 juni 2018 22:11:49 CEST schreef Dennis West: >>> I'm sure you like to get feedback from someone with absolutely no >>> problems at all. >>> >>> I was using 2.6.21 on my primary computer and testing 3.1/3.2 on my >>> standby testbed (both on Win 10.1803). I finally decided to take the >>> plunge and upgraded my primary computer form 2.6.21 to 3.2. The >>> experience was flawless and now my testbed pc is eagerly awaiting vs 4.0. > > But approximately a decade away for v4 so maybe get some new kit before 2030 > for your testbed :) > >> That's nice to hear :) > > Aside: is there a reason why version changes aren't on (or easily found from) > the front page of gnucash.org? they used to be there. > > -- > Wm > > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
