GnuCash
Contact   Instructions
Bug 794617 - Can't compile with -DWITH_GNUCASH=NO due to scm-gnome-utils
Summary: Can't compile with -DWITH_GNUCASH=NO due to scm-gnome-utils
Status: RESOLVED FIXED
Alias: None
Product: GnuCash
Classification: Unclassified
Component: Build system (show other bugs)
Version: 2.7.x
Hardware: Other Linux
: Normal normal
Target Milestone: ---
Assignee: core
QA Contact: core
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-23 07:31 EDT by Potuz
Modified: 2018-06-07 17:20 EDT (History)
6 users (show)

See Also:


Attachments
Patch to compile without gtk+ nor webkit (1.30 KB, patch)
2018-03-23 07:31 EDT, Potuz
jralls: committed+
Details

Description Potuz 2018-03-23 07:31:28 EDT
Created attachment 370048 [details]
Patch to compile without gtk+ nor webkit

I am reporting here a bug requeste for an enhancement that I opened in Gentoo's bugzilla https://bugs.gentoo.org/651200

Trying to compile libgnucash without gnucash in a system without gtk+ (in particular no gnome and no webkit-gtk) I ran into errors like so:

> make[2]: *** No rule to make target
> '/var/tmp/portage/app-office/gnucash-2.7.5-r1/work/
> gnucash-2.7.5/libgnucash/scm/scm-gnome-utils', needed by
> 'lib64/gnucash/scm/ccache/2.2/ gnucash/price-quotes.go'.  Stop.
>

But scm-gnome-utils is defined in gnucash/gnome-utils hence it will not be pulled by the build system with -DWITH_GNUCASH=NO. 

I simply removed the target in libgnucash/scm/CMAkeLists.txt and I managed to get past these errors. After that I managed to compile libgnucash but only after removing the /doc directory because of a missing gnucash.1 file that CMake would complain about. 

Attached are the changes that I needed in order to compile.
Comment 1 John Ralls 2018-06-07 17:19:57 EDT
Comment on attachment 370048 [details]
Patch to compile without gtk+ nor webkit

Comment on attachment 370048 [details]
Patch to compile without gtk+ nor webkit

Committed with a couple of modifications. Thanks!
Comment 2 John Ralls 2018-06-07 17:20:09 EDT
This problem has been fixed in our software repository. The fix will go into the next software release. Once that release is available, you may want to check for a software upgrade provided by your Linux distribution.

Note You need to log in before you can comment on or make changes to this bug.