The website has been updated with the new links. These are the basically the same MinGW 32-bit GnuCOBOL 3.2 Final Release binaries for Windows, but the PDF format GnuCOBOL manuals have been updated recently.
Since about 27Jul2023, www.osdn.net has been down or very slow while transferring to a new hosting services, so it has been impossible to download mingw-get.exe and update a MinGW32 build environment.
Here are links to backups of my development MinGW folder:
Here is an additional MinGW build of GnuCOBOL 3.2 using Berkeley DataBase 6.0.19, which was the last version that used the Sleepycat license. This is a much less restrictive license that should make it easier to distribute programs compiled with GnuCOBOL.
GnuCOBOL 3.2 with BDB 6.0.19 (31May2013) passes all the same tests as GnuCOBOL 3.2 with the most current BDB 18.1.40.
Note @jamesbwhite: all versions up to 6.0.19 (= including 5.3.28 and 4.8) are available freely under the Sleepycat license.
Newer versions switched to AGPL which means that it is still free to use, but if you distribute binaries linked to that (like Arnold does with the packages - but the source to GnuCOBOL is always available) or if you run the program for the user (for example with a web frontend) you need to make the source to the programs using that library also available to the user.
This is the reason why people that don't want to distribute their (COBOL) source only use AGPL'd software locally, but neither in a (web) server chain nor distributing binaries linked to that.
When speaking of GnuCOBOL one could distribute binaries that are linked to libcob only - but not libcob or its dependencies in binary form) and the receiving party could use those with whatever libcob (and bdb/vbisam/...) they want; for example by getting the later from Arnold's distribution locally.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The website has been updated with the new links. These are the basically the same MinGW 32-bit GnuCOBOL 3.2 Final Release binaries for Windows, but the PDF format GnuCOBOL manuals have been updated recently.
https://www.arnoldtrembley.com/GC32-BDB-SP1-rename-7z-to-exe.7z
https://www.arnoldtrembley.com/GC32-VBI-SP1-rename-7z-to-exe.7z
https://www.arnoldtrembley.com/GC32-NODB-SP1-rename-7z-to-exe.7z
Lots of older binaries are still available at:
https://www.arnoldtrembley.com/GnuCOBOL.htm
GnuCOBOL 3.2 Build Guide for MinGW 32-bit (in PDF or LibreOffice .docx format which also works in MS Word:
https://www.arnoldtrembley.com/GnuCOBOL-3.2-MinGW-Build-Guide-V1.8.pdf
https://www.arnoldtrembley.com/GnuCOBOL-3.2-MinGW-Build-Guide-V1.8.docx
Here is the normal link to OSDN.NET for the MinGW 32-bit tools:
https://mingw.osdn.io/index.html
Since about 27Jul2023, www.osdn.net has been down or very slow while transferring to a new hosting services, so it has been impossible to download mingw-get.exe and update a MinGW32 build environment.
Here are links to backups of my development MinGW folder:
After installing MinGW, but before building any GnuCOBOL components:
https://www.arnoldtrembley.com/MinGW-bkup01.7z
Like the previous backup, but after building a gmplib "fat" binary, per the build guide:
https://www.arnoldtrembley.com/MinGW-bkup02.7z
Here is an additional MinGW build of GnuCOBOL 3.2 using Berkeley DataBase 6.0.19, which was the last version that used the Sleepycat license. This is a much less restrictive license that should make it easier to distribute programs compiled with GnuCOBOL.
GnuCOBOL 3.2 with BDB 6.0.19 (31May2013) passes all the same tests as GnuCOBOL 3.2 with the most current BDB 18.1.40.
https://www.arnoldtrembley.com/GC32-BSL-rename-7z-to-exe.7z
Note @jamesbwhite: all versions up to 6.0.19 (= including 5.3.28 and 4.8) are available freely under the Sleepycat license.
Newer versions switched to AGPL which means that it is still free to use, but if you distribute binaries linked to that (like Arnold does with the packages - but the source to GnuCOBOL is always available) or if you run the program for the user (for example with a web frontend) you need to make the source to the programs using that library also available to the user.
This is the reason why people that don't want to distribute their (COBOL) source only use AGPL'd software locally, but neither in a (web) server chain nor distributing binaries linked to that.
When speaking of GnuCOBOL one could distribute binaries that are linked to libcob only - but not libcob or its dependencies in binary form) and the receiving party could use those with whatever libcob (and bdb/vbisam/...) they want; for example by getting the later from Arnold's distribution locally.