Re: Windows 64bit build in 32bit command prompt

2015-12-11 Fir de Conversatie Bram Moolenaar
Mike Williams wrote: > Another week, another diff. After some discussion with Ken and Taro I > offer up the following diff to cope with and (attempt to) tidy up cross > compilation across architectures with Visual Studio. [...] > In theory you can target ARM from Intel host but I don't a sys

Re: Windows 64bit build in 32bit command prompt

2015-12-06 Fir de Conversatie Mike Williams
Hi, Another week, another diff. After some discussion with Ken and Taro I offer up the following diff to cope with and (attempt to) tidy up cross compilation across architectures with Visual Studio. diff --git a/src/Make_mvc.mak b/src/Make_mvc.mak --- a/src/Make_mvc.mak +++ b/src/Make_mvc.m

Re: Windows 64bit build in 32bit command prompt

2015-11-29 Fir de Conversatie Mike Williams
On 29/11/2015 17:04, Mike Williams wrote: Hi Ken (and Taro), On 29/11/2015 15:13, Ken Takata wrote: Hi Mike, 2015/11/29 Sun 20:06:42 UTC+9 Mike Williams wrote: Hi, Just done my first build of VIM on an old Windows 7 32bit machine upgraded to Windows 10 using VC. The link stage was failing d

Re: Windows 64bit build in 32bit command prompt

2015-11-29 Fir de Conversatie Mike Williams
On 29/11/2015 16:57, Taro MURAOKA wrote: I wrote: We may be able to use "Platform" environment variable for this purpose. It get one of values: "x64", "X64", "X86" or "ARM" as cross compiling target, in all of VS10, 11, 12, 14 environments. Hi Mike and Ken. I have wrote a patch to use PLATF

Re: Windows 64bit build in 32bit command prompt

2015-11-29 Fir de Conversatie Mike Williams
Hi Ken (and Taro), On 29/11/2015 15:13, Ken Takata wrote: Hi Mike, 2015/11/29 Sun 20:06:42 UTC+9 Mike Williams wrote: Hi, Just done my first build of VIM on an old Windows 7 32bit machine upgraded to Windows 10 using VC. The link stage was failing due to mixed machine targets being used in t

Re: Windows 64bit build in 32bit command prompt

2015-11-29 Fir de Conversatie Taro MURAOKA
I wrote: > We may be able to use "Platform" environment variable for this purpose. > It get one of values: "x64", "X64", "X86" or "ARM" as cross compiling target, > in all of VS10, 11, 12, 14 environments. Hi Mike and Ken. I have wrote a patch to use PLATFORM for this purpose. Please try https:

Re: Windows 64bit build in 32bit command prompt

2015-11-29 Fir de Conversatie Taro MURAOKA
I wrote: > So we should try/find another way. We may be able to use "Platform" environment variable for this purpose. It get one of values: "x64", "X64", "X86" or "ARM" as cross compiling target, in all of VS10, 11, 12, 14 environments. You can see these variables at VC\bin\**\vcvars*.bat in each

Re: Windows 64bit build in 32bit command prompt

2015-11-29 Fir de Conversatie Ken Takata
Hi Mike, 2015/11/29 Sun 20:06:42 UTC+9 Mike Williams wrote: > Hi, > > Just done my first build of VIM on an old Windows 7 32bit machine > upgraded to Windows 10 using VC. The link stage was failing due to > mixed machine targets being used in the make file - 32 and 64 bit! I > tracked this d

Re: Windows 64bit build in 32bit command prompt

2015-11-29 Fir de Conversatie Taro MURAOKA
Mike Williams wrote > Hi, > > Just done my first build of VIM on an old Windows 7 32bit machine > upgraded to Windows 10 using VC. The link stage was failing due to > mixed machine targets being used in the make file - 32 and 64 bit! I > tracked this down to some fun with the PROCESSOR_ARCHIT

Windows 64bit build in 32bit command prompt

2015-11-29 Fir de Conversatie Mike Williams
Hi, Just done my first build of VIM on an old Windows 7 32bit machine upgraded to Windows 10 using VC. The link stage was failing due to mixed machine targets being used in the make file - 32 and 64 bit! I tracked this down to some fun with the PROCESSOR_ARCHITECTURE in a 32bit prompt on a