Geany fails to build even though it is enabled

Bug #769295 reported by Manish Sinha (मनीष सिन्हा)
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zeitgeist Data-Sources
Fix Committed
Medium
Manish Sinha (मनीष सिन्हा)

Bug Description

I just installed geany and when running autogen.sh over the code. I get

configure: ** bzr plugin enabled
configure: ** chrome plugin enabled
configure: ** eog plugin enabled
configure: firefox-libzg plugin disabled
configure: ** geany plugin enabled
configure: ** gedit plugin enabled
configure: ** rhythmbox plugin enabled
configure: totem-libzg plugin disabled
configure: ** vim plugin enabled
configure: ** emacs plugin enabled
configure: ** tomboy plugin enabled
configure: ** telepathy plugin enabled
configure: ** xchat plugin enabled

Which says that geany is enabled

When I run make, I get an error

Making all in geany
make[1]: Entering directory `/home/manish/code/zeitgeist-dataproviders/geany'
  CC zeitgeist_dataprovider_la-zeitgeist_dataprovider.lo
zeitgeist_dataprovider.c:24:25: fatal error: geanyplugin.h: No such file or directory
compilation terminated.
make[1]: *** [zeitgeist_dataprovider_la-zeitgeist_dataprovider.lo] Error 1
make[1]: Leaving directory `/home/manish/code/zeitgeist-dataproviders/geany'
make: *** [all-recursive] Error 1

There is something wrong in the way build-script runs

Related branches

Revision history for this message
Manish Sinha (मनीष सिन्हा) (manishsinha) wrote :

Assigning it to myself.

After done this, check LP Bug #690355 at https://bugs.launchpad.net/zeitgeist-dataproviders/+bug/690355

Changed in zeitgeist-dataproviders:
assignee: nobody → Manish Sinha (मनीष सिन्हा) (manishsinha)
importance: Undecided → Medium
milestone: none → 0.2.0
status: New → Confirmed
Revision history for this message
Manish Sinha (मनीष सिन्हा) (manishsinha) wrote :

I think I found the reason why it fails. It needs gtk development headers for working

$ pkg-config --cflags geany
Package gtk+-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gtk+-2.0.pc'
to the PKG_CONFIG_PATH environment variable
Package 'gtk+-2.0', required by 'Geany', not found

After installing libgtk2.0-dev on Ubuntu, it worked

This means that a check has to be made for gtk-dev

Revision history for this message
Manish Sinha (मनीष सिन्हा) (manishsinha) wrote :

Added a check for GTK in geany section

if test "x$HAVE_GTK" = "xno"; then
    plugin_error_or_ignore "You need to install gtk development headers"
    continue

and now ./autogen.sh gives

checking for ZEITGEIST... yes
checking for GTK... no
no
checking for LIBXUL... no
configure: WARNING: libxul not found (disabling plugin)
configure: WARNING: You need to install gtk development headers (disabling plugin)
configure: WARNING: gtk+-2.0 not found (disabling plugin)
checking for emacs... no
checking for xemacs... no
checking where .elc files should go... ${datadir}/emacs/site-lisp
checking for ZEITGEIST_SHARP... yes
checking for TOMBOY_ADDINS... yes
checking for GTK_SHARP... yes
checking for tomboy... /usr/bin/tomboy
checking which plugins to compile... bzr chrome eog gedit rhythmbox vim emacs tomboy telepathy xchat
configure: Zeitgeist-dataproviders was configured with the following options:
configure: ** bzr plugin enabled
configure: ** chrome plugin enabled
configure: ** eog plugin enabled
configure: firefox-libzg plugin disabled
configure: geany plugin disabled
configure: ** gedit plugin enabled
configure: ** rhythmbox plugin enabled
configure: totem-libzg plugin disabled
configure: ** vim plugin enabled
configure: ** emacs plugin enabled
configure: ** tomboy plugin enabled
configure: ** telepathy plugin enabled
configure: ** xchat plugin enabled

geany gets disabled

Revision history for this message
Manish Sinha (मनीष सिन्हा) (manishsinha) wrote :

Done. This issue is faced only when you are building from source. Most of the build systems solve this by explicitly specifying the build-deps

Changed in zeitgeist-dataproviders:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.