Build on Windows 10 w/ VS2017 Community Edition and TIP organization …

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Build on Windows 10 w/ VS2017 Community Edition and TIP organization …

Martin Lemburg
Hi all together,
 
Some questions, because the EuroTcl and the feature list for 8.7a made me decide to get involved a bit more:
  1. As non-Linux user, not familiar with Cygwin, Mingw, etc. I just installed Visual Studion 2017 Community Edition. Afterwards I created a new project cloning the current tcl repository mirrored at github.
    Now I want to just build tcl/Tk and do not know how to do.
    I have a CMake menu, but this does not "connect" to the tcl build system.
    I have the buildall.vc.bat file in the win folder, used it in the developer command prompt started from within VS2017, but it fails while trying to build zlib with:

    "zconf.h": No such file or directory

    This is correct, since there are only zconf.h.cmakein, zconf.h.in and zconf.h.included available. But shouldn't the zconf.h be build automatically to be used in the zlibs build? What am I or the build system missing?

    So - is there still no way to build tcl more easily with Visual Studio? More easily, than in the last 18 years?

    Some may say, that I'm doing it wrong, that it is so simple to use Linux-like build systems or Eclipse … if it is so simple, please instruct me, but please with direct emails to keep this distribution list less noisy.
    BTW I never needed to use Eclipse and since "decades" I'm working with Visual Studio! My brain and memory resources are limited and if it is possible, I'd like to stay in my "work" environment to keep me from learning new things, but to concentrate on providing new things to tcl/Tk.

    I may ask a colleague, who got it right to build tcl in VS2008, VS2010, VS2013. Eventually that would work with VS2017CE, too. But if he is allowed to share his work for my private engagement? I don't know.
     
  2. The TIP system is about to be changed, right? Is there already a plan, a how-to?
    If the TIPs are (in some time) hosted at the FOSSIL repository, will the be mirrored to github, too?

    So if I want to TIP something how to start today?

    Or better waiting some "weeks", to get the new system implemented?
     
  3. I never used FOSSIL and git mostly never from the command line. Would it be okay to start enhancing tcl/Tk starting cloning the github mirror?
    Or is there a FOSSIL source code revision system plug-in for VS2017 available, so I could connect to the original repository?
    Or is it "better" to get a copy of the source code, to enhance the wished parts accordingly to a new TIP and provide the patch to those with FOSSIL experiences and write access to integrate the hopefully accepted new stuff?
Thanks in advance for some enlighting information!
 
Good night!
 
Martin Lemburg
Berlin / Germany

[hidden email]
http://about.me/Martin0815

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Tcl-Core mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/tcl-core
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

tcl-core mailing list

Hi Martin,

- To build tcl using command line, you need first set the VS environment variables, hereafter use nmake.

Below you'll find an example for VS2K8 (9.0):

if "%VCINSTALLDIR%" == "" call "%VS90COMNTOOLS%vsvars32.bat"
nmake -nologo -f makefile.vc release OPTS=threads,thrdalloc

- To build tcl via IDE:

A while ago I repaired build for windows via VS-IDE (in fossil 8.5 - trunk).
If you had previously compiled older version you should firstly remove (auto-created) "win\nmakehlp.exe".
Hereafter, just open "tcl.dsp" with Visual Studio (it should be converted to VS solution on demand).
If your VS version is unable to convert ".dsp" to ".vcproj", I can send you the "tcl.vcproj"...

Regards,
Sergey.

Am 16.07.2017 22:44, schrieb Martin Lemburg:

Hi all together,
 
