On 2019-06-01 16:36:38 +1000, Cameron Simpson wrote:
> On 31May2019 17:36, Kevin J. McCarthy wrote:
> > On Fri, May 31, 2019 at 11:19:27PM +0200, Vincent Lefevre wrote:
> > > On 2019-05-31 09:37:02 -0700, Kevin J. McCarthy wrote:
> > > > Of course, if anyone has an idea how to do this in a way tha
On Sat, Jun 01, 2019 at 02:16:24PM +0200, Vincent Lefevre wrote:
On 31May2019 17:36, Kevin J. McCarthy wrote:
On Fri, May 31, 2019 at 11:19:27PM +0200, Vincent Lefevre wrote:
How about using AM_CONDITIONAL in configure.ac, setting a variable
GNU_MAKE when GNU Make is used (based on "make --ver
On Sat, Jun 01, 2019 at 04:36:38PM +1000, Cameron Simpson wrote:
If I were writing the conjectured goal above I'd probably do this:
mutt_version='#define MUTT_VERSION "'`sh "$(srcdir)/version.sh`'"'
version_h=`[ -s version.h ] && cat version.h`
[ "$$mutt_version" = "$$version_h" ] || echo "$$mut
On 01Jun2019 14:16, vincent lefevre wrote:
On 2019-06-01 16:36:38 +1000, Cameron Simpson wrote:
I'm an opinionated make user. Can you explain why you want the
"FORCE"
target at all?
The goal is to make sure that version.h is up-to-date after an update
such as "git pull".
Ah, where the file
On 01Jun2019 07:18, Kevin J. McCarthy wrote:
On Sat, Jun 01, 2019 at 04:36:38PM +1000, Cameron Simpson wrote:
If I were writing the conjectured goal above I'd probably do this:
mutt_version='#define MUTT_VERSION "'`sh "$(srcdir)/version.sh`'"'
version_h=`[ -s version.h ] && cat version.h`
[ "$
On 2019-06-02 08:31:01 +1000, Cameron Simpson wrote:
> On 01Jun2019 14:16, vincent lefevre wrote:
> > On 2019-06-01 16:36:38 +1000, Cameron Simpson wrote:
> > > I'm an opinionated make user. Can you explain why you want the
> > > "FORCE"
> > > target at all?
> >
> > The goal is to make sure that
