[Gpg4win-devel] Updated Compiling Guide

[Phillip]

I never was able to figure this out. All I wanted to do was up the
limitation on key size. Is there a reason why it's limited to 4096? If not
would you mind increasing the limit for the next release?

-----Original Message-----
From: Werner Koch [mailto:wk at gnupg.org] 
Sent: Wednesday, June 26, 2013 4:38 AM
To: Phillip
Cc: gpg4win-devel at wald.intevation.org
Subject: Re: [Gpg4win-devel] Updated Compiling Guide

On Wed, 26 Jun 2013 05:13, phillip654 at hotmail.com said:
> Werner,
>
> I don't remember the error I was getting before as I have reinstalled 
> multiple times, but the error im currently getting is "Error: invalid 
> VIProductVersion format, should be X.X.X.X". I have tried manually 
> putting in the version in the installer.nsi file, but that didn't help.

Check out include/config.h.  You whould fine a line like

  !define _BUILD_FILEVERSION 2.1.1.43292

This is created by configure from include/config.h.in.  The last part of
that version is a decimalized git commit id.  That one is created by running
./autogen.sh.  To be sure that no automake caching gets into the way, you
may want to run

  ./autogen.sh --force

once.  This is a bit of M$ magic:

  m4_define([git_revision], m4_esyscmd([git branch -v 2>/dev/null \
            | awk '/^\* / {printf "%s",$3}']))
  m4_define([git_revision_dec],
            m4_esyscmd_s([echo $((0x$(echo ]git_revision[|head -c 4)))]))

Right, using git branch might fail - I need to update it to use git
rev-parse as it is done with all other projects.


Salam-Shalom,

   Werner

--
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.