Some questions, because the EuroTcl and the feature list for 8.7a made me decide to get involved a bit more:
  1. As non-Linux user, not familiar with Cygwin, Mingw, etc. I just installed Visual Studion 2017 Community Edition. Afterwards I created a new project cloning the current tcl repository mirrored at github.
    Now I want to just build tcl/Tk and do not know how to do.
    I have a CMake menu, but this does not "connect" to the tcl build system.
    I have the buildall.vc.bat file in the win folder, used it in the developer command prompt started from within VS2017, but it fails while trying to build zlib with:

    "zconf.h": No such file or directory

    This is correct, since there are only zconf.h.cmakein, zconf.h.in and zconf.h.included available. But shouldn't the zconf.h be build automatically to be used in the zlibs build? What am I or the build system missing?

    So - is there still no way to build tcl more easily with Visual Studio? More easily, than in the last 18 years?

    Some may say, that I'm doing it wrong, that it is so simple to use Linux-like build systems or Eclipse … if it is so simple, please instruct me, but please with direct emails to keep this distribution list less noisy.
    BTW I never needed to use Eclipse and since "decades" I'm working with Visual Studio! My brain and memory resources are limited and if it is possible, I'd like to stay in my "work" environment to keep me from learning new things, but to concentrate on providing new things to tcl/Tk.

    I may ask a colleague, who got it right to build tcl in VS2008, VS2010, VS2013. Eventually that would work with VS2017CE, too. But if he is allowed to share his work for my private engagement? I don't know.
     
  2. The TIP system is about to be changed, right? Is there already a plan, a how-to?
    If the TIPs are (in some time) hosted at the FOSSIL repository, will the be mirrored to github, too?

    So if I want to TIP something how to start today?

    Or better waiting some "weeks", to get the new system implemented?
     
  3. I never used FOSSIL and git mostly never from the command line. Would it be okay to start enhancing tcl/Tk starting cloning the github mirror?
    Or is there a FOSSIL source code revision system plug-in for VS2017 available, so I could connect to the original repository?
    Or is it "better" to get a copy of the source code, to enhance the wished parts accordingly to a new TIP and provide the patch to those with FOSSIL experiences and write access to integrate the hopefully accepted new stuff?
Thanks in advance for some enlighting information!
 
Good night!
 
Martin Lemburg
Berlin / Germany

[hidden email]
http://about.me/Martin0815

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Tcl-Core mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/tcl-core

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Tcl-Core mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/tcl-core
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

Harald Oehlmann
In reply to this post by Martin Lemburg
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
- 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

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Tcl-Core mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/tcl-core
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

Christian Gollwitzer
In reply to this post by tcl-core mailing list
Am 17.07.17 um 09:07 schrieb Dipl. Ing. Sergey G. Brester via Tcl-Core:
> - To build tcl using command line, you need first set the VS environment
> variables, hereafter use nmake.
>
> Below you'll find an example for VS2K8 (9.0):
>
> if "%VCINSTALLDIR%" == "" call "%VS90COMNTOOLS%vsvars32.bat"

This line is specific for one version of VS. Instead of trying to figure
out the correct incantation, you can run a properly set up command line
window from the VS menu. There is a menu entry called "Visual Studio
Developer Command Prompt" or similar, it varies a bit between versions
and for the more professional versions you can choose between the target
(32 bit, 64 bit, bitness of the compiler itself). This will open up a
cmd.exe window with all set up.

You can check that it works by typing "cl" only; this should display a
help message of the MS compiler, stating which version/bitness it will
compile for.

> nmake -nologo -f makefile.vc release OPTS=threads,thrdalloc

That should be run in the windws/ subdir of the Tcl sources.

Compiling Tcl and Tk that way is not hard. If you want a bunch of
interesting extensions, I suggest that you take a look at build systems,
though. There is BAWT from Paul Obermeier
http://www.bawt.tcl3d.org/documentation.html and kbs from Rene Zaumseil
https://sourceforge.net/projects/kbskit/files/kbs/0.4.8/

Yes, they require MinGW (there is a ready-to-install package on the BAWT
site) and compile using gcc instead of Visual Studio, but the advantage
is that from a single command you can install a large number of useful
extensions (tkpath, ...) Another variant is the excellent KitCreator
from Roy Keene http://kitcreator.rkeene.org/kitcreator
It compiles stuff on the server for a large nuber of platforms and you
can download it afterwards. Here the selection of packages is rather
small, unfortunately.

        Christian

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Tcl-Core mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/tcl-core
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

