This is indeed a build-system bug and not a source code problem. If our
autotools files were fixed, the source should build fine without
clucene. I hadn't been aware that we still had a problem. I think
glasseyes commited a patch recently. Looking.... The last log entry in
svn on configure.ac is as follows:
------------------------------------------------------------------------
r2008 | dglassey | 2006-11-25 14:17:33 -0700 (Sat, 25 Nov 2006) | 3 lines
add --enable-warnings to build with warnings as errors
fixes for clucene detection
------------------------------------------------------------------------
Maybe he can comment on the issue, or someone more knowledgeable than me
in autoconf can look at the recent deltas to configure.ac
-Troy.
Karl Kleinpaste wrote:
> DM Smith <[EMAIL PROTECTED]> writes:
>> In usrinst.sh it is an option.
>
> But it seems not to work: Even when commented out, if CLucene is not
> installed, dependencies fail. It has to be there, even if it's not
> intended to be used.
>
> And when it is wanted, it seems to be necessary to use e.g.
> --with-clucene=/usr, to explicitly specify CLucene's install prefix.
> Credit to Terry for pointing this out to Moses and myself in
> #gnomesword just a couple days ago.
>
> Greg Hellings wrote:
>>> Also, if I'm not mistaken, there is no build
>>> of CLucene (at least that I've been able to locate) that operates for
>>> the cygwin building environment either.
>
> Not quite true. In order to build GnomeSword for Cygwin, installing
> CLucene is necessary just to get past the configure dependency, even
> though until this week I didn't understand why CLucene's availability
> was not having any useful effect. The problems are that [a] Cygwin GTK
> has some old crud in a couple #includes and [b] CLucene itself is too
> dumb to install its own fundamental .h file in /usr/include/CLucene.
> (It mis-installs clucene-config.h in /usr/lib/CLucene.)
>
> Part of my Cygwin GnomeSword build script is:
>
> # fix gtk #includes
> cd /usr/include/gtk-2.0/gtk
> mv gtkclist.h gtkclist.h.ORIG
> sed -e 's/GMemChunk \*/gpointer /' < gtkclist.h.ORIG > gtkclist.h
> mv gtkstatusbar.h gtkstatusbar.h.ORIG
> sed -e 's/GMemChunk \*/gpointer /' < gtkstatusbar.h.ORIG > gtkstatusbar.h
> # ... unpack/build/install CLucene, then ...
> cp -pv src/CLucene/clucene-config.h /usr/include/CLucene
>
> This solves the build problems for CLucene under Cygwin. And then a
> GnomeSword search on e.g.
> +god +father +"jesus christ"
> is amazingly fast.
>
> Per Terry's instruction earlier this week, I also do this to sword's
> configure.ac, to remove the conditionals on CLucene detection,
> although it's not clear it's needed in either Linux or Cygwin, now
> that I know to use --with-clucene=/usr:
>
> ----------------------------------------------------------------
> --- configure.ac.~1~ 2007-04-03 11:53:57.000000000 -0400
> +++ configure.ac 2007-04-24 11:15:21.000000000 -0400
> @@ -211,4 +211,4 @@
>
> -use_clucene=
> -if test -z "$with_clucene"; then
> +#use_clucene=
> +#if test -z "$with_clucene"; then
> echo "lucene found - lucene searching options available"
> @@ -218,5 +218,5 @@
> use_clucene="yes"
> -else
> - echo "lucene searching options not available"
> -fi
> +#else
> +# echo "lucene searching options not available"
> +#fi
>
> ----------------------------------------------------------------
>
> I need to re-tweak my Cygwin build script to account for automatically
> handling CLucene detection via --with-clucene=/usr but I haven't
> actually done so yet; probably this weekend, after more testing.
>
> --karl
>
> _______________________________________________
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
