Re: [fossil-users] windows compiling with MS VC

[Ross Berteig]

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.” 
Running nmake under that should succeed, at least with this C99 fix 
in place. 


SUCCESS!



I think MS gave up on putting the VS tool chain in the PATH by default 
when they started delivering both 32-bit and 64-bit toolchains. If you 
look in vcvarsall.bat, you'll see that the full environment it needs is 
more complicated than just the PATH, and looking in the nest of batch 
files now, it is more complicated than I recalled.


As an embedded developer with many different compiler toolchains 
crossing my desk, I am very happy to see that from them. Back in the 
day, they used to insist on setting PATH, and then adding INCLUDE and 
LIB which often messed with other compilers, even other compilers 
targeting Windows let alone cross compilers.


--
Ross Berteig   r...@cheshireeng.com
Cheshire Engineering Corp.   http://www.CheshireEng.com/
+1 626 303 1602

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] windows compiling with MS VC

[Warren Young]

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 launches a batch file which calls other batch files which in turn 
call other batch files.  In total, each invocation probably runs through 
several hundred lines of batch file spaghetti code.

If you were to diff your environment variables after this batch file runs 
relative to the stock version, you’d probably be stunned by all the changes it 
makes.

Up to about a decade ago, upon each new release of Visual Studio I would 
convert the predecessors to this script from BAT to Bourne shell format so I 
could use the Visual C++ tools under Cygwin, too, but I gave up when it grew to 
more than a few dozen lines of batch code.

I recommend that you also not try to do by hand what this tangle of batch files 
does for you.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] windows compiling with MS VC

[jungle Boogie]

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 -O2 -Oy- -Zi -Fd"zlib"  .\adler32.c
>>> 'cl' is not recognized as an internal or external command,
>>
>> Is what's above something I can work around to build successfully?
>
> ‘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.”  Running nmake under 
> that should succeed, at least with this C99 fix in place.


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.

C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin

Launching Visual Studio Command Prompt (2010) directly did get the
build working.


Thanks for the pointers, Warren!

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] windows compiling with MS VC

[Warren Young]

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 -W3 -O2 -Oy- -Zi -Fd"zlib"  .\adler32.c
>>> 'cl' is not recognized as an internal or external command,
>> 
>> Is what's above something I can work around to build successfully?
> 
> ‘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.”  Running nmake under 
> that should succeed, at least with this C99 fix in place.

Verified:

C:\...\fossil\win>nmake /f Makefile.msc
...noisenoisenoise...

C:\...\fossil\win>dir fossil.exe
...
  10/24/2016  14:14 2,465,792 fossil.exe

C:\...\fossil\win>fossil ver
This is fossil version 1.37 [7f2af9d8eb] 2016-10-24 20:00:09 UTC

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] windows compiling with MS VC

[Warren Young]

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 recognized as an internal or external command,
> 
> Is what's above something I can work around to build successfully?

‘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.”  Running nmake under that should 
succeed, at least with this C99 fix in place.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] windows compiling with MS VC

[jungle Boogie]

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 Files (x86)\Microsoft Visual
> Studio 10.0\VC\bin\nmake.exe" /f Makefile.msc
>
> 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 recognized as an internal or external command,
> operable program or batch file.
> NMAKE : fatal error U1077: 'cl' : return code '0x1'
> Stop.
> NMAKE : fatal error U1077: 'pushd' : return code '0x2'
> Stop.
>
>

Is what's above something I can work around to build successfully?

>
>
> --
> ---
> inum: 883510009027723
> sip: jungleboo...@sip2sip.info



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] windows compiling with MS VC

[jungle Boogie]

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 Makefile.msc

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 recognized as an internal or external command,
operable program or batch file.
NMAKE : fatal error U1077: 'cl' : return code '0x1'
Stop.
NMAKE : fatal error U1077: 'pushd' : return code '0x2'
Stop.




-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] windows compiling with MS VC

[Adam Jensen]

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-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] windows compiling with MS VC

[Richard Hipp]

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 problem too, I'm not sure why I didn't
> even notice. Sorry.

I should have testing on MSVC before tagging the release

-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] windows compiling with MS VC

