From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org>, Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>, Hiroshi Saito <hiroshi(at)winpg(dot)jp>, Dave Page <dpage(at)pgadmin(dot)org> |
Subject: | Re: Building psqlODBC installers |
Date: | 2014-06-13 12:43:26 |
Message-ID: | CAB7nPqS+L397Q3hn=K_MVnN2pjwTB1578i7+6P3kvYst8oK=bg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
On Fri, Jun 13, 2014 at 9:33 PM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> I found the procedure for building the installers quite cumbersome. There
> are several ways to do it, using the PowerShell installers, or Make.bat or
> Makex64.bat files, and you have to first build the right drivers versions
> etc.
>
> To simplify things, I invented yet another way to build the installers ;-).
> I pushed a patch that adds new targets to the top-level win64.mak file. The
> most interesting target is "world", which builds both x64 and x86 versions
> of the driver, both ANSI and Unicode versions. And then it builds both x86
> and x64 installers. All in one command:
>
> nmake /f win64.mak world
Awesome +1 for the strategy with nmake. Just had a look at what you
pushed and this is really straight-forward.
While looking at that I am wondering as well about having localized
installers with some embedded mst files created by torch. Perhaps this
is too much thinking?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2014-06-13 15:07:38 | Re: Building psqlODBC installers |
Previous Message | Heikki Linnakangas | 2014-06-13 12:33:51 | Building psqlODBC installers |