Re: GIT version - no display of html messages



On 2018.07.04 16:48, Peter Bloomfield wrote:
On 07/04/2018 04:30:26 PM Wed, Jack via balsa-list wrote:
On 07/04/2018 04:18 PM, Peter Bloomfield wrote:
On 07/04/2018 03:04:38 PM Wed, Jack via balsa-list wrote:
…
Also - I am currently stuck on trying to compile from git-head because balsa.desktop.in.in seems to be missing, at least for me.  Is this known, a temporary issue, or something local to my setup?

You might need to rerun autogen.sh, or perhaps just automake. In migrating from libnotify to GNotification, balsa.desktop was renamed to org.desktop.Balsa.desktop, and the .in files and Makefile.am were changed accordingly. I'm guessing you have a stale Makefile.

Let us know if you can fix it.

Thanks!
autogen.sh did the trick.  No stale Makefile, this was building from scratch.  I think the main file fixed by this was Makefile.in.

What I had been worried about was running autogen and then having a bunch of files different from git.  However, I now see that all files modified by autogen are actually in .gitignore so no problems with this.

I guess an in-tree build is taken care of by .gitignore. An out-of-tree build is more robust:

mkdir path/to/builddir
cd path/to/builddir
path/to/srcdir/autogen.sh --what-ever
make

will create 'configure' in the git tree, but all the other generated files are in builddir. Your git tree will be (almost) clean, even if .gitignore isn't kept up to date (really? that happens?☺)

It's all magic..... :-)

I'm using a slightly different out of tree build, although I suppose your example does include mine. (Most folks seem to create the build dir below the top of the source dir.)
cd ...../workingarea
git clone ........ balsa-git
mkdir build
In this case, though, I thought I even ran autogen.sh while IN the source dir, not in the builddir. I had forgotten autogen does a configure, but now I don't see (for example) Makefile there, so my memory is worse than I thought. It's just too hot and humid here to be doing much more of this today.

Anyway - all (mostly?) working now.

One more possible heads up on a potential issue. I sometimes (depending on specific configure parameters) get an error about not finding enchant <=1.6.0. I think that might mainly be with the internal spell checker. Using either external spell checker, balsa only checks for it, and lets (I assume) it deal with required version of enchant. In my case, gspell is happily using enchant 2.1.1, but I think that migh have taken some patching - I know enchant 2.x is still marked as very unstable on gentoo, so anywhere it does work is still a special case for now.

Jack


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]