[Andy Bradford]

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 notice. Sorry.

Andy
-- 
TAI64 timestamp: 4000580e5391


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] windows compiling with MS VC

[Richard Hipp]

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-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] windows compiling with MS VC

[jungle Boogie]

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
> period leading up to the 1.36 release and I failed to notice the
> problem.  Hence, the 1.36 tarball will not build (without patching)
> using MSVC. Bummer.  Maybe 1.37 will go better.
>

So did you patch prior to making the Windows build and that's how you
have Windows binary?

> If you want to build Fossil from sources on windows using MSVC, then
> use the trunk.

Got it! I'll download Windows binary and attempt building from trunk.

>
> --
> D. Richard Hipp
> d...@sqlite.org


-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] windows compiling with MS VC

[Richard Hipp]

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 the
problem.  Hence, the 1.36 tarball will not build (without patching)
using MSVC. Bummer.  Maybe 1.37 will go better.

If you want to build Fossil from sources on windows using MSVC, then
use the trunk.

-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] windows compiling with MS VC

[jungle Boogie]

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..\compat\zlib /Fo.\stash.obj -c stash_.c
stash_.c
cl /c /nologo /MT /O2  /I. /I..\src /I..\win\include
/I..\compat\zlib /Fo.\stat.obj -c stat_.c
stat_.c
cl /c /nologo /MT /O2  /I. /I..\src /I..\win\include
/I..\compat\zlib /Fo.\statrep.obj -c statrep_.c
statrep_.c
cl /c /nologo /MT /O2  /I. /I..\src /I..\win\include
/I..\compat\zlib /Fo.\style.obj -c style_.c
style_.c
cl /c /nologo /MT /O2  /I. /I..\src /I..\win\include
/I..\compat\zlib /Fo.\sync.obj -c sync_.c
sync_.c
cl /c /nologo /MT /O2  /I. /I..\src /I..\win\include
/I..\compat\zlib /Fo.\tag.obj -c tag_.c
tag_.c
cl /c /nologo /MT /O2  /I. /I..\src /I..\win\include
/I..\compat\zlib /Fo.\tar.obj -c tar_.c
tar_.c
cl /c /nologo /MT /O2  /I. /I..\src /I..\win\include
/I..\compat\zlib /Fo.\th.obj -c ..\src\th.c
th.c
cl /c /nologo /MT /O2  /I. /I..\src /I..\win\include
/I..\compat\zlib /Fo.\th_lang.obj -c ..\src\th_lang.c
th_lang.c
cl /c /nologo /MT /O2  /I. /I..\src /I..\win\include
/I..\compat\zlib /Fo.\th_main.obj -c th_main_.c
th_main_.c
cl /c /nologo /MT /O2  /I. /I..\src /I..\win\include
/I..\compat\zlib /Fo.\th_tcl.obj -c ..\src\th_tcl.c
th_tcl.c
cl /c /nologo /MT /O2  /I. /I..\src /I..\win\include
/I..\compat\zlib /Fo.\timeline.obj -c timeline_.c
timeline_.c
cl /c /nologo /MT /O2  /I. /I..\src /I..\win\include
/I..\compat\zlib /Fo.\tkt.obj -c tkt_.c
tkt_.c
..\src\tkt.c(552) : error C2143: syntax error : missing ';' before 'type'
..\src\tkt.c(553) : error C2065: 'rid' : undeclared identifier
..\src\tkt.c(560) : error C2065: 'rid' : undeclared identifier
..\src\tkt.c(563) : error C2065: 'rid' : undeclared identifier
..\src\tkt.c(564) : error C2065: 'rid' : undeclared identifier
..\src\tkt.c(566) : error C2065: 'rid' : undeclared identifier
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
Studio 10.0\VC\BIN\cl.EXE"' : return code '0x2'
Stop.

yes, 1.36 is now available to download:
https://www.fossil-scm.org/index.html/uv/download.html


Taking the 1.35 source and doing the same steps, I get a fossil.exe
binary in my win C:\Users\me\Downloads\fossil-1.35\win directory.

Do I need to modify the makefiles to generate the binary using the
same steps that worked on 1.35?

Thanks!



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users