| From: | Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: Mentioning CPU for Windows build in docs |
| Date: | 2014-06-02 16:00:50 |
| Message-ID: | 538C9FB2.8050103@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
(2014/06/02 20:54), Heikki Linnakangas wrote:
> On 06/02/2014 02:35 PM, Inoue, Hiroshi wrote:
>> Official Windows build no longer uses nmake.
>> The binaries are built using MSBuild.
>> Please look at readme_winbuild.txt or winbuild/readme.txt.
>
> Huh? Really?
>
> Why did we switch? What's the advantage of MSBuild over nmake?
For example, MSBuild can switch the environment (Platform,
VisualStudioVersion or platformToolset) easily. In fact
BuildAll.ps1(bat) builds both 32bit and 64bit drivers.
Or MSBuild can detect the changes of related files (e.g.
header files).
IMHO nmake is needed only for vc9 or before.
regards,
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-06-02 18:26:14 | Re: Mentioning CPU for Windows build in docs |
| Previous Message | Hiroshi Inoue | 2014-06-02 15:16:51 | Re: Prepared statement error with UseServerSidePrepare=1 |