From: Junio C Hamano <gitster@pobox.com>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH/RFC] Makefile: Fix compilation of windows resource file
Date: Tue, 21 Jan 2014 13:04:24 -0800 [thread overview]
Message-ID: <xmqqy529t5bb.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <52DD857C.6060005@ramsay1.demon.co.uk> (Ramsay Jones's message of "Mon, 20 Jan 2014 20:22:20 +0000")
Ramsay Jones <ramsay@ramsay1.demon.co.uk> writes:
> If the git version number consists of less than three period
> separated numbers, then the windows resource file compilation
> issues a syntax error:
>
> $ touch git.rc
> $ make V=1 git.res
> GIT_VERSION = 1.9.rc0
> windres -O coff \
> -DMAJOR=1 -DMINOR=9 -DPATCH=rc0 \
> -DGIT_VERSION="\\\"1.9.rc0\\\"" git.rc -o git.res
> C:\msysgit\msysgit\mingw\bin\windres.exe: git.rc:2: syntax error
> make: *** [git.res] Error 1
> $
>
> [Note that -DPATCH=rc0]
Thanks for a report. I've been wondering how many distros and
packagers would have an issue like this when we go to 2-digit
release naming. Of course we knew everybody can grok 3-or-4 ;-)
> In order to fix the syntax error, we replace any rcX with zero and
> include some additional 'zero' padding to the version number list.
>
> Signed-off-by: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
> ---
>
> Hi Junio,
>
> This patch is marked RFC because, as I was just about to send this
> email, I realized it wouldn't always work:
Yeah, and I suspect that with the use of $(wordlist 1,3,...) it is
not even working for maintenance releases. Does it differenciate
between 1.8.5.1 and 1.8.5.2, for example?. Or does "windres" always
assume that a package version is always 3-dewey-decimal (not 2, not
4)?
next prev parent reply other threads:[~2014-01-21 21:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 20:22 [PATCH/RFC] Makefile: Fix compilation of windows resource file Ramsay Jones
2014-01-21 21:04 ` Junio C Hamano [this message]
2014-01-21 21:36 ` Junio C Hamano
2014-01-21 22:51 ` Ramsay Jones
2014-01-21 23:48 ` Junio C Hamano
2014-01-22 6:55 ` Johannes Sixt
2014-01-22 16:12 ` Junio C Hamano
2014-01-22 16:42 ` Johannes Sixt
2014-01-22 17:38 ` Junio C Hamano
2014-01-22 20:14 ` Junio C Hamano
2014-01-23 7:28 ` [PATCH v2] Makefile: Fix compilation of Windows " Johannes Sixt
2014-01-23 12:02 ` Pat Thoyts
2014-01-23 14:16 ` Johannes Sixt
2014-01-23 15:19 ` Pat Thoyts
2014-01-23 18:02 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqy529t5bb.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ramsay@ramsay1.demon.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.