Re: [TCLCORE] Build on Windows 10 w/ VS2017 Community Edition and TIP organization …

[Alexander S. <a.s...@gm...>]

Hi Martin,

a simple way to build Tcl/Tk is to use Paul Obermeier’s BAWT.
See http://wiki.tcl.tk/48005 and http://www.bawt.tcl3d.org.
Most packages will be build with MSys/MinGW and some other need VS.

You just need to download the build environment from his site.
Extract it.
Call "Build-Windows.bat x64 vs2008 Bawt-All\All.bawt“.
That’s it.

Tcl/Tk with a lot of packages (batteries included) will automatically build.

Regards,
Alex

Bochum - Germany

> Am 17.07.2017 um 16:43 schrieb Martin Lemburg <mar...@gm...>:
> 
> Dear Harald,
> 
> Thanks for your guide to building tcl in VS201x.
> 
> A short summary:
> 
> 1. get the most current sources from core.tcl.tk (extract to FileSystem (FS))
> 2. Use the VS developer console to build tcl(/Tk)
> 2.a Building Tk needs TCLDIR environment variable pointing to tcl source code containing directory
> 3. use nmake, not the ./win/buildall.vc.bat file - which stumbled building zlib from the VS developer console.
> 
> Questions:
> 
> 1. Visual Studio projects/solutions
> 
> There are ./win/tcl.dsp and ./win/tcl.dsw files.
> Those are VC6 project/solution files, but there are now more recent VS201x project/solution files.
> If I would use those, VS2017 would try to convert them, so I'd try to work with them.
> But, why are they so "old"? Why aren't much "younger" files included?
> Sergey mentioned the project file, does anyone else use it?
> 
> 2. Fossil/github mirror
> 
> I might download the most current fossil sources or I might clone the github mirror and work on that.
> Since I won't necessarily need the direct repository access, whom would I may give the patches, changed files to put it into a "test" branch, test it, …?
> Or may I create my branch on the cloned repository change the desired files push the changes and fossil will get those? I fear not, since github is only a mirror and I don't have write access to the fossil repository, am I wrong?
> So - to keep it simple - should I stay with Haralds suggested scenario downloading, extracting, changing, and …?
> 
> 3. TIP creation
> The TIPs are about to migrate - some day - to fossil.
> But currently I have to stay with writing a TIP (accordingly to #2 and #3) and send it to Donal, correct?
> BTW: https://www.tcl.tk/cgi-bin/tct/tip/ is blocked by chrome trying to load scripts from an unsafe location.
> 
> Best regards,
> 
> Martin Lemburg
> Berlin / Germany
> 
> mar...@gm...
> http://about.me/Martin0815
> 
> ------------------------------------------------------------------------------
> Gesendet: Montag, 17. Juli 2017 um 09:14 Uhr
> Von: "Harald Oehlmann" <har...@el...>
> An: tcl...@li...
> Betreff: Re: [TCLCORE] Build on Windows 10 w/ VS2017 Community Edition and TIP organization …
>> Dear Martin,
>> 
>> thank you trying this !
>> 
>> First I recomment to use fossil. All the recent TCL knowledge is there
>> including the wiki. I try to include info like "how to build" on the
>> wiki... Don't mix with the tcl wiki "wiki.tcl.tk". The core wiki is in
>> the tcl core repository.
>> 
>> To make build tries, you don't need an installation.
>> - Go to http://core.tcl.tk/tcl
>> - Login as anonymous to get zip download and ticket features.
>> - Click on timeline
>> - click on the very left number of the last node with "tags:trunk". At
>> the moment, this is "[a3919af766]". This will lead you to:
>> http://core.tcl.tk/tcl/info/a3919af766032254[http://core.tcl.tk/tcl/info/a3919af766032254]
>> - klick on "TIP Archive" to get the current test version.
>> 
>> Now how to build ?
>> Here is my recipee. It is my way, other ways exist. This is the
>> mingw-free way. Most use the mingw way.
>> - create a folder c:\test
>> - copy the downloaded zip file to it
>> - extract it. You get C:\test\Tcl_Source_Code-a3919af766
>> - go in the start menu to
>> Visual Studio 2015\Visual Studio Tools\Windows Desktop Command
>> Prompts\VS2015 x86 Native Tools-Eingabeaufforderung
>> - type in the command prompt:
>> c:\test\Tcl_Source_Code-a3919af766\win
>> nmake -f makefile.vc
>> nmake -f makefile.vc INSTALL INSTALLDIR=c:\test\tcl-a3919af766
>> - you have tclsh.exe in c:\test\tcl-a3919af766\bin
>> 
>> If you want to build Tk, it is quite similar, specify the
>> TCLDIR=c:\test\Tcl_Source_Code-a3919af766 in addition to the command line.
>> 
>> If this scares you, I am sorry. I have many projects here (non TCL
>> community projects like zint, qzint) which build like that.
>> It sounds strange, but it is much more error-save than using
>> VisualStudio project files.
>> See the make file for more info.
>> 
>> ---
>> 
>> fossil is great. But it is command line and may feel very scary, I am
>> sorry for that. But it is the gate to the core, so please try to look
>> into it.
>> 
>> ---
>> 
>> About TIP's: it is also "scary" as it is but so far, we work with it and
>> it is better than nothing. So, if you have a tip, send it to donal by
>> email and hope, that he is not on holidays etc.
>> 
>> ---
>> Hope this helps,
>> Harald