Martin Lemburg
In reply to this post by Harald Oehlmann
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

[hidden email]
http://about.me/Martin0815

------------------------------------------------------------------------------
Gesendet: Montag, 17. Juli 2017 um 09:14 Uhr
Von: "Harald Oehlmann" <[hidden email]>
An: [hidden email]
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
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot[http://sdm.link/slashdot]
_______________________________________________
Tcl-Core mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/tcl-core[https://lists.sourceforge.net/lists/listinfo/tcl-core]

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Tcl-Core mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/tcl-core
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

Alexander Schöpe-2
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 <[hidden email]>:
>
> 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
>
> [hidden email]
> http://about.me/Martin0815
>
> ------------------------------------------------------------------------------
> Gesendet: Montag, 17. Juli 2017 um 09:14 Uhr
> Von: "Harald Oehlmann" <[hidden email]>
> An: [hidden email]
> 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

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Tcl-Core mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/tcl-core

smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

Martin Lemburg
Thanks Alexander,

BAWT was mentioned before, but after taking a look, it is not necessarily the think I need to develop inside the tcl sources.
If I do not write perfect working code, I'd like to inspect, to debug it and while BAWT is for sure really helpful in build from the scratch ….

I'm a lazy guy, wanting to stay in its used environment, needing some really good reasons to exchange it.

Best regards,
 
Martin Lemburg
Berlin / Germany

[hidden email]
http://about.me/Martin0815
 
 
--------------------------------------------------------------------------------
Gesendet: Montag, 17. Juli 2017 um 17:53 Uhr
Von: "Alexander Schöpe" <[hidden email]>
An: "Tcl Core List" <[hidden email]>
Cc: "Martin Lemburg" <[hidden email]>
Betreff: Re: [TCLCORE] Build on Windows 10 w/ VS2017 Community Edition and TIP organization …

> 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[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 <[hidden email]>:
> >
> > 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/[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
> >
> > [hidden email]
> > http://about.me/Martin0815[http://about.me/Martin0815]
> >
> > ------------------------------------------------------------------------------
> > Gesendet: Montag, 17. Juli 2017 um 09:14 Uhr
> > Von: "Harald Oehlmann" <[hidden email]>
> > An: [hidden email]
> > 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[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][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

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Tcl-Core mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/tcl-core
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

Harald Oehlmann
In reply to this post by Martin Lemburg
Dear Martin,

Great resumé.
I did core development like that (Windows socket driver).

About fossil or GitHub - I suppose in a first place you should just
deliver patches as tickets on fossil - you don't need a fossil
installation for that, just use the web interface.

Later, the TCL core guys may give you a login and then, you can write
directly in fossil. But mostly, the login comes sooner than one expects ;-)

I also ivite you to maintain pages as wiki.tcl.tk, so for example put a
recipe on how one may develop with MS-VC 12.

About the project files. They are always old, intransparent and tend to
depend to local computers. I have this issue with many non TCL projects.
Makefile.vc at least works and is kept up to date...

Enjoy,
Harald

Am 17.07.2017 um 16:43 schrieb Martin Lemburg:

> 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
>
> [hidden email]
> http://about.me/Martin0815
>
> ------------------------------------------------------------------------------
> Gesendet: Montag, 17. Juli 2017 um 09:14 Uhr
> Von: "Harald Oehlmann" <[hidden email]>
> An: [hidden email]
> 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
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot[http://sdm.link/slashdot]
> _______________________________________________
> Tcl-Core mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/tcl-core[https://lists.sourceforge.net/lists/listinfo/tcl-core]
>


--
ELMICRON Dr. Harald Oehlmann GmbH
Koesener Str. 85
06618 Naumburg
Germany
Phone: +49 (0)3445 78112-0
Fax: +49 (0)3445 78112-19
www.Elmicron.de
German legal references:
Geschaeftsfuehrer: Dr. Harald Oehlmann, Jens Oehlmann
UST Nr. / VAT ID No.: DE206105272
HRB 212803 Stendal

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Tcl-Core mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/tcl-core
Loading...