On 10/24/2016 2:12 PM, jungle Boogie wrote:
On 24 October 2016 at 13:08, Warren Young wrote:
‘cl’ and related tools are not in the PATH after installing Visual
Studio. If you look in the Start Menu folder for Visual Studio, you
will find something like “VS2015 x86 Native Tools Command Prompt.”
On Oct 24, 2016, at 3:12 PM, jungle Boogie wrote:
>
> On 24 October 2016 at 13:08, Warren Young wrote:
>> VS2015 x86 Native Tools Command Prompt.
>
> SUCCESS! I had put this big ugly thing in my path thinking it had all
> the toolchain necessary but it looks like it still failed.
That shortcut
On 24 October 2016 at 13:08, Warren Young wrote:
> On Oct 24, 2016, at 2:03 PM, jungle Boogie wrote:
>>
>> On 24 October 2016 at 11:44, jungle Boogie wrote:
>>> Building zlib from "..\compat\zlib"...
>>>
>>>cl -c -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE
>>> -nologo -MD -W3
On Oct 24, 2016, at 2:08 PM, Warren Young wrote:
>
> On Oct 24, 2016, at 2:03 PM, jungle Boogie wrote:
>>
>> On 24 October 2016 at 11:44, jungle Boogie wrote:
>>> Building zlib from "..\compat\zlib"...
>>>
>>> cl -c -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE
>>> -nologo -MD
On Oct 24, 2016, at 2:03 PM, jungle Boogie wrote:
>
> On 24 October 2016 at 11:44, jungle Boogie wrote:
>> Building zlib from "..\compat\zlib"...
>>
>>cl -c -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE
>> -nologo -MD -W3 -O2 -Oy- -Zi -Fd"zlib" .\adler32.c
>> 'cl' is not recog
On 24 October 2016 at 11:44, jungle Boogie wrote:
> On 24 October 2016 at 11:17, Richard Hipp wrote:
>> If you want to build Fossil from sources on windows using MSVC, then
>> use the trunk.
>
> Downloaded 1.36 cloned trunk and attempting the build again:
> fossil-trunk\fossil\win>"C:\Program Fil
On 24 October 2016 at 11:17, Richard Hipp wrote:
> If you want to build Fossil from sources on windows using MSVC, then
> use the trunk.
Downloaded 1.36 cloned trunk and attempting the build again:
fossil-trunk\fossil\win>"C:\Program Files (x86)\Microsoft Visual
Studio 10.0\VC\bin\nmake.exe" /f M
On 10/24/2016 02:17 PM, Richard Hipp wrote:
> Yes, except that Andy broken the build while we were in the quiet
> period leading up to the 1.36 release
Nice job, Andy
http://big.assets.huffingtonpost.com/tumblr_nqxexloObr1rubttio1_400.gif
___
fossil-u
On 10/24/16, Andy Bradford wrote:
> Thus said Richard Hipp on Mon, 24 Oct 2016 14:17:37 -0400:
>
>> Yes, except that Andy broken the build while we were in the quiet
>> period leading up to the 1.36 release and I failed to notice the
>> problem.
>
> My apologies. Such an obvious C89 pro
Thus said Richard Hipp on Mon, 24 Oct 2016 14:17:37 -0400:
> Yes, except that Andy broken the build while we were in the quiet
> period leading up to the 1.36 release and I failed to notice the
> problem.
My apologies. Such an obvious C89 problem too, I'm not sure why I didn't
even not
On 10/24/16, jungle Boogie wrote:
>
> So did you patch prior to making the Windows build and that's how you
> have Windows binary?
The binary for 1.36 is built using mingw+msys.
--
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-u
On 24 October 2016 at 11:17, Richard Hipp wrote:
> On 10/24/16, jungle Boogie wrote:
>> Hi All,
>>
>> So I installed Microsoft Visual Studio and within that toolkit, I need
>> to use VC to build the fossil.exe file, right?
>
> Yes, except that Andy broken the build while we were in the quiet
> pe
On 10/24/16, jungle Boogie wrote:
> Hi All,
>
> So I installed Microsoft Visual Studio and within that toolkit, I need
> to use VC to build the fossil.exe file, right?
Yes, except that Andy broken the build while we were in the quiet
period leading up to the 1.36 release and I failed to notice th
Hi All,
So I installed Microsoft Visual Studio and within that toolkit, I need
to use VC to build the fossil.exe file, right?
https://www.fossil-scm.org/index.html/doc/trunk/BUILD.txt
Do that against the 1.36 source, I get this:
cl /c /nologo /MT /O2 /I. /I..\src /I..\win\include
/I..\c
14 matches
Mail list logo