Re: [be] Re: Compiling Bibledit on MacOS X - again

[Teus Benschop]

A new release is not planned to be coming so soon. The current code is
available from the git repository. See
http://www.nongnu.org/bibledit/development.html for details on how to
obtain this code. This code no longer requires chmsee. 

If it is not possible for macports to obtain code from the git
repository, I can then supply a tarball and upload it somewhere. Let me
know what you need in this regard.

There's no special patch for the Makefile.am or the configure.ac unless
one was going to dig around in the git repository. But this could be
tricky since I didn't pay special attention to making a clean commit.

Teus.

On Thu, 2009-11-12 at 09:39 -0800, Mark Duling wrote:
> I thought a new release with the chmsee fix was imminent and I was
> waiting for that to update the macport, but maybe Tues was referring
> to a nightly build.  Is there a Makefile or configure patch that can
> be applied to 3.9 to fix the chmsee issue?  I’d be happy to update the
> bibledit macport.  If some dependencies are from macports it is a
> shame not to just use it for all of it.  Scripting is better than
> documentation any day, and is a form of documentation anyway.  I
> learned several years ago that taking a week to learn macports would
> repay dividends in time saved for me and others.  But I don’t use
> bibledit and I lose track of releases sometimes.
> 
> Mark
> 
> 
>         Hi Teus and all,
>         
>         sorry to reopen the issue of compiling Bibledit on MacOS X.
>         First of
>         all, thanks so much for your work on removing the chmsee
>         issue. But
>         now I have a problem with the libwebkit dependence. I have
>         installed
>         the WebKit for Mac (the latest nightly build), but the
>         configure
>         script still complains about not finding WebKit. Do I need to
>         set some
>         variables, or am I missing something?
>         
>         (To those who have requested updated instructions: I will do
>         so once I
>         have been successful.)
>         
>         --Christoph