• Announce: BAWT 2.1.0 released

    From Paul Obermeier@21:1/5 to All on Thu Dec 30 19:25:17 2021
    Version 2.1.0 of BAWT, the "Build Automation With Tcl" framework has been released on 2021/12/28.


    The following features are included in this release:
    - Support for Tcl/Tk 8.6.12.
    - Support for tclMuPDF.
    - Several updated packages.
    - Windows Setup programs for Tcl/Tk 8.6.11, 8.6.12 and 8.7.a5.

    See http://www.bawt.tcl3d.org/ for more information and downloads.

    Best regards,
    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alexandru@21:1/5 to Paul Obermeier on Fri Dec 31 04:20:03 2021
    Paul Obermeier schrieb am Donnerstag, 30. Dezember 2021 um 19:25:21 UTC+1:
    Version 2.1.0 of BAWT, the "Build Automation With Tcl" framework has been released on 2021/12/28.


    The following features are included in this release:
    - Support for Tcl/Tk 8.6.12.
    - Support for tclMuPDF.
    - Several updated packages.
    - Windows Setup programs for Tcl/Tk 8.6.11, 8.6.12 and 8.7.a5.

    See http://www.bawt.tcl3d.org/ for more information and downloads.

    Best regards,
    Paul

    Hi Paul,

    I tested the basic procedure to compile:

    Create basic Tcl packages for 64-bit (using only MSYS / MinGW): Build-Windows.bat x64 gcc Setup\Tcl_Basic.bawt update

    All seem to work correctly.

    Now I wonder if I should create extended Tcl packages including InnoSetup installation executable for 64-bit (using Visual Studio 2013 to build Tcl packages supporting Visual Studio like Mpexpr and tkdnd):
    Build-Windows.bat x64 vs2013+gcc Setup\Tcl_Distribution.bawt update

    When is this step required? If I need it, should it be performed as a second step right after the first one? Is there a list of all packages, that are compiled by the second step?

    Thanks
    Alexandru

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Obermeier@21:1/5 to All on Fri Dec 31 16:59:39 2021
    Paul Obermeier schrieb am Donnerstag, 30. Dezember 2021 um 19:25:21 UTC+1:
    Version 2.1.0 of BAWT, the "Build Automation With Tcl" framework has been released on 2021/12/28.


    The following features are included in this release:
    - Support for Tcl/Tk 8.6.12.
    - Support for tclMuPDF.
    - Several updated packages.
    - Windows Setup programs for Tcl/Tk 8.6.11, 8.6.12 and 8.7.a5.

    See http://www.bawt.tcl3d.org/ for more information and downloads.

    Best regards,
    Paul

    Hi Paul,

    I tested the basic procedure to compile:

    Create basic Tcl packages for 64-bit (using only MSYS / MinGW): Build-Windows.bat x64 gcc Setup\Tcl_Basic.bawt update

    All seem to work correctly.

    Now I wonder if I should create extended Tcl packages including InnoSetup installation executable for 64-bit (using Visual Studio 2013 to build Tcl packages supporting Visual Studio like Mpexpr and tkdnd):
    Build-Windows.bat x64 vs2013+gcc Setup\Tcl_Distribution.bawt update

    When is this step required? If I need it, should it be performed as a second step right after the first one? Is there a list of all packages, that are compiled by the second step?

    Thanks
    Alexandru

    Am 31.12.2021 um 13:20 schrieb Alexandru:

    Chapter 3.2 of the user manual lists the dependencies and contents of the different Setup files:
    Tcl_Distribution.bawt builds all packages contained in Tcl_Basic.bawt, Tcl_Extended.bawt and Tcl_Distribution.bawt.

    If you call the seconds batch line, only the packages contained in Tcl_Extended.bawt and Tcl_Distribution are rebuilt,
    as you are using the "update" action.

    Note: The Windows BI distributions available on the BAWT homepage are built using gcc+vs2019 and Tcl_Distribution.bawt.

    Happy new year,
    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alexandru@21:1/5 to Paul Obermeier on Fri Dec 31 08:23:13 2021
    Paul Obermeier schrieb am Freitag, 31. Dezember 2021 um 16:59:44 UTC+1:
    Paul Obermeier schrieb am Donnerstag, 30. Dezember 2021 um 19:25:21 UTC+1:
    Version 2.1.0 of BAWT, the "Build Automation With Tcl" framework has been released on 2021/12/28.


    The following features are included in this release:
    - Support for Tcl/Tk 8.6.12.
    - Support for tclMuPDF.
    - Several updated packages.
    - Windows Setup programs for Tcl/Tk 8.6.11, 8.6.12 and 8.7.a5.

    See http://www.bawt.tcl3d.org/ for more information and downloads.

    Best regards,
    Paul

    Hi Paul,

    I tested the basic procedure to compile:

    Create basic Tcl packages for 64-bit (using only MSYS / MinGW): Build-Windows.bat x64 gcc Setup\Tcl_Basic.bawt update

    All seem to work correctly.

    Now I wonder if I should create extended Tcl packages including InnoSetup installation executable for 64-bit (using Visual Studio 2013 to build Tcl packages supporting Visual Studio like Mpexpr and tkdnd):
    Build-Windows.bat x64 vs2013+gcc Setup\Tcl_Distribution.bawt update

    When is this step required? If I need it, should it be performed as a second step right after the first one? Is there a list of all packages, that are compiled by the second step?

    Thanks
    Alexandru
    Am 31.12.2021 um 13:20 schrieb Alexandru:

    Chapter 3.2 of the user manual lists the dependencies and contents of the different Setup files:
    Tcl_Distribution.bawt builds all packages contained in Tcl_Basic.bawt, Tcl_Extended.bawt and Tcl_Distribution.bawt.

    If you call the seconds batch line, only the packages contained in Tcl_Extended.bawt and Tcl_Distribution are rebuilt,
    as you are using the "update" action.

    Note: The Windows BI distributions available on the BAWT homepage are built using gcc+vs2019 and Tcl_Distribution.bawt.

    Happy new year,
    Paul
    Thanks for the help.
    I just started it with VS2019.
    I need to compile myself, because after that I need the sdx and kit files for self packing my Tcl/Tk app.

    Happy new year to you too